-
Notifications
You must be signed in to change notification settings - Fork 14
[Issue]: Solutions to the problem that some devices still cannot configure or enter FSE after a reboot. #17
Description
⚠️ Step 1: Required Checks
- I have read the entire README, especially the following sections:
- "System Requirements" (I confirm my build is one of the COMPATIBLE builds:
26100.7019+,26200.7015+or26220.6972+.) - "Screen Dimension Override for Desktop PCs & Laptops" (I understand the difference between
PhysPanelCS/PhysPanelDrv) - "Quick Start" (I have followed the installation and initial setup steps.)
- I understand this tool is an Enabler / Activation Utility / Configuration Tool and not the implementer of the Full Screen Experience (FSE) feature. I understand FSE itself is a Shell Replacement that replaces the normal Windows desktop/taskbar, and FSE's behavior is not a bug in this tool.
- I have already tried going to the Microsoft Store to update all apps (especially Xbox and Game Bar).
- I have searched the existing Issues to ensure my problem is not already reported.
1. What is your PC Type?
Laptop
PC Model
Surface Laptop Studio, Surface Pro 12 in 1st Ed with Snapdragon
2. What is your full Windows OS Build number?
26100.7019, 26100.7171
3. Which "Screen Dimension Override Mode" are you currently using?
Task Scheduler Mode (PhysPanelCS) (Default)
4. Which Xbox Full Screen Experience Tool version are you using?
v0.0.13
5. Describe your issue or question:
Hi @8bit2qubit,
I have found a solution to the problem that some users cannot automatically enter the full-screen experience after logging in.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"DisableAutomaticRestartSignOn" = 1
The policy setting controls whether a device will automatically sign in and lock the last interactive user after the system restarts or after a shutdown and cold boot. Setting the DWORD registry value to 1 is an equivalent to setting the group policy "Computer Configuration > Windows Components > Windows Logon Options > Sign-in and lock last interactive user automatically after a restart" to "Disabled", making the user's startup apps and scripts not started after the system starts until a user is explicitly logged in, enabling the system-level scheduled task to be executed before the user is logged in.
The policy setting has a minor impact on the user experience as it does not force users to wait until the scheduled tasks have completed before logging in. It can be incorporated as an optional feature into your tool.
6. Steps to Reproduce (if applicable):
No response
7. Expected Behavior:
(None)
8. Actual Behavior:
(None)