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

Page 37 of 48 FirstFirst ... 27353637383947 ... LastLast

  1. Posts : 2,034
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       31 Mar 2016 #361

    You guys make me blush but thank you.
    The old version from tech bench should work as I am using it.
    Steve's suggestion is the same as if you mount the install.wim.
    If all else fails, try to copy just the install.wim to desktop then from admin command, copy and paste then run:
    1. Dism /Online /Cleanup-Image /StartComponentCleanup
    2. Dism /Online /Cleanup-Image /CheckHealth
    3. DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:%USERPROFILE%\Desktop\Install.wim:1 /LimitAccess


    NOTE:
    #1 will take a while to run.
      My ComputerSystem Spec


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

    I attempted this:

    Download the the Installation ISO: Windows 10 Download - Tech Bench
    1.Mount the ISO and copy install.wim from the source folder to Desktop
    2.Create a folder on desktop: mount

    Open Admin Command prompt, copy/paste each line and run:
    1.Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount

    ...but get an error:

    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    Error: 2
    The system cannot find the file specified.


    I tried it by using the command as is and replacing
    %USERPROFILE% with my profile 'NVision4D'.

    I'll try this now:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:%USERPROFILE%\Desktop\Install.wim:1 /LimitAccess
      My ComputerSystem Spec


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

    Looking at this: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:%USERPROFILE%\Desktop\Install.wim:1 /LimitAccess
    does it matter that the 'Temp' folder I created is not in the string? And, should I leave %USERPROFILE% or replace it?

    Edit:
    It appears not, it's running now.
      My ComputerSystem Spec


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

    Same error:

    C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:%USERPROFILE%\Desktop\Install.wim:1 /LimitAccess


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================100.0%==========================]


    Error: 1392


    The file or directory is corrupted and unreadable.


    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
      My ComputerSystem Spec


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

    After limited success it failed again with 1392:

    -----------------------------------------------
    This completed: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    No component store corruption detected.
    The operation completed successfully.


    This failed: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================100.0%==========================]


    Error: 1392


    The file or directory is corrupted and unreadable.


    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    -----------------------------------
      My ComputerSystem Spec


  6. Posts : 2,034
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       31 Mar 2016 #366

    Try what I suggested above (post #361)
      My ComputerSystem Spec


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

    topgundcp said: View Post
    Try what I suggested above (post #361)
    I did. Same result same error.

    You mentioned that #1 would take a while to run. I only takes about 2-seconds to return this:
    ----------------------------------
    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /StartComponentCleanup


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [=========== 20.0% ]
    The operation completed successfully.
    --------------------------------

    Is this an indication that it failed to run properly because it only took 2-seconds even though it says "successfully?"
      My ComputerSystem Spec


  8. Posts : 1,683
    Windows 10 x86 14383 Insider Pro and Core 10240
       31 Mar 2016 #368

    I've read thru this thread this evening - all 37 pages. Fascinating.
    When reading the discussion of .wim and .esd as component sources for DISM and their minor build upgrade numbers e.g. 10586.164, and how to tell what the version from techbench was, there's a way to find out, if you have 7-zip and regedit.

    Pictures speak volumes so here's the Regedit from my current OS - the full key path is visible in the screenshot - note the last entry UBR, value 164:

    Click image for larger version. 

Name:	Screenshot (40).png 
Views:	7 
Size:	169.0 KB 
ID:	72464

    Now I have the slow ring update to build 14295 waiting on my drive to be installed, so navigating to J:\$WINDOWS.~BT\Sources\Install.ESD, and right-clicking 7-zip to open the archive,
    I could check the [1].xml to see what the 4 indexed images contained:

    Code:
    <WIM>  <TOTALBYTES>2172814752</TOTALBYTES>
      <IMAGE INDEX="1">
        <DIRCOUNT>94</DIRCOUNT>
        <FILECOUNT>965</FILECOUNT>
        <TOTALBYTES>213985667</TOTALBYTES>
        <HARDLINKBYTES>0</HARDLINKBYTES>
        <CREATIONTIME>
          <HIGHPART>0x01D18223</HIGHPART>
          <LOWPART>0x65F721B2</LOWPART>
        </CREATIONTIME>
        <LASTMODIFICATIONTIME>
          <HIGHPART>0x01D18AC2</HIGHPART>
          <LOWPART>0x75201063</LOWPART>
        </LASTMODIFICATIONTIME>
        <WIMBOOT>0</WIMBOOT>
        <NAME>Windows Setup Media</NAME>
        <DESCRIPTION>Windows Setup Media</DESCRIPTION>
      </IMAGE>
      <IMAGE INDEX="2">
        <DIRCOUNT>2999</DIRCOUNT>
        <FILECOUNT>13572</FILECOUNT>
        <TOTALBYTES>1168590687</TOTALBYTES>
        <HARDLINKBYTES>477408408</HARDLINKBYTES>
        <CREATIONTIME>
          <HIGHPART>0x01D1821D</HIGHPART>
          <LOWPART>0x24A26467</LOWPART>
        </CREATIONTIME>
        <LASTMODIFICATIONTIME>
          <HIGHPART>0x01D18AC2</HIGHPART>
          <LOWPART>0x75298913</LOWPART>
        </LASTMODIFICATIONTIME>
        <WIMBOOT>0</WIMBOOT>
        <WINDOWS>
          <ARCH>0</ARCH>
          <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
          <EDITIONID>WindowsPE</EDITIONID>
          <INSTALLATIONTYPE>WindowsPE</INSTALLATIONTYPE>
          <PRODUCTTYPE>WinNT</PRODUCTTYPE>
          <PRODUCTSUITE></PRODUCTSUITE>
          <LANGUAGES>
            <LANGUAGE>en-GB</LANGUAGE>
            <FALLBACK LANGUAGE="en-GB">en-US</FALLBACK>
            <DEFAULT>en-GB</DEFAULT>
          </LANGUAGES>
          <VERSION>
            <MAJOR>10</MAJOR>
            <MINOR>0</MINOR>
            <BUILD>14295</BUILD>
            <SPBUILD>1000</SPBUILD>
            <SPLEVEL>0</SPLEVEL>
          </VERSION>
          <SYSTEMROOT>WINDOWS</SYSTEMROOT>
        </WINDOWS>
        <NAME>Microsoft Windows PE (x86)</NAME>
        <DESCRIPTION>Microsoft Windows PE (x86)</DESCRIPTION>
        <FLAGS>9</FLAGS>
      </IMAGE>
      <IMAGE INDEX="3">
        <DIRCOUNT>3029</DIRCOUNT>
        <FILECOUNT>14010</FILECOUNT>
        <TOTALBYTES>1302614980</TOTALBYTES>
        <HARDLINKBYTES>546828534</HARDLINKBYTES>
        <CREATIONTIME>
          <HIGHPART>0x01D1821D</HIGHPART>
          <LOWPART>0x53A0BFAA</LOWPART>
        </CREATIONTIME>
        <LASTMODIFICATIONTIME>
          <HIGHPART>0x01D18AC2</HIGHPART>
          <LOWPART>0x7531C68A</LOWPART>
        </LASTMODIFICATIONTIME>
        <WIMBOOT>0</WIMBOOT>
        <WINDOWS>
          <ARCH>0</ARCH>
          <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
          <EDITIONID>WindowsPE</EDITIONID>
          <INSTALLATIONTYPE>WindowsPE</INSTALLATIONTYPE>
          <PRODUCTTYPE>WinNT</PRODUCTTYPE>
          <PRODUCTSUITE></PRODUCTSUITE>
          <LANGUAGES>
            <LANGUAGE>en-GB</LANGUAGE>
            <FALLBACK LANGUAGE="en-GB">en-US</FALLBACK>
            <DEFAULT>en-GB</DEFAULT>
          </LANGUAGES>
          <VERSION>
            <MAJOR>10</MAJOR>
            <MINOR>0</MINOR>
            <BUILD>14295</BUILD>
            <SPBUILD>1000</SPBUILD>
            <SPLEVEL>0</SPLEVEL>
          </VERSION>
          <SYSTEMROOT>WINDOWS</SYSTEMROOT>
        </WINDOWS>
        <NAME>Microsoft Windows Setup (x86)</NAME>
        <DESCRIPTION>Microsoft Windows Setup (x86)</DESCRIPTION>
        <FLAGS>2</FLAGS>
      </IMAGE>
      <IMAGE INDEX="4">
        <DIRCOUNT>14243</DIRCOUNT>
        <FILECOUNT>78684</FILECOUNT>
        <TOTALBYTES>9695607189</TOTALBYTES>
        <HARDLINKBYTES>4415570446</HARDLINKBYTES>
        <CREATIONTIME>
          <HIGHPART>0x01D18221</HIGHPART>
          <LOWPART>0xD7A4E470</LOWPART>
        </CREATIONTIME>
        <LASTMODIFICATIONTIME>
          <HIGHPART>0x01D18AC2</HIGHPART>
          <LOWPART>0x753AA3C2</LOWPART>
        </LASTMODIFICATIONTIME>
        <WIMBOOT>0</WIMBOOT>
        <WINDOWS>
          <ARCH>0</ARCH>
          <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
          <EDITIONID>Professional</EDITIONID>
          <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
          <SERVICINGDATA>
            <GDRDUREVISION>0</GDRDUREVISION>
            <PKEYCONFIGVERSION>10.0.14295.1000;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
          </SERVICINGDATA>
          <PRODUCTTYPE>WinNT</PRODUCTTYPE>
          <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
          <LANGUAGES>
            <LANGUAGE>en-GB</LANGUAGE>
            <FALLBACK LANGUAGE="en-GB">en-US</FALLBACK>
            <DEFAULT>en-GB</DEFAULT>
          </LANGUAGES>
          <VERSION>
            <MAJOR>10</MAJOR>
            <MINOR>0</MINOR>
            <BUILD>14295</BUILD>
            <SPBUILD>1000</SPBUILD>
            <SPLEVEL>0</SPLEVEL>
          </VERSION>
          <SYSTEMROOT>WINDOWS</SYSTEMROOT>
        </WINDOWS>
        <NAME>Windows 10 Pro Technical Preview</NAME>
        <DESCRIPTION>Windows 10 Pro Technical Preview</DESCRIPTION>
        <FLAGS>Professional</FLAGS>
        <DISPLAYNAME>Windows 10 Pro Insider Preview</DISPLAYNAME>
        <DISPLAYDESCRIPTION>Windows 10 Pro Insider Preview</DISPLAYDESCRIPTION>
      </IMAGE>
      <ESD>
        
      </ESD>
    </WIM>
    Now if that wasn't enough, I opened image 4 within 7-zip, navigated to J:\$WINDOWS.~BT\Sources\Install.esd\4\Windows\System32\config\SOFTWARE - the software hive of the 14295 Windows image, copied it to my Documents folder, and from Regedit, imported the hive as 14295, and voila:

    Click image for larger version. 

Name:	Screenshot (41).png 
Views:	5 
Size:	148.8 KB 
ID:	72465

    The current version build properties in all their glory - in this case UBR value is 1000.

    Hope this proves helpful.

    One item of hardware that is often overlooked is/are Optical Drives - yet they are checked at POST, and loaded before bootup, often when they are when they are inactive and unloaded, or at other times, they are running with the bootable media for an install or a utility to troubleshoot a problem state. They may be in one of several different states of operation at different times.

    But they are almost the only mechanical device with somewhat exposed parts left in modern computers, with the exception of keyboards, and mechanical devices fail in many ways.

    I had a laptop that developed a problem - it started to take abnormally long to boot, and various odd glitches developed, and after weeks of searching, the DVD ribbon cable connecting the case to the carriage of the drive was observed to have kinks, some of which had rubbed off the insulating coating and were shorting to the aluminium case of the drive. Once the drive had been taken out, all of the problems vanished.

    They should be disconnected (easy enough even with most laptops!) and tests run to check out whether they are a problem, when there are intractable errors found on a system.

    MSINFO32 is also a useful tool in conjunction with Device Manager, and Task Manager showing the resource graphs for CPU. There is a section which deals with IRQ Conflicts and IRQ sharing. Often 2 devices will share one IRQ, sometimes 3. Disabling each device in a triplet in turn in Device Manager and watching the resources change may indicate a conflict. It can also be done for pairs of devices.
      My ComputersSystem Spec


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

    Fafhrd said: View Post
    I've read thru this thread this evening - all 37 pages. Fascinating.
    It thrills me that there are people like you guys who find this "fascinating." I know more about this deeper computer stuff than the average guy but not much more. I find it interesting and it gives me comfort that you guys who find this fascinating will be here when the rest of us are gone. You know how it all fits together. I just know tiny disjointed bits and pieces. I have to learn enough to keep my machines running so I can do what fascinates me, CGI.

    Having said that, I need to work and have to call it a day on this issue. We tried a lot of things but were unable to solve the problem. If I were never to peek under the hood or try to run 'sfc' you'd never know there was a problem. Nothing is currently malfunctioning and my machine is behaving nicely. However, I do realize that small issues can grow if left alone or ignored. One thing I cannot entertain doing is reinstall Windows right now in any way that would require me to reinstall all of my software.

    I have no less than 30 programs that are authorized and it takes me about two weeks to recover. I have to avoid that at all costs. So, if you run across anything that I can try to get DISM to complete, I'll try anything. I do want to solve it.

    Because everything we tried today generated the same Error:1392, I have to assume that something else is hanging things up. It's not where the 'install.wim' file resides. We tried it in various places, all with the same end result. Something else is common to all of the failures, something we haven't thought of yet or explored. But, I don't have the breadth of knowledge to diagnose it. All I can do is make crude guesses like this one.

    Let me know if you think of anything. And, the fact that you guys find this fascinating gives me hope that you'll figure out some brilliant way to solve this issue. Then we can have a party, I'll buy the beer...
      My ComputerSystem Spec


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

    I do need one thing. I need to delete this 'mount' folder from my desktop. Right click does not offer me 'eject' like when I mount an ISO to a drive letter. When I try to delete it I'm told it needs permission and I'm logged in as an Administrator. I don't know how to delete it.
      My ComputerSystem Spec


 
Page 37 of 48 FirstFirst ... 27353637383947 ... 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:49.
Find Us