Can not log into Windows 10 after an update

MikeLud1

IPCT Contributor
Apr 5, 2017
2,581
4,679
Brooklyn, NY
My Windows 10 PC had pending updates that need to be restated. I had a 30 seconds power outage and the updates happened. After the updates finished and booted up to the login screen now I can not log in using my PIN. I can enter the PIN then it goes to the normal spinning wheel and stays there.
Does anyone know a way to get back logged in.

Thanks
Mike
 
Have you tried booting into Safe Mode with Command Prompt Mike?

If so and you can get in, try running CMD as Admin and using the DISM commands, namely the DISM Restore and Cleanup commands (not much point using the file checking one) when you know there's an issue. The DISM commands should replace Windows Key Files with perfect versions from the Web or a Backup file. If that fails, you could try Windows Restore as I think Windows Updates create a restore point but whether that works from Safe Mode, I'm not sure. I don't know if there's any way of creating a bootable restore file to allow you to access restore points from outside windows.

I think there's also a way of accessing rollback to last known gogd config on bootup, but you'll need the web on that one. Even then, when I used it in the past, it was very hit and miss. I'd regard this one as a last resort as it could stop you booting entirely.

Personally I use Shadow Protect SPX these days but it's a bit late once you already have an issue.
 
I am sort of login using RDP. I think I know what might be causing my login issue, it is the %temp% folder be loaded up with a ton of temp file. I had this happen once before if the %temp% folder has to many temp file it takes forever to login. Since I am logged in I am deleting all the temp files

1760814659240.png
 
Last edited:
Keep us posted. Since you are remoted in, you should temporarily disable updates so you don't run into more problems if you have to reboot. If all that still fails, I agree to try safe mode and see if that works.
 
I am back to normal, there were over 2.2M files in the %temp% folder, it took over a hour and a half to delete them all. I am pretty sure that was causing my login issue.