Windows 10: Reboot takes 2-5 hours and no login prompt after sleep

Hello,
So yesterday I installed some updates on my computer, however when it was rebooting it sat there for about an hour doing nothing. Eventually I force turned it off and tried to reboot it, however it kept doing the same thing. I looked up any fixes I could find, the only thing I saw was to try and boot it in safe made (Ctrl-Alt-Del then holding shift while clicking restart) even that still just sat at the red loading screen with the dots spinning in circles. I force shut it down a few more times and retried it, admittedly a bad idea but I was getting pissed off, until I finally just let it sit there and finish, hoping it would have a time out feature. Well eventually it booted to the login prompt after 4 hours.

New issue is that whenever I close my laptop to put it to sleep, and then reopen it it looks fine but when I swipe away the cool picture, theres no login prompt. It looks just like the screen when you press ctrl alt delete. So I told it to do a regular restart, and upon rebooting it was stuck at the spinning dots on the red screen for 3 more hours before it booted.

How can I fix this? I seriously don't want to take hours to turn on my computer, and not be able to just put it to sleep.

Final info: I understand I can just turn off putting the computer to sleep when I close the lid, and just darken the screen. I've already done that, I'm looking for a more permanent fix.

:)

 

log in screen on loop

Hi Dominique!

I have also noticed the same thing that during startup when the computer gets stuck on this infinite login loop it helps to go 1 to 3 times to sleep mode. I posted about it on October 20th 2016 in this thread and since then it has always worked for me and
helped me to login without rebooting.

I have noticed that sometimes it is not consistent and I can login after going only one time to sleep mode. But like you said most of the time it takes 2 times sleep mode before the login succeeds.

For me it does not prompt for PIN code - I can login with my Microsoft account password. So it seemingly works also with password login.

Best regards

 

Windows 10 login issues after wake up from sleep

After updated the windows 10 anniversary update, these issues constantly appears to my PC:

1. After wake up from sleep, the login screen shows as usual, but no matter I input the correct or incorrect password, it will stuck on the circle spinning status for over 1 minute then go back to the login screen without any prompt or message displayed.
I also tried to connect to another WiFi access point or disable WiFi to rule out the network reason (I'm using WiFi instead of Ethernet connection). Nothing helps and I have to reboot to fix it.

2. After wake up from sleep, sometimes the login screen will not show, all I got is a black screen with moving cursor. Only reboot can fix it too.

These issues ONLY appears after wake up from sleep, neither reboot nor logout nor lock screen will lead to this issue, and ONLY appears after the anniversary update.

And I'm using Microsoft account to login my PC, hope this information can help.

 

Suggestions :
1. Do a system file check to look for corrupt files. It will try to do repair if any found.
Right click at Start button > click Command Prompt (Admin) > at the flashing prompt, copy/paste this.......
sfc /scannow

> press Enter.
It will take quite sometime.
When finished, it will give you one of the 3 reports...............(paraphrasing)
1. No integrity violation.
2. Found corrupt files and repair successful.
3. Found corrupt files but unable to repair.

If the report is #1, your solution lies elsewhere.
If the report is #2, check if your problems have been resolved.
If the report is #3, use this method................
In the same Command Prompt (Admin) windows, copy and paste this command...........

dism /online /cleanup-image /restorehealth

> press Enter.
Again it will take some time.
When finished, it will give you a report.


2. If the above does not fix the problem, do a repair install, also known as in-place install.
Here is the tutorial :
Repair Install Windows 10 with an In-place Upgrade

 

Thank you! running the scan now.

 

Scan didn't find any integrity violations. Is the repair install honestly the next best bet?

 

In my opinion, yes.
If you find the tutorial I posted earlier a little intimidating, have a look at the one I use myself, and once a while I also showed it to others in this forum............

Use this Tech Bench link and download the Windows 10 iso file:
https://www.microsoft.com/en-us/soft...brrWLRbagYCa0w

scroll down to Select Edition > click the pointer at the right and select Windows 10 > click Confirm.
click the pointer and select Language > make sure you pick the same language the computer is now running > click Confirm
select the bit version, 32 or 64-bit. Make sure you select the same bit version as the computer is now running.
at the bottom, click the pointer next to Save > click Save As > navigate to a folder of your choice > click the chosen folder > click Save
The iso will start downloading to your chosen folder.
When it is done, go to that folder > open the folder > right click at the iso file > click Mount > click Setup.exe
Installation will begin.
It will allow you to keep you files, settings and apps.
No product key is required.
Activation will be automatic.

 

Alright, thank you so much for your help! Downloading now, I'm probably gonna run it tonight overnight. I'll post tomorrow morning if it isn't fixed, if it is thank you again!

 

Good luck.

 

I've had the same problem since applying the updates on March 4. I called MS support several times and they said that it is normal for an update to take this long. I have restarted my PC at least 10 times now and it takes 2 hours to boot every time. I have also tried a system restore to the point just before the updates but even that didn't work.

 

...............I've had the same problem since applying the updates on March 4.............
Which update was that ?
If you were referring to the new Insider Preview build 14279, you are on a completely different issue.