Windows Booting very slow after 2004 update ,

Anonymous
2020-06-07T04:38:08+00:00

My Windows 10 starting on very slow after windows 10 , 2004 update now what i do ?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

128 answers

Sort by: Newest
  1. Anonymous
    2020-11-20T01:47:22+00:00

    @DanDScan - that is interesting that it made such a dramatic change. As the C: disk is the boot disk (and should always be treated as "non-removable"), I am surprised that any "autorun" functionality is used at all!  Did you say that Kapersky scan recommended that change? A reference would be useful.

    Altering the registry can be dangerous. It is best to use an official utility for "autorun" changes. This official Microsoft tool (autoruns) developed by Mark Russinnovich is very good, and a right click on entries will remove registry entries as required. This is especially useful for those hard to detect items/drivers/bloat apps that start up that you do not need, and also detects stranded items from faulty uninstalls (that can cause added delays as items are searched for during startup).

    https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-11-17T15:12:33+00:00

    I have tried most of the solutions proposed for the long boot time with version 2004 and none has worked. I have now found a solution that does work on my computer. From login to useable screen was taking about 6 minutes and now takes 75 seconds which is the same as with previous versions of Windows 10.

    Machine: Laptop, Intel i5, single HDD, Windows 10 Pro 2004

    In the registry I have disabled Autorun for the HDD – see Microsoft’s documentation in the reference at the end of this post. One difference is that I have this key under HKEY_LOCAL_MACHINE rather than Microsoft’s recommendation of HKEY_CURRENT_USER.

    Using Regedit create the following key (if it’s not already there):

    HKEY_LOCAL_MACHINE

        Software

          Microsoft

             Windows

                CurrentVersion

                   Policies

                     Explorer

    Then create NoDriveTypeAutoRun as REG_DWORD with value 0x08 (decimal 8)

    The possible values are:

    Bit Number       Bitmask Constant                     Description

    0x04             DRIVE_REMOVEABLE         Disk can be removed (such as a floppy disk).

    0x08             DRIVE_FIXED                       Disk cannot be removed from drive (a hard disk).

    0x10             DRIVE_REMOTE                  Network drive.

    0x20             DRIVE_CDROM                    CD-ROM drive.

    0x40             DRIVE_RAMDISK                 RAM disk.

    All other solutions proposed under earlier posts have worked for some users but not all and I suspect this solution will be no different. Still, this solution has zero cost, is easy to apply (if you are used to using Regedit) and is reversible. Hopefully, a few more users will find themselves dug out of the slow-boot hole.

    Note:

    I have not tested with Microsoft’s recommendation of using HKEY_CURRENT_USER.

    Reference:

    https://docs.microsoft.com/en-us/windows/win32/shell/autoplay-reg

    Acknowledgement:

    Kaspersky’s Total Security ‘Vulnerability Scan’ tool

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-11-15T23:33:43+00:00

    Glad to be of help

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-11-15T23:22:25+00:00

    Cannot thank you enough - as does Geek Squad.  With your information computer is running well and no more password amnesia.  Thanks again for taking time to address this issue.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-11-14T12:51:44+00:00

    Hi @Jaavenor - thanks for the feedback, I hope they are successful with your repair/fix at Geek Squad.

    As regards the Lenovo Desktop PC and the 0xC1900101 - this can be several causes - check if you get a "sub-code" like 0x20017 after the main error code, for instance 0x20017 can mean it is a driver issue. Graphics drivers have caused trouble with several Feature Upgrades in the last, and I am sure that certain (older or out of date) Intel and NVIDIA drivers can cause update issues. A sub-code of 0x30017 might mean that a third-party Anti-Virus program is blcking some key part of the update process. I did see that there was a big list of Lenovo models that have issues with 2004 update, and I don't think they have all been resolved yet. I suspect that many models will still have driver conflicts. Have you checked the Device Manager list to see if any devices have yellow flags?

    You can download the Microsoft update log analysis tool from the link below, install it and run it after an update failure, and check out its report. The sub-codes it finds might give you more insight, that you can pass to Lenovo support for advice.

    https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

    There is a list of stuff here, many of which I suspect you already tried, but ignore the item 7 for "chkdsk" as they got the command syntax wrong anyway (no space after the command and the /f switch option, so you would get an error)!

    https://support.microsoft.com/en-us/windows/get-help-with-windows-10-upgrade-and-installation-errors-ea144c24-513d-a60e-40df-31ff78b3158a

    Was this answer helpful?

    0 comments No comments