May 8, 2019 at 10:07 pm #33221
Has anyone got any suggestions please? I managed to get my computer stuck in a boot loop as I described here:
Windows would look as if it was getting to the login screen, but it stayed black other than the cursor and a spinning circle. I found a registry edit for the recovery mode that gave me a command line at that point, so ran msconfig and set it to reboot into a minimal safe boot with all non MS services disabled. Now it reboots to a low resolution black screen with a spinning circle of white dots and won’t go any further.
Other than chkdsk finding a disk error on my SSD on the first boot, none of the recovery options do anything. I can’t undo the safe boot option, and I can’t get the command line back as Windows doesn’t get far enough. sfc /scannow doesn’t find any errors, and the startup repair log says that Windows is starting up properly. The Windows boot log says that everything except DirectX loads properly, until the second or third boot when it says that dozens of drivers won’t load.
I can’t think of anything else, and I don’t really want to wipe and reinstall or do a refresh install if I can help it, but wouldn’t mind running setup from Windows and doing a repair install if I can keep my setup.
Can anyone help please?
June 7, 2019 at 11:54 am #33962
Wheels-Of-FireParticipant@grahamdearsleyForumite Points: 1,542
Maybe an explination of how things SHOUD work would help.
Logon begins when the local session manager (Lsm.exe) runs for the first time and calls Winlogon.exe. Both Lsm and Winlogin are critical processes and the system will blue screen instantly if either stops running. Because Winlogin is critical you never get to actually see it, it calls LogonUI.exe as a child process and that presents you with the login box. The idea is if LogonUI crashes then Winlogin can restart it.
LogonUI handles the running of credential providers which by default are password or smartcard but developers can write their own.
Once a users details have been captured LogonUI will pass them to the local security authentication server process (LSASS.exe) and then close.
Once a users credentials have been verified LASS obtains an access token object that contains the users security profile. If you are an admin and UAC is enabled then a second restricted token is also generated and thats the one that gets used until you use ellivation.
The token is passed back to Winlogon which uses it to run Userinit.exe with the correct user details.
Userinit does some initialisation including running the logon script and then runs the user shell (usually explorer.exe) then it quits.
You will now see your desktop. Winlogon never quits and its always in the background waiting for someone to press CTL ALT DEL.00
You must be logged in to reply to this topic.