Win 10 64 bit (1703) boot time too long!

Page 6 of 7 FirstFirst ... 4567 LastLast

  1. Posts : 165
    win10 pro 64 bit
    Thread Starter
       #51

    No, I did not run xbootmgr.exe!
    Here is what I have under GlobalLogger:
    Attached Thumbnails Attached Thumbnails Win 10 64 bit (1703) boot time too long!-logger.gif  
      My Computer


  2. Posts : 857
    windows 10
       #52

    Add these keys with values in decimal:

    BufferSize = 1024MinimumBuffers = 300MaximumBuffers = 600

    Then take another boot trace, and preferably choose to save the ELT file in an external storage (USB flashdisk).
      My Computer


  3. Posts : 165
    win10 pro 64 bit
    Thread Starter
       #53

    Sorry, I can't figure out how that works.
    When I right-click on GlobalLogger and select New>Key, it creates a new folder below the E51BB... folder.
      My Computer


  4. Posts : 857
    windows 10
       #54

    In the right side of the window, right click on the blank space the choose New > DWORD (32 bits). Then create the 3 keys with the indicated values

    Win 10 64 bit (1703) boot time too long!-capture.png
      My Computer


  5. Posts : 165
    win10 pro 64 bit
    Thread Starter
       #55

    OK, that I did understand, thanks.
    Ed
      My Computer


  6. Posts : 857
    windows 10
       #56

    After you complete this operation, take another boot trace and choose the usb disk as destination for the ETL file.
      My Computer


  7. Posts : 165
    win10 pro 64 bit
    Thread Starter
       #57

    I did exactly per your instructions but got the same error message.
    Sorry, don't mean to be a nuisance.
    Ed
      My Computer


  8. Posts : 857
    windows 10
       #58

    Anyway. Send me the boot trace I'll try to grab some informaton.
      My Computer


  9. Posts : 165
    win10 pro 64 bit
    Thread Starter
       #59
      My Computer


  10. Posts : 857
    windows 10
       #60

    The Session init phase has the same duration and the reload catalogue event for the "AtihdWT6.sys" driver still occurs. If you check the Windows events graph I guess you'll see the Error ID 3004.

    what I suggest:

    1. Uninstall and Reinstall the ATI video driver
    2. Uninstall avira, there is a lot of disk I/O generated by Avira AV. when you uninstall Avira Windows Defender will take over.
    3. run this command to optimize the Prefetcher : "xbootmgr -trace boot -prepSystem -verboseReadyBoot"

    The last command can take several hourse, I suggest you to use this to tool to allow autologon and not have to enter your credential at each reboot. cause this command will restart your system 6 times. you can download this tool from here
      My Computer


 

  Related Discussions
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 02:50.
Find Us




Windows 10 Forums