Windows 10: Windows takes two hours to boot every reboot. Goes to spinning circles

Page 1 of 48 12311 ... LastLast

  1. Posts : 165
    Windows 10 Version 1511 (10586.164)
       11 Mar 2016 #1

    Windows takes two hours to boot every reboot. Goes to spinning circles


    I have a very limiting issue. I've had Windows 10 for months and all has been fine. Then all of a sudden about 5 days ago I rebooted my machine and it passed by the normal logon screen and went straight to a blue screen (not a BSD screen, just a normal blue background color screen) with dots spinning in a circle. If I wait about two hours it will finally end and give me my logon screen.

    Once in Windows, I have no errors and and if I check my "Updates" status, there are no errors. So, once in, I create an Image of my C: Drive thinking that now I have a good and bootable OS. But on reboot, I get the spinning circles. If I restore C: with the image, I get the spinning circles.

    In desperation I've downloaded "WinShowHideUpdates" and hidden every update in the list. I reboot and the same thing, two hours to boot while stuck on spinning circles.

    So I'm really stuck. I can't update anything that requires a reboot unless I want to waste the rest of the day. Has anyone seen this issue? Is there a way to stop it?
      My ComputerSystem Spec


  2. Posts : 11,951
    W10Prox64
       11 Mar 2016 #2

    RobH2 said: View Post
    I have a very limiting issue. I've had Windows 10 for months and all has been fine. Then all of a sudden about 5 days ago I rebooted my machine and it passed by the normal logon screen and went straight to a blue screen (not a BSD screen, just a normal blue background color screen) with dots spinning in a circle. If I wait about two hours it will finally end and give me my logon screen.

    Once in Windows, I have no errors and and if I check my "Updates" status, there are no errors. So, once in, I create an Image of my C: Drive thinking that now I have a good and bootable OS. But on reboot, I get the spinning circles. If I restore C: with the image, I get the spinning circles.

    In desperation I've downloaded "WinShowHideUpdates" and hidden every update in the list. I reboot and the same thing, two hours to boot while stuck on spinning circles.

    So I'm really stuck. I can't update anything that requires a reboot unless I want to waste the rest of the day. Has anyone seen this issue? Is there a way to stop it?
    Hi RobH2 and welcome to Tenforums.
    Question: Is this system an "update" from W7/W8.x, or a clean install of W10?
    You could try running sfc /scannow to see if your system files are in good shape.
    Turn off Fast Startup, if it's not off already. (This option may not appear at all on a desktop anymore.)
    Perhaps a repair install with an in-place upgrade might get things back to normal.
    Let us know how it goes.
      My ComputerSystem Spec


  3. Posts : 165
    Windows 10 Version 1511 (10586.164)
    Thread Starter
       11 Mar 2016 #3

    simrick said: View Post
    Hi RobH2 and welcome to Tenforums.
    Question: Is this system an "update" from W7/W8.x, or a clean install of W10?
    You could try running sfc /scannow to see if your system files are in good shape.
    Turn off Fast Startup, if it's not off already. (This option may not appear at all on a desktop anymore.)
    Perhaps a repair install with an in-place upgrade might get things back to normal.
    Let us know how it goes.
    Thanks for the fast response. It's a clean install. I've spent dozens of hours reading and diagnosing. I've run 'scannow' and it only reports a couple of minor issues. 'Fast Startup' is OFF. I've run a repair install several times. I can try it again.

    This is a tough one.
      My ComputerSystem Spec


  4. Posts : 11,951
    W10Prox64
       11 Mar 2016 #4

    A difficult one indeed!


    RobH2 said: View Post
    Thanks for the fast response. It's a clean install. I've spent dozens of hours reading and diagnosing. I've run 'scannow' and it only reports a couple of minor issues. 'Fast Startup' is OFF. I've run a repair install several times. I can try it again.

    This is a tough one.
    Would you please run this command in an admin command prompt and paste the results here in a CODE BOX for me? I'd like to see the errors:
    Code:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    (I don't want the whole cbs log.)

    Have you downloaded the latest ISO from MSTechBench for the repair install, or are you using an older version?

    Have you tried a dism repairhealth? (although a repair install should do the same thing, if not better...)

    What about the health of your drive? Have you run chkdsk?

    Were there any other drives attached to your system when you did the clean install? This includes secondary internal drives, external drives, flash drives, etc.

    I don't see where you've indicated that you've had any BSODs, but, you might try installing WhoCrashed, run it, and see if there are any dump files available for analysis.

    Please let me know if you need any links for info on these things. Normally I provide them in the initial post, but it appears that you are familiar with all this stuff.

    EDIT: Can you post a screenshot of your Disk Management window? What do you see in the Reliability History, anything?
    Last edited by simrick; 11 Mar 2016 at 08:32. Reason: added Disk Management request
      My ComputerSystem Spec


  5. Posts : 165
    Windows 10 Version 1511 (10586.164)
    Thread Starter
       11 Mar 2016 #5

    Will do most of this tonight as I need to get work done and can't risk having to reboot.

    In the meantime:

    1. Downloading from MSTechBench now. Will try repair tonight.
    2. All 6 of my drives report that they are in good shape and SMART is good.
    3. Clean install had only a CD drive attached.
    4. I don't get any BSOD's or any crashes. All is fine and rock solid. I just can't boot to my login screen without getting "spinning circles" and two hours for that to finish and give me my login. After that, all is perfectly fine and stable.

    Code:
    PS C:\WINDOWS\system32> findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop
    out-file : Could not find a part of the path 'C:\WINDOWS\system32\%userprofile%\Desktop\sfc
    At line:1 char:1
    + findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\s ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    Click image for larger version. 

Name:	RH_DeviceManager_20160311.png 
Views:	8 
Size:	30.0 KB 
ID:	68853

    I didn't realize 'Reliability Monitor' existed. This is potentially a very handy tool. I came straight from Windows 7 to Win 10. Did Windows 7 have this? If so, I don't know how I could have missed it as I do spend a lot of time under the hood, not like you, but more than most people. It looks like 'Adobe Acrobat DC' is having some issues. This could be it. Windows may be trying to repair it on every boot. Is there another log for dump file that might corroborate that and show that it's what's holding the boot process up? I've attached an RM screenshot:
    Click image for larger version. 

Name:	RM_3_11_2016-,-10_17_39-AM.jpg 
Views:	10 
Size:	129.9 KB 
ID:	68855

    Now I have something to explore. I'll report in later. Let me know your thoughts.

    Thank you.... Rob
      My ComputerSystem Spec


  6. Posts : 11,951
    W10Prox64
       11 Mar 2016 #6

    RobH2 said: View Post
    Will do most of this tonight as I need to get work done and can't risk having to reboot.
    That's fine, no rush. I have some work to get done today as well.

    RobH2 said: View Post
    In the meantime:

    1. Downloading from MSTechBench now. Will try repair tonight.
    I would first remove Adobe DC Reader, and any 3rd party AV; also monitoring tools (i.e. Speccy, etc.) Of course, I am hoping you're just using Defender, because uninstalling a 3rd party AV will require a "potential" 2-hour reboot....Please, let's discuss things before you start the repair install/in-place upgrade.

    RobH2 said: View Post
    2. All 6 of my drives report that they are in good shape and SMART is good.
    Just to be sure - chkdsk on the OS drive came back okay? Because SMART can be fine and chkdsk may still be needed. You can run chkdsk while in the OS without the boxes checked for repair. As long as it's a "read-only" chkdsk, you won't need a reboot.

    RobH2 said: View Post
    3. Clean install had only a CD drive attached.
    Perfect!

    RobH2 said: View Post
    4. I don't get any BSOD's or any crashes. All is fine and rock solid. I just can't boot to my login screen without getting "spinning circles" and two hours for that to finish and give me my login. After that, all is perfectly fine and stable.
    Yes, I figured that. Still would be good to run it, to see if there are any problem logs available.

    RobH2 said: View Post
    Code:
    PS C:\WINDOWS\system32> findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop
    out-file : Could not find a part of the path 'C:\WINDOWS\system32\%userprofile%\Desktop\sfc
    At line:1 char:1
    + findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\s ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    IDK-It seems the command wasn't complete - did you get the part where it makes the "sfcdetails.txt" file on your desktop? Because what you've posted here is not what I expected. Here is the code again:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    I would like the contents of that text file it puts on your desktop for evaluation.

    RobH2 said: View Post

    Click image for larger version. 

Name:	RH_DeviceManager_20160311.png 
Views:	8 
Size:	30.0 KB 
ID:	68853

    I didn't realize 'Reliability Monitor' existed. This is potentially a very handy tool. I came straight from Windows 7 to Win 10. Did Windows 7 have this? If so, I don't know how I could have missed it as I do spend a lot of time under the hood, not like you, but more than most people. It looks like 'Adobe Acrobat DC' is having some issues. This could be it. Windows may be trying to repair it on every boot. Is there another log for dump file that might corroborate that and show that it's what's holding the boot process up? I've attached an RM screenshot:
    Click image for larger version. 

Name:	RM_3_11_2016-,-10_17_39-AM.jpg 
Views:	10 
Size:	129.9 KB 
ID:	68855
    Absolutely a very handy tool! I believe it did indeed exist in W7 (I can't verify that atm, but I will next time I'm in the VM). Acrobat DC is a problem, yes. I would uninstall it for now.

    So, the yellow triangles all correspond to Adobe DC Reader and reboots? What are you seeing for failures with the red Xs? I am not sure where to go for a log; this is usually as far as I need to go when trouble-shooting.

    What AV are you using?

    RobH2 said: View Post
    Now I have something to explore. I'll report in later. Let me know your thoughts.

    Thank you.... Rob
    Yes, no rush. Let's just make sure we touch base before you start the repair install.
      My ComputerSystem Spec


  7. Posts : 165
    Windows 10 Version 1511 (10586.164)
    Thread Starter
       11 Mar 2016 #7

    I would first remove Adobe DC Reader, and any 3rd party AV; also monitoring tools (i.e. Speccy, etc.) Of course, I am hoping you're just using Defender, because uninstalling a 3rd party AV will require a "potential" 2-hour reboot....Please, let's discuss things before you start the repair install/in-place upgrade.
    My AV is AVG. I do have Speccy and another snooper that came with my Corsair liquid chillers called, "Corsair Link 4." Since I'm going to be doing these tasks at 1AM and you won't be around, what do we need to "discuss" prior to doing the "repair install/in-place upgrade?"

    Just to be sure - chkdsk on the OS drive came back okay?
    All 6 disks passed CHDKSK with no issues.

    Code:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    (I don't want the whole cbs log.)
    Can't get this to run. I've tried a bunch of variations and no luck. I copied cbs.log to my temp folder incase it was a permissions issue. I also "TookOwnership" of the file, no help. I wasn't getting any permission errors but just TookOwnership anyway. Here's what I've tried.
    findstr /c:[SR] %windir%\Logs\CBS\CBS.log >sfcdetails.txt


    findstr /c:[SR] c:\Windows\Logs\CBS\CBS.log >sfcdetails.txt


    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt


    findstr /c:[SR] Temp\CBS.log >sfcdetails.txt >%userprofile%\Desktop\sfcdetails.txt


    findstr /c:[SR] Temp\CBS.log


    notepad c:\temp\cbs.log


    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >nvision4d\Desktop\sfcdetails.txt

    Here's the error I get:
    PS C:\> findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
    out-file : Could not find a part of the path 'C:\%userprofile%\Desktop\sfcdetails.txt'.
    At line:1 char:1
    + findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdet ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: ( [Out-File], DirectoryNotFoundException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand


    So, I guess the main question is what do you want me to know before I do the "repair install/in-place upgrade?" It won't matter if I make a mess. I create a full Image every morning at 7AM and have the one from today. So I can quickly get back to where I was when today started out. However, I've done a bunch of configuration with IOS Development and Unity today. I'd like to have not wasted that effort. Will the "repair install/in-place upgrade" wreck that?

    Edit: Forgot to add this. Same error on 3 occasions from WhoCrashed. No others:

    On Wed 3/9/2016 3:54:19 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030916-32421-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x81)
    Bugcheck code: 0x124 (0x7, 0xFFFFE000DE42AAE8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My ComputerSystem Spec

  8.    11 Mar 2016 #8

    RobH2 said: View Post
    I've done a bunch of configuration with IOS Development and Unity today. I'd like to have not wasted that effort.Will the "repair install/in-place upgrade" wreck that?
    No.

    Do it.

    Then upload the .dmp file as WhoCrashed isn't that reliable.
      My ComputerSystem Spec


  9. Posts : 11,951
    W10Prox64
       11 Mar 2016 #9

    RobH2 said: View Post
    My AV is AVG. I do have Speccy and another snooper that came with my Corsair liquid chillers called, "Corsair Link 4." Since I'm going to be doing these tasks at 1AM and you won't be around, what do we need to "discuss" prior to doing the "repair install/in-place upgrade?"
    See further below...

    RobH2 said: View Post
    All 6 disks passed CHDKSK with no issues.
    Okay good.

    RobH2 said: View Post
    Can't get this to run. I've tried a bunch of variations and no luck. I copied cbs.log to my temp folder incase it was a permissions issue. I also "TookOwnership" of the file, no help. I wasn't getting any permission errors but just TookOwnership anyway. Here's what I've tried.
    findstr /c:[SR] %windir%\Logs\CBS\CBS.log >sfcdetails.txt

    findstr /c:[SR] c:\Windows\Logs\CBS\CBS.log >sfcdetails.txt

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

    findstr /c:[SR] Temp\CBS.log >sfcdetails.txt >%userprofile%\Desktop\sfcdetails.txt

    findstr /c:[SR] Temp\CBS.log

    notepad c:\temp\cbs.log

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >nvision4d\Desktop\sfcdetails.txt

    Here's the error I get:
    PS C:\> findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
    out-file : Could not find a part of the path 'C:\%userprofile%\Desktop\sfcdetails.txt'.
    At line:1 char:1
    + findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdet ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (:) [Out-File], DirectoryNotFoundException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    It appears you're missing the second set of quotes where it tells where to make the file:

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    Yeah, you won't get access to the CBS log where it resides; you have to copy/paste it somewhere to be able to open it in notepad. But the entire log will be huge, and I only wanted to see the searched results.
    Maybe try copying and pasting the command from the tutorial? (see option #5)

    RobH2 said: View Post
    So, I guess the main question is what do you want me to know before I do the "repair install/in-place upgrade?" It won't matter if I make a mess. I create a full Image every morning at 7AM and have the one from today. So I can quickly get back to where I was when today started out. However, I've done a bunch of configuration with IOS Development and Unity today. I'd like to have not wasted that effort. Will the "repair install/in-place upgrade" wreck that?
    No, as lx07 said, it shouldn't mess with any of that.
    I have no experience with Corsair Link4 - how much effort would be required to uninstall it before doing the repair install and then put it back? Is there a profile that can be saved or something? I'd also like to see Adobe Reader DC, AVG and Speccy uninstalled as well. And, since you have daily images, that answered my next question.

    RobH2 said: View Post
    Edit: Forgot to add this. Same error on 3 occasions from WhoCrashed. No others:

    On Wed 3/9/2016 3:54:19 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030916-32421-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x81)
    Bugcheck code: 0x124 (0x7, 0xFFFFE000DE42AAE8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Looking here, (Parameter 1 = 0x7) it appears there may also be a boot issue going on, but I can't be positive because, as lx07 said, WhoCrashed can be unreliable at times. If you do follow the BSOD posting instructions and upload the dump, I will see if we can get a BSOD analyst to have a look at it for you.

    p.s. we'll see how late I am around tonight; have lots to do...;)
      My ComputerSystem Spec


  10. Posts : 165
    Windows 10 Version 1511 (10586.164)
    Thread Starter
       11 Mar 2016 #10

    OK, I'm getting setup to do a "repair install/in-place." One thing that I can't do is disable 'SecureBoot' right now as then I'll be held hostage for two hours to get back in. So, I assume I can change that on my first reboot after the repair if necessary.

    Wish me luck.
      My ComputerSystem Spec


 
Page 1 of 48 12311 ... LastLast

Related Threads
Solved Spinning Dots at Boot Up in General Support
I have win 10 x64 on a Dell XPS 8700. It had Win 8.1. Been on Win 10 since release. Today my son went to reboot the computer and at boot, just got spinning dots. He turned it off, same thing. Got to a diagnostic and it said it could not repair....
Solved Boot up takes 2 hours! in Performance & Maintenance
Alright so after long hours of research I have narrowed down y problem. Long story short I messed with the permissions of my C:\Windows directory and sure enough it has caused issues. Now my computer when powering on will show a light blue screen...
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...
So, I've encountered this issue lately where Windows 10 takes considerably longer to boot than before. (Usually 4 to 5 minutes) It used to boot under 30 seconds before so I don't know what went wrong here. So, the screen with the Windows logo...
I installed Windows 10 fairly quickly on my laptop, and firlgured it'd be just as painfree to do so on my desktop, but the install was stuck at 'Copying files - 48%' for hours. I figured that since it was just copying files, I would just restart the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:50.
Find Us