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 No 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 No comments

703 additional answers

Sort by: Newest
  1. Anonymous
    2017-04-10T16:22:14+00:00

    Considering that it was all over the computer sites for a while, and the experiences people had with XP would have hopefully taught them to look up "End Of Life" dates for their support on other MS software (even Wikipedia has an article on this) there isn't much to hold up that theory. If your machine is too old to run 8.1 then 7 is probably the best alternative, or Linux. Linux won't run your MS software but it does run similar programs and apps and you can keep an older computer running well a while longer.

    Windows 7 is still available to download as an ISO at https://www.microsoft.com/en-us/software-download/windows7, you will need a key or I don't know if you can update from Vista using that, never had to do it.

    Burn that to a DVD and go from there.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-04-10T07:14:31+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.

    Hi m#l:

    If the initial "Checking for updates..." phase of Windows Update hangs for several hours on Patch Tuesdays on the second Tuesday of the month without throwing an error, this is a widespread problem that currently affects many Vista SP2 users.  Some users find that Windows Update will eventually run to completion if you let it run for several hours (or even days), but there is also a workaround posted on Dalai's webpage Search for Windows Updates takes forever? - A possible solution at http://wu.krelay.de/en/ that speeds up Windows Update for most affected users.  If you'd like to try Dalai's workaround, I'd suggest the following:

    REVISED for the March 2017 Patch Tuesday (valid 14-Mar-2017 to 10-Apr-2017):

    ****IMPORTANTExtended support for Vista SP2 is ending on 11-Apr-2017 and there will be no further security updates released for Vista SP2 after this date.  Please see Microsoft's Windows Life Cycle Fact Sheet for more information.****

    If you were fully patched as of January 2017, the latest Windows updates that must be pre-installed to speed up Windows Update on Vista SP2 computers is KB4012497 (MS17-018 Security Update for Windows Kernel-Mode Drivers and for Microsoft Graphics Component: March 14, 2017).  Some early testers are reporting that KB4012583 (MS17-013 Security Update for Microsoft Graphics Component: March 14, 2017) and/or KB4012204 (MS17-006 Cumulative Security Update for Internet Explorer 9 for Windows Vista: March 14, 2017) also helped to reduce their "Checking for updates..." hang this month.  See Note 2 below for download links for both the 32-bit (x86) and 64-bit (x64) standalone .msu installers.

    Terminate any Windows Update sessions running in the background [Windows Update | Change settings | Important updates | Never check for updates (not recommended) and then re-boot - the re-boot is critical] before running your .msu installer to prevent the installer from getting stuck at "Checking for updates..." (see STEP # 1 and Note 5 below).  I normally save my .msu installer to my Windows desktop and then double-click to run.

    I pre-installed KB4012497, KB4012583 and KB4012204 this month and my Windows Update ran to completion in 3 hours 15 min (Checking for updates... required 3 hours), which is the slowest that Windows Update has run since I started using Dalai's workaround in June 2016.  Windows Update found 12 additional Important updates, including 3 related to my MS Office Compatibility Pack.  Please read Note 6 if you have MS Office or a MS Office Compatibility Pack installed on your system since this can add a significant amount of time to your "Checking for updates..." hang.

    If Windows Update failed to install your January 2017 Patch Tuesday updates (or you have reinstalled / restored your Vista SP2 OS to an earlier date and can't get Windows Update to run to completion), please follow these steps:

    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. As of 14-Mar-2017, the updates that must be installed on your system to speed up Windows Update are: KB3191203 (rel. 11-Oct-2016); KB3203859 (rel. 08-Nov-2016); KB3205638 (rel. 13-Dec-2016); KB4012497 (rel. 14-Mar-2017); KB4012583 (rel. 14-Mar-2017). If IE9 is installed then KB4012204 (March 2017 cumulative update for IE9 for Vista) could also help.  See Note 1.
    3. Search your installed updates at Control Panel | Programs and Features | View Installed Updates to see if any of these Win32K.sys updates is already installed your system. When searching, enter the full KB number in the search box (e.g., "KB3191203" and not a partial string like "3191203").
    4. Download the standalone update packages (.msu files) for any missing Win32K.sys updates from the Microsoft Update Catalog and save them to your Windows desktop - see Note 2 for download links.   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 3 if you have problems downloading the .msu installers.
    5. Install any missing updates in chronological order, from oldest (lowest KB) to newest (highest KB).  Double-click the .msu file on your desktop to start each installer - restart your computer when prompted after each update is installed.  See Notes 4 and 5 if you have problems running the .msu installers.
    6. Once all missing Win32K.sys updates are pre-installed, run a manual Windows Update [Windows Update | Check for updates] to install your remaining updates.  See Note 6.

    This "solution" is only a temporary workaround and a new Win32K.sys update(s) will be posted on Dalai's webpage on 11-Apr-2017 that will have to be pre-installed before you run Windows Update to install your April 2017 Patch Tuesday updates.

    ______________________

    Note 1:  KB3203859 (rel. 08-Nov-2016) has replaced KB3164033.  KB3204723 (rel. 13-Dec-2016) has replaced KB3198234.  The combination of KB319203/KB3203859/KB3205638 has replaced KB3078601/KB3109094.  KB4012497 (rel. 14-Mar-2017) has replaced KB3204723.

    Note 2:  Users can find download links for all the 32-bit (x86) and 64-bit (x64) installers by searching for the KB number in the Microsoft Update Catalog (e.g., search for the string "KBxxxxxxx Vista" where xxxxxxx is the 7-digit KB number) or just click the following links:

         KB3191203:  http://www.catalog.update.microsoft.com/Search.aspx?q=KB3191203 Vista

         KB3203859:  http://www.catalog.update.microsoft.com/Search.aspx?q=KB3203859 Vista

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

         KB4012497:  http://www.catalog.update.microsoft.com/Search.aspx?q=KB4012497 Vista

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

            

    OPTIONAL (if IE9 installed):

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

            

    Note 3:  Some users have reported problems downloading the .msu installers from the Microsoft.com site with Internet Explorer 9 (e.g., the user never sees a pop-up to Run/Save the file).  If this happens use an alternate browser (I recommend Firefox - Chrome is no longer supported for XP and Vista) or download the .msu installers to a USB thumb drive from another (non-Vista) computer and copy the .msu installers to your Vista desktop.

    Note 4: If you try to install a Win32K.sys speed up patch that is already installed on your computer, download an installer with the wrong bitness for 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 was recently superseded (replaced) by a newer update you will see a "not applicable" error - see the MS support article "The update is not applicable to your computer" error when you install Windows updates.  If one of the speed up patches listed in STEP # 2 throws a "not applicable" error and you are sure you have downloaded the correct installer (32-bit or 64-bit) for your system then move on to the next update in the list.

    Note 5:  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) as instructed in E-Chen's thread Vista Updates just keeps "Checking" before 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 6: If Windows Update has not successfully installed updates for a few months please be patient when running your Windows Update in March 2017.  It is not unusual for Windows Update to run for several hours before it finds all available updates when a 32-bit Vista SP2 OS is several months out-of-date, even after missing speed up patches are installed.

    If you have a supported version of MS Office or an MS Office Compatibility Pack that still receives security updates via Windows Update (Windows Update | Change settings | Microsoft Update | Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows) this can significantly increase your "Checking for updates..." hang.  User Volume Z maintains a list of additional speed up patches for MS Office-related products in peggybeggs' thread why has vista stopped automatic updates? that could help speed up Windows Update.

    If you followed STEPS # 1 to # 5 and your manual Windows Update (STEP # 6) is still stuck on "Checking f

    or updates..." after running overnight, I would suggest you try using Torsten Wittrock's WSUS Offline Update tool.  I haven't tried this tool but vista134's recent feedback in the bleepingcomputer thread How I got clean install of Vista Ultimate SP2 to install updates... indicates that WSUS Offline Update tool can be used to download and install important security updates for Vista SP2 (see the Legacy tab of the interface) and other Microsoft products like MS Office.  Dalai is an active contributor in the WSUS Offline Update forum.


    32-bit Vista Home Premium SP2 * Firefox ESR v52.0 * NIS v22.9.0.71 * MBAM v2.2.1

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

    The "Updates not working, it has been searching for updates for hours" has been a very unfortunate experience for so many.  When support for Microsoft Windows XP ended, the Operating System provided an early warning pop up to users of the PC.  It is disappointing that, from my experience, that Microsoft provided very little official guidance during the final year of Windows Vista update support and it seems there isn't even an internal warning in the Vista operating system to warn that support is ending within days of this posting.

    My thanks go out to Great White North and a few others for being so talented, dedicated to resolve the issue, and for being so helpful.

    It isn't over yet.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-03-29T22:14:42+00:00

    All of a sudden I know how to make sense of "The update is not applicable to your computer" reports about KB3078601 from before Patch Day October 2016.

    KB3109094 + KB3087039 supersedes KB3078601.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-03-28T19:40:57+00:00

    At least 7...it's much better in my opinion and you can take it farther than you would take Vista. You will have to do something eventually. Even if you aren't fond of 10 or simply cannot use it on your machine you still have better Windows options.

    I came to 7 pretty late and like it. And at some point everybody has had the Windows Update problems. You need to look to non-OS specific questions about that.

    Was this answer helpful?

    0 comments No comments