Fix "Winlogon Process Termination Detected" on Windows 10/11

You're sitting at your desk, Windows 10 boots up fine, you see the login screen. You type your password, hit Enter — black screen. Then a blue screen flashes for half a second and the PC restarts. This loop keeps going. You can't get in. The error message says something like "Winlogon Process Termination Detected" or sometimes just a stop code like CRITICAL_PROCESS_DIED. This usually happens right after a Windows Update or a driver install. I've seen it most often on HP and Dell laptops after a cumulative update, especially KB5026372 from May 2023.

What causes this?

Winlogon.exe is the process that handles your login — it loads your desktop, your start menu, your profile. When it crashes, Windows has no choice but to restart because it can't keep the system secure without a working login. The crash is almost always because a recent update or driver changed something that Winlogon depends on. The worst part is you can't even uninstall the update normally because you can't log in.

The fix — step by step

You need to break the loop by starting Windows in Safe Mode. Safe Mode loads only the bare minimum drivers and services. From there you can undo the update or fix the driver.

1. Force restart into recovery mode. Turn your PC on. As soon as you see the Windows logo spinning, hold the power button until it shuts off. Do this three times in a row. On the fourth boot, Windows should show a blue screen with options. This is the Windows Recovery Environment (WinRE).
2. Select "Troubleshoot". You'll see a list of three or four options. Click "Troubleshoot".
3. Select "Advanced options". Then click "Startup Settings".
4. Click "Restart". The PC will restart and show a list of numbered options.
5. Press 4 or F4 to select "Enable Safe Mode". If you need networking (for example, to download a driver), press 5 or F5 for "Safe Mode with Networking".
6. Windows should now start in Safe Mode. The screen will look different — black background, "Safe Mode" in the corners. Log in with your normal password. This time it should work.
7. Uninstall the latest Windows Update. Press the Windows key, type "View installed updates", press Enter. In the list, look for the most recent update (sort by "Installed On" if needed). Select it and click "Uninstall". Restart the PC — it should boot normally now.
8. If you can't find the update or uninstalling doesn't help, try System Restore. In Safe Mode, press Windows key + R, type rstrui.exe, press Enter. Choose a restore point from before the problem started — ideally a few days before. Click Next, then Finish. The PC will restart and restore. This fixes about 80% of Winlogon crashes I've seen.
9. Run SFC and DISM to repair system files. In Safe Mode, open Command Prompt as Administrator (right-click Start, select "Windows Terminal (Admin)"). Run this command:

   sfc /scannow

   Wait for it to finish. If it finds corrupt files, run this afterwards:

   DISM /Online /Cleanup-Image /RestoreHealth

   Then restart.
10. Check for bad drivers. If Safe Mode works but normal boot still crashes, a driver is the problem. Go to Device Manager (right-click Start, select Device Manager). Look for devices with a yellow exclamation mark. Update or roll back the driver for your graphics card, network card, or chipset. If you recently installed a new printer or webcam driver, uninstall that device entirely and try a generic driver.

What to check if it still fails

Sometimes none of the above works. The real culprit might be a corrupt user profile. If you have another admin account on the PC, try logging in with that. If it works, your own profile is damaged. You can copy your files from C:\Users\yourname to the other account's folder and then delete the old profile.

If there's no other account, you can create one from Safe Mode. Open Command Prompt as Admin and type:

net user NewUser /add

net localgroup administrators NewUser /add

And if that still doesn't fix it — I mean, the PC boots to a blue screen even in Safe Mode — you're looking at a hardware issue. Memory or hard drive failure can corrupt system files. Run a memory test: type mdsched.exe in the Run box (Windows key + R) and let it check your RAM. Also check your hard drive health with chkdsk c: /r from the Command Prompt. If either finds errors, you need to replace that part before reinstalling Windows.

Bottom line: this error is almost always fixable without reinstalling. Start with Safe Mode, uninstall the update, then move to System Restore, then driver repair. You'll be back in your desktop in under an hour.