Updates not working, it has been searching for updates for hours

Anonymous
2016-06-15T04:54:11+00:00

My PC is quite old and I have tried the microsoft fix it tool. The fix it tool never works. 

I have been trying to check for new updates from since yesterday (Tuesday 14th June) in the afternoon. It is now Wednesday morning (12 hours approx) and it is still checking. There is no error code, it is just checking for the updates.

I have no technical skills so please do not ask me any technical questions. I would just like a solution to this problem.

Thank you.

It is August now and my pc has been searching for updates for 1 week now. This is****ridiculous

Windows for home | Previous Windows versions | Windows update

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
Answer accepted by question author
lmacri 2,505 Reputation points
2016-06-16T12:03:51+00:00

My PC is quite old and I have tried the microsoft fix it tool. The fix it tool never works. 

I have been trying to check for new updates from since yesterday (Tuesday 14th June) in the afternoon. It is now Wednesday morning (12 hours approx) and it is still checking. There is no error code, it is just checking for the updates...

***** IMPORTANT NOTICE as of August 3, 2020 *****

Microsoft has announced they will be deactivating Windows Update on August 3, 2020 for computers with unsupported Windows operating systems that do not support SHA-2 code signing - see the 24-Jun-2020 Microsoft support article Windows Update SHA-1 Based Endpoints Discontinued for Older Windows Devices for more information.   Win XP and Vista users will likely see one of the following error codes when Windows Update is run after this date.

  • Error code 80072ee2 or 80244019: The device cannot connect to Windows Update.
  • Error code 8024402c: The device is unable to locate Windows Update.

Image

Unfortunately, this means that the instructions below to fix slow Windows Updates and automatically patch a Vista SP2 OS to end of extended support (11-Apr-2017) will no longer work.  After 03-Aug-2020, Vista SP2 users who are still missing security updates released prior to 11-Apr-2017 should read post # 9 in the VistaForums thread WinVista HomePremium-X86 (SP1) Reinstallation Question about using the **** Dism++ utility to patch Vista SP2 back to end of support.
___________________________________________________________________________

**** INSTRUCTIONS BELOW WILL NOT FIX WINDOWS UPDATES AS OF 03-AUG-2020 ****

Hi m#l:

There is a known issue on Vista SP2 computers where Windows Update can hang on "Checking for updates..." for several hours (or even days) without throwing an error message. This problem was first reported in August 2015 and these slow Windows Updates have become progressively worse over time. In June 2016, IT expert Dalai began posting lists of "speed up" patches (a small number of security updates for the Win32K.sys kernel mode driver, graphics components, and IE9) at http://wu.krelay.de/en/ that could be manually installed each month to fix this problem.    Here are step-by-step instructions for Dalai's solution:

REVISED for the JUNE 2017 Patch Tuesday (valid as of July 2020):

  1. Disable automatic Windows Updates [Windows Update | Change settings | Important updates | Never check for updates (not recommended)] and re-boot to terminate any Windows Update sessions currently running in the background on your system.
  2. Search your installed updates at Control Panel | Programs and Features | View Installed Updates to see if any of the following "speed up" patches are missing from your system: KB3205638 (rel. 13-Dec-2016); KB4012583 (rel. 14-Mar-2017); KB4015380 (rel. 11-Apr-2017); KB4019204 (rel. 09-May-2017).  If IE9 is installed then KB4018271 (the 09-May-2017 cumulative security update for IE9) is also required. When searching, enter the full KB number in the search box (e.g., "KB3205638" and not a partial string like "3205638".
  3. Download the standalone installers (.msu files) for any missing "speed up" patches from the the Microsoft Update Catalog and save them to your Windows desktop using the download links in Note 1.  Use the Vista x86 installer if you have a 32-bit OS; use the Vista x64 installer if you have a 64-bit OS. See Note 2 if you have problems downloading the .msu installers.
  4. Double-click to run each .msu standalone installer.  Re-boot after all .msu installers have run to completion unless the installation wizard for one of the installers specifically requests a re-boot to finish the installation. See Notes 3 and 4 if you have problems running the .msu installers.
  5. Once all missing "speed up" patches are pre-installed, run a manual Windows Update [Windows Update | Check for updates] to detect and install any available updates released as of 11-Apr-2017.  It might take a few re-boots and manual Windows Updates to get everything patched, depending on how many months or years your Vista SP2 OS is out of date. See Note 5 if Windows Update continues to hang at "Checking for updates...". [WARNING*: If you following these instructions after July 2020 and Windows Update throws an error see the IMPORTANT NOTICE at the top of this post.]*

**** EDIT as of June 2017:  Microsoft released five out-of-band emergency security updates for Vista SP2 in June 2017 were posted on the Microsoft Update Catalog but will not be delivered via Windows Update.  See the thread More Shadow Brokers Exploits Patched June 2017 for Win XP and Vista for instructions on how to install these emergency updates if they are still missing from your system. ****

**** EDIT as of April 2020:  Since March 2020 multiple users performing a clean reinstall of their Vista SP2 OS have reported that Windows Update can throw an error 800B0109 ("A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider") while trying to install KB4014984 (Security and Quality Rollup for NET. Framework 2.0, 3.0, 4.5.2, 4.6 on Windows Vista SP2 and Server 2008 SP2: April 11, 2017).  To fix this error, download the MicrosoftRootCertificateAuthority2011.cer file from http://go.microsoft.com/fwlink/?linkid=747875&clcid=0x409 and save it to the root C:\ directory of your computer (i.e.., so the location is C:\MicrosoftRootCertificateAuthority2011.cer), open anelevated command prompt with Administrator rights, and enter the command certutil -addstore "Root" "C:\MicrosoftRootCertificateAuthority2011.cer" to apply the required trust certificate. Kudos to greenhillmaniac for posting about this fix in his 06-Apr-2020 post in the MSFN threadCertificate Trust Provider Error Installing Updates. ****
______________________

Note 1:  Download 32-bit (x86) or 64-bit (x64) .msu installers from the Microsoft Update Catalog at the following links:

REQUIRED:

     KB3205638:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB3205638 Vista

     KB4012583:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB4012583 Vista
     KB4015380:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB4015380 Vista

     KB4019204:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB4019204 Vista

OPTIONAL (if Internet Explorer 9 is installed):

    KB4018271:  https://www.catalog.update.microsoft.com/Search.aspx?q=KB4018271 Internet Explorer 9 Vista

OPTIONAL (if MS Office 2007, MS Office 2010 or the MS Office Compatibility Pack SP3 is installed):

     See Note 5 below.

Image

Note 2:  If you have problems downloading the .msu installers using Internet Explorer 9 then try an alternate browser like Firefox ESR v52.9.0 (the legacy extended support release for Win XP and Vista, last updated 26-Jun-2018).  You can also download the .msu installers to a USB thumb drive from another computer and copy the .msu installers to your Vista desktop.

Note 3:  If you try to install a speed up patch that is already installed on your computer, download an installer that does not match the bit architecture of your OS (e.g., you try to run a 64-bit .msu installer on a 32-bit Vista machine), or try to install a speed up patch that has been superseded (replaced) by a newer update you will see a "The update is not applicable to your computer" error - see the MS support article Windows Update Troubleshooting for other common causes of this error.

Note 4:  The standalone update packages (.msu files) will get stuck at "Checking for updates..." if there is a Windows Update session already running in the background on your computer.  Most users find that disabling automatic Windows Updates and re-booting is sufficient (STEP # 1), but if your .msu installer still gets stuck you can temporarily disconnect from the internet or stop your Windows Update service (wuauserv) at Control Panel | System and Maintenance | Administrative Tools | Services while running these installers.  Unlike Windows Update, these standalone update packages (.msu files) are associated with the Windows Update Standalone Installer (C:\Windows\System32\wusa.exe) and can be installed on computers without an internet connection.

Note 5:  This issue has not been prevalent since 2018, but if you have MS Office 2007 SP3, MS Office 2010 SP2 and/or the MS Office Compatibility Pack SP3 (an add-on that allows older MS Office products like MS Office 2000/2003/2007 to work with files with newer Open XML formats like .docx, .xlsx, etc.) and find that Windows Update is still running slowly after completing the instructions above then links for additional "speed up" patches (.exe self-extracting installers) for these MS Office products are posted below.

If MS Office 2007 SP3 installed:
KB4018355: for Word 2007 (rel. Apr 2018)

 [KB4018353](https://www.microsoft.com/en-us/download/details.aspx?id=56780): for Excel 2007 (rel. Apr 2018)

If MS Office Compatibility Pack SP3 (MS Office 2000/2003/2007 add-on) installed:

 [KB4018354](https://www.microsoft.com/en-us/download/details.aspx?id=56800): Word converter file (wordconv; rel. Apr 2018)

 [KB4461607](https://www.microsoft.com/en-us/download/details.aspx?id=57877): Excel converter file (xlconv; rel. Feb 2019)

If 32-bit MS Office 2010 SP2 installed:

 [KB4493218](https://www.microsoft.com/en-us/download/details.aspx?id=102981 "https://www.microsoft.com/en-us/download/details.aspx?id=102981"): for 32-bit MS Word 2010 (rel. Apr 2021)

 [KB3017810](https://www.microsoft.com/download/details.aspx?familyid=dbf63fea-6134-43ed-8960-a5e6822b494a "https://www.microsoft.com/download/details.aspx?familyid=dbf63fea-6134-43ed-8960-a5e6822b494a"): for 32-bit MS Excel 2010 (rel. Apr 2021)

If 64-bit MS Office 2010 SP2 installed:

 [KB4493218](https://www.microsoft.com/download/details.aspx?familyid=0ad9421d-1f16-4ed2-bc3c-59c293c11ad5 "https://www.microsoft.com/download/details.aspx?familyid=0ad9421d-1f16-4ed2-bc3c-59c293c11ad5"): for 64-bit MS Word 2010 (rel. Apr 2021)

[KB3017810](https://www.microsoft.com/download/details.aspx?familyid=0d5a97be-08a4-485f-aba0-9fa27f072a93 "https://www.microsoft.com/download/details.aspx?familyid=0d5a97be-08a4-485f-aba0-9fa27f072a93"): for 64-bit MS Excel 2010 (rel. Apr 2021)

If you have performed a clean reinstall of your MS Office product and are missing the final Service Pack then links to MS Office 2007 Service Pack 3 (KB2526086) and MS Office 2010 Service Pack 2 (KB2687455) are posted in the Lifewire article Latest Microsoft Office Service Packs. These Service Packs should be installed before applying the above "speed up" patches for your Office product(s).

32-bit Vista Home Premium SP2 * FF ESR v52.9.0 * Malwarebytes Premium v3.5.1 * MS Office 2003 Pro SP3
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Was this answer helpful?

0 comments

703 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-08-25T04:45:13+00:00

    Mine can download but it wont install the standalone update installer searches for several hours 10 to be exact and does not find any updates to install

    Have you tried disconnecting from the Internet? Find the downloaded file, click to open, and it will search for a bit until it realizes there's no web connectivity, then the update will run (usually).

    Was this answer helpful?

    0 comments
  2. lmacri 2,505 Reputation points
    2016-08-25T04:03:56+00:00

    Mine can download but it wont install the standalone update installer searches for several hours 10 to be exact and does not find any updates to install so therefore my computer doesn't prompt me for a restart because it has not found any updates to install

    Hi DarlingDell:

    I provided detailed instructions specific to your 32-bit Vista machine for the initial Steps 1 to 3 on 12-Aug-2016 (page 3) and for the remaining Steps 4 to 6 on 14-Aug-2016 (page 4).  These customized instructions included screenshots and the following hint that "some users report that they see the .msu installer get stuck at "Checking for updates..." for more than 30 min. That usually happens when people skip Step # 1 of the instructions and fail to stop their background Windows Updates, but if you run into this problem thendisconnect from the internet and re-run the .msu installer."

    You seem to be confused about the purpose of the standalone update packages (.msu files) for the Windows kernel-mode driver (Win32K.sys) updates listed on Dalai's webpage at http://wu.krelay.de/en/.  The .msu files are self-extracting installers.  If you download the 32-bit standalone update package for KB3177725 from the Microsoft Download Center (Windows6.0-KB3177725-x86.msu) to your desktop and double-click the file to launch the installer, it will only install that one update - KB3177725.  The "Searching for updates" step for these standalone installers only means that it is running an internal check to see if**:**

    • the update is already installed on your system
    • the update is out-of-date and has been replaced (superseded) by a newer update already installed on your system
    • the .msu installer is not compatible with your OS (e.g., you downloaded a 64-bit version of the installer for your 32-bit Vista OS)
    • the update cannot be installed because a required prerequisite update needs to be installed first

    If the "Checking for updates" phase of the standalone installer determines the update doesn't need to be installed (or shouldn't be installed) on your system you'll see a a message saying "The update is not applicable to your computer"

    Please go back and read the step-by-step instructions I posted for you on 12-Aug-2016 and 14-Aug-2016.

    32-bit Vista Home Premium SP2 * Firefox v48.0.1 * NIS v22.7.1.32 * MBAM Premium v2.2.1

    HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-08-25T03:14:13+00:00

    This was really helpful, but I guess there are many different systems out there with a slightly different fix. Before I start - it's really sad that MS have let so many customers wither without support. The update architecture has become a real mess and both my Vista PCs folded their arms and stopped WU at exactly the same time - that's more than coincidence. It seems most Vista PCs get a hissy fit when they try to work out which updates they need and what order to do them in, and MS have done nothing to streamline this.

    So, I turned off WU (right click on it in Services, stop it, and put to manual start - important as you want the only version running to be the one you call when you double click to run each of these msu files. I put the KB number vista x86 (I'm 32 bit) into Google and downloaded each to a memory stick, so I could carry them to both PCs. I copied the files to each desktop. I left Services open so between each installed update I could see WU was stopped.

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=6a0ee156-04f4-40ba-8480-009699a60145)

    Some of the updates were not needed by my PCs but the rest installed in a minute or so.  I rebooted between each. After that, I put WU back to its usual delayed start and set the usual "check for updates" - which took 4 hours on one PC and 5 on the other. As there were 43 updates it did take a while, but after that they both alerted to a further 1 or updates after about 10 minutes, which was fine.

    But who knows what it will be like next month!

    I also hope that shiny new Windows 10 is not allowed to get in such a terrible state as it ages.

    Mine can download but it wont install the standalone update installer searches for several hours 10 to be exact and does not find any updates to install so therefore my computer doesn't prompt me for a restart because it has not found any updates to install

    I have tried that and it didn't work either

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-08-25T03:06:28+00:00

    This was really helpful, but I guess there are many different systems out there with a slightly different fix. Before I start - it's really sad that MS have let so many customers wither without support. The update architecture has become a real mess and both my Vista PCs folded their arms and stopped WU at exactly the same time - that's more than coincidence. It seems most Vista PCs get a hissy fit when they try to work out which updates they need and what order to do them in, and MS have done nothing to streamline this.

    So, I turned off WU (right click on it in Services, stop it, and put to manual start - important as you want the only version running to be the one you call when you double click to run each of these msu files. I put the KB number vista x86 (I'm 32 bit) into Google and downloaded each to a memory stick, so I could carry them to both PCs. I copied the files to each desktop. I left Services open so between each installed update I could see WU was stopped.

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=6a0ee156-04f4-40ba-8480-009699a60145)

    Some of the updates were not needed by my PCs but the rest installed in a minute or so.  I rebooted between each. After that, I put WU back to its usual delayed start and set the usual "check for updates" - which took 4 hours on one PC and 5 on the other. As there were 43 updates it did take a while, but after that they both alerted to a further 1 or updates after about 10 minutes, which was fine.

    But who knows what it will be like next month!

    I also hope that shiny new Windows 10 is not allowed to get in such a terrible state as it ages.

    I'm glad it has worked for you. It will work for some but not others. Thank You

    Was this answer helpful?

    0 comments