[SOLVED] Waiting for local session manager at every boot

Deleted022220

Well-known member
Joined
Dec 14, 2019
Posts
74
Good morning. I am getting this error, and at shutdown "stopping services" message.
In addition, when I click system button at settings in Windows 10, it automatically closes.
 
Are you connected to a network server at all? Is this a personal computer or a work one?
 
No unfortunately not. To my knowledge, the Local Session Manager service is used when connected to a network domain, was your computer connected to the school network? When does the error occur?
 
No unfortunately not. To my knowledge, the Local Session Manager service is used when connected to a network domain, was your computer connected to the school network? When does the error occur?
I reinstalled Windows from scratch. So, from the beginning, the issue occurred.
 
I have had verbose messages turned on for boot and shut down on my system for several years now. The "Waiting for local session manager" message has always, since day one, been a part of every boot.

I connect to nothing except my WiFi.
 
I have had verbose messages turned on for boot and shut down on my system for several years now. The "Waiting for local session manager" message has always, since day one, been a part of every boot.

I connect to nothing except my WiFi.
I solved it by going to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Then, I deleted DWORD verbosestatus.
Moreover, setting value to 1 in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages
 
I have no desire to disable verbose messages, as I intentionally enabled them. I prefer to know what step the boot or shutdown process is actually at rather than having a perpetual, "Please wait," message.

My point was that the session manager wait is a standard step of the boot/shutdown process that most people never know about if they do not have verbose status messages enabled to begin with.
 
I solved it by going to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Then, I deleted DWORD verbosestatus.
Moreover, setting value to 1 in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages

Thanks for mentioning your solution, glad you were able to get the issue resolved.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top