Windows 11 Sign out option has disappeared since the June 2024 Preview

T

tired-it

Member
I have been trying to troubleshoot this for a while and I could use some fresh perspectives.

This issue is related to the information in this microsoft answer page. Basically, the Sign Out and Switch User options have been hidden behind a 3-dot menu when clicking the account picture (thanks MS for making the UI worse again). Is there a way, perhaps a registry edit, to revert the change?

Another related issue is that I have applied registry keys through NTLite to lock down a user account so they can no longer access the Settings app. That user account no longer sees a Sign Out option when clicking the account picture. In fact, nothing comes up at all when clicking on the account picture. The user is forced to either right click on the Windows icon or to use CTRL+ALT+DEL to sign out.

I'm managing an environment where some users will think their PC is broken if an option is missing and so I would prefer to keep the Sign Out option in its original place. To be fair, I cannot confirm that the missing menu is the result of the registry key, but seeing as how the update changed something about how that particular sign out experience works, it is fair to assume they are somewhat related.
 
Tried out the tool on a live install and it worked. Is it possible to implement this via NTLite using Post-Setup? I'll be experimenting with this, but the idea is to run the command and then delete the file(s) afterwards. Not sure it can be done before logon though.

Edit: I can also confirm that the locked down user profile now has the ability to sign out by clicking on the account picture. So the update was certainly the cause of the issue mentioning in the OP. Also edited the title to reflect garlin's clarification.
 
Last edited:
Created a simple batch file to CD into the imported ViveTool directory, run the command and then delete the folder contents. There are probably cleaner ways to do with, but I want to see if this works first.
 
1. After running ViveTool, export the current set of Feature Control overrides:
Code: 
reg export "HKLM\System\ControlSet001\Control\FeatureManagement\Overrides" FeatureControl.reg

2. From the Registry screen, import this reg file. Overrides are always loaded on every boot.

Two years from now, when MS removes the underlying code to switch back in a future update, you'll be screwed again.
 
tired-it said:
Edit: I can also confirm that the locked down user profile now has the ability to sign out by clicking on the account picture. So the update was certainly the cause of the issue mentioning in the OP. Also edited the title to reflect garlin's clarification.
Click to expand...
New features always arrive first in the Monthly Preview, before showing up next month. So June 2024 Preview.

Does it matter? Yes, because if you're reading the CU release notes, it won't list any changes for July because MS never repeats what they wrote back in June's Preview. That's just how they handle the release cycle.
 
garlin said:
New features always arrive first in the Monthly Preview, before showing up next month. So June 2024 Preview.

Does it matter? Yes, because if you're reading the CU release notes, it won't list any changes for July because MS never repeats what they wrote back in June's Preview. That's just how they handle the release cycle.
Click to expand...
Yeah I am aware of the distinction. Granted, I never install the previews and opt to wait for the proper monthly release.
 
Update: My initial experiment worked. Restart was still required for changes to take effect, not a big deal. The Vivetool folder was imported before logon. A batch file would CD into the vivetool folder, run the command and then delete all the files within. I opted to leave the empty Vivetool folder within the Setup folder so I can confirm it was copied over. Also confirmed that the change affects all accounts. I may be able to deploy this as a standalone package as needed.

The registry solution is exactly what was looking for. I am going to attempt to narrow down the export to just the specific changes. Searching the registry for the feature IDs in garlin's answer turned up no results, so I will manually comb through a few options.

Edit: Found the registry entries. That was easy.


Code: 
[HKEY_LOCAL_MACHINE\System\ControlSet001\Control\FeatureManagement\Overrides\8\1801939084]
"EnabledState"=dword:00000001

[HKEY_LOCAL_MACHINE\System\ControlSet001\Control\FeatureManagement\Overrides\8\1853569164]
"EnabledState"=dword:00000001

Default value is 2. A value of 1 disables the feature.
 
Last edited:
You must log in or register to reply here.
Back
Top