Nov 11, 2016 - My Windows 7 SP1 Windows Update feature is taking forever to check for updates in my Dell Inspiron 1750 Laptop, so how can I fix that.

I noticed when doing a manual Windows Updates using Control Panel it finds the updates fast enough but after selecting updates I want to install and asking to install them takes forever to Download updates and no progress indicated, but if I click the start icon after some time it shows the updates are ready to install if I Shut Down the PC, indicated by the yellow Bang. No indication of what updates are ready to install either.

If I let the Windows update run on downloading, it will eventually download and install the selected updates but still no progress indicated, but takes hours. I see this behavior on some (4) my W7 PC's (7).

Its like the Windows Update screen does not refresh.

Any insight to this behavior or how to solve it?

Fully updated Windows 7 64bit prior to this months (Aug 2016) patch Tuesday.

Note: Home network, Fios with no other issues. Its wide spread on several computers and does it on any of them when I travel with those devices also, it is a windows update gui issue. Happens on Normal month to month updates.

This has nothing to do with 'checking' for updates as answered in this question I answered this question myself but this is an entirely different issue and have found no solution so far.

6 Answers

Downloading Windows Updates takes forever

Dice Roll. . .

I like all the methods listed here on this MS KB as potential solutions to this problem. In particular Method 10 thru Method 13 stick out to me the most that sound like solutions I've used in the past to resolve correlated problems even if not exactly the same.

I'll only quote the methods below I would not skip for sure if I were troubleshooting this issue but I wouldn't limit myself to just these or just this KB for that matter but these may be good starting points for potential solutions.

I also agree that seeing any applicable detail from the %windir%WindowsUpdate.log would be helpful in troubleshooting this issue.

Lastly, I'd start troubleshooting and working this problem from one of the machines and ensure it's connected to a rather speedy Internet connection so in other words if you're traveling and connected to public network or a mobile wifi, just wait to ensure those factors don't play a role in the issue just in case.

Potential Resolution Methods

Method 1: Run the Windows Update troubleshooter

To do this, go to the Windows Update troubleshooter.

Method 4: Run the System Update Readiness tool (CheckSur.exe)

Download and run the System Update Readiness tool. This tool runs a one-time scan for inconsistencies that may prevent future servicing operations. For more information about how to download and run the CheckSur.exe tool, see the following article in the Microsoft Knowledge Base:

Fix Windows corruption errors by using the DISM or System Update Readiness tool (https://support.microsoft.com/kb/947821)

Try to install updates again.

Note After you run the tool, the CheckSur.log file is saved in the following location:

Method 5: Run the System File Checker tool (SFC.exe)

To do this, follow these steps:

1. Open an administrative Command Prompt window.
2. At the command prompt, type sfc /scannow, and then press Enter.
3. After the scan is finished, try to install updates again.

Method 6: Reset the content of the Catroot2 folder

To do this, follow these steps:

1. Open an administrative Command Prompt window.

2. Type the following commands, and press Enter after each command:

   • net stop cryptsvc
   • md %systemroot%system32catroot2.old
   • xcopy %systemroot%system32catroot2 %systemroot%system32catroot2.old /s

3. Delete all contents of the catroot2 folder, but do not delete the catroot2 folder.

4. Type the following command, and then press Enter:

net start cryptsvc

5. Exit the Command Prompt window.

Method 8: Register the Windows Update files

To do this, follow these steps:

1. Open an administrative Command Prompt window.
2. At the command prompt, type the following command:

3. Try to install updates again.

Method 10: Rename the SoftwareDistribution folder

To do this, follow these steps:

1. Open an administrative Command Prompt window.

2. Run the following commands, and press Enter after each command:

   • Net stop wuauserv
   • cd %systemroot%
   • Ren SoftwareDistribution SoftwareDistribution.old
   • Net start wuauserv

3. Try to install updates again.

Important The following issues occur when you use this method:

• Updates that are currently downloaded but that have not yet been installed have to be downloaded again by using Windows Update or Microsoft Update.

• When you delete the Software Distribution folder, your download history is removed.

• If you currently receive updates from Microsoft Update and from Windows Update, you will have to reselect this option from the Windows Update website.

Note If the issue is resolved and you can successfully download and install updates, you can safely delete the SoftwareDistribution.old folder to recover disk space.

Method 11: Clear the BITS queue of any current jobs

To do this, follow these steps:

1. Open an administrative Command Prompt window.
2. At the command prompt, type the following commands, and press Enter after each command:

Note After you complete these steps, the BITS queue is cleared.

3. Try to install updates again.

Method 12: Rename Pending.xml

To do this, follow these steps:

1. Open an administrative Command Prompt window.

2. At the command prompt, type the following command:

   takeown /f C:Windowswinsxspending.xml

3. Rename the c:windowswinsxspending.xml path by using the following command:

   Ren c:windowswinsxspending.xml pending.old

Method 13: Run Chkdsk on the Windows partition

To do this, follow these steps:

1. Open an administrative Command Prompt window.

2. At the command prompt, type the following command:

   Chkdsk volume: /f /r

If the fixes for Windows Update listed in the other answers have notfixed your problem, the slow updating might be caused by the way that WindowsUpdate works on the affected computers.

In another answer of mine, I have explainedthat Windows Update constructs in memory a tree of all the updates which couldapply to a computer, then prunes it with a view to the updates already installedon the computer, to finally arrive at the set of updates that need to be installed and the order of installation.

The time taken for this brute-force process is a function of the total numberof updates available for this platform, since the last service pack.Every service pack sort of defines a new platform for which updates startto accumulate anew. Also, Windows Update need to transfer large amounts of datafrom the Microsoft servers who may be overburdened.

Windows 7 SP1 came out on February 22, 2011, more than 5 years ago, and since thenthe number of updates has grown enormously. In addition, Microsoft'sWindows Update servers now give priority on bandwidth to Windows 10 clients.So all in all, Windows 7 SP1 is left to suffer.

To solve this problem, Microsoft has lately released theconvenience rollup for Windows 7 SP1, which, exactly the same as aservice pack, serves as a starting platform for updates.Installing it results in a much smallerupdates tree which is much faster to download and process,since only updates posterior to it are considered rather than all updates since 2011.Unfortunately, it is not available via Windows Update and has to bedownloaded and installed manually.

For more information on the convenience rollup for Windows 7 SP1, read
Microsoft overhauls Windows 7 and 8.1 updating -- but don't call it a service pack.

This convenience rollup is the only way by which one can reduce theWindows Update running time on Windows 7 SP1. Another one would be tolaunch it on hours in which the Windows Update servers of Microsofthave more available bandwidth (early morning or late night).

Admittedly, the problems you observe are a bit extreme, and might be relatedto some inefficiency that relates to the particular setup of these computers.I think that some combination of factors has enormously increased the time thatWindows Update takes to download and prune its update tree.This might even be a Microsoft bug.You might gain more information on the problem by watching Windows Updatewhile it is working, as regarding memory usage, network activity and disk access.

Installing the convenience rollup for Windows 7 SP1 is the only way I can thinkof to cut this Gordian Knot of Windows Update on the affected computers.However, it will probably stop working some time in the future, so has to be appliedquickly.

Turn off automatic Windows updates from the Control Panel and turn off the Windows Update service. Then, go to C:WindowsSoftwareDistributionDownload and delete everything in the folder. Restart the Windows Update service. Finally, open the CLI, type wuauclt.exe /updatenow, and press 'Enter.' Try to download the patches again and see what happens.

This is not a permanent fix but if there's a particular update you need asap and don't have time to sort out something permanent at the moment you can use.

You need to use IE. Do that then disable the Windows Update service.

Then sort out a permanent fix when you have the time.

You can try manually installing all missing updates using WSUS Offline, http://wsusoffline.net/

In the software you can choose your OS, download ALL updates for that version of windows, and then start the updater, and it will install all missing updates.

The 'Download pending' could also be due to expired / damaged certificates.Considering that Windows 7 and Windows 10 are pretty much suffering from similar decisions when looking at Windows Update, I'd like to contribute a further possible solution.

Just in case you want to rely on tools included in Windows, feel free to check the Event Log -> Application for 'CertificateServicesClient-AutoEnrollment' with ID 64 and a criticality of 'Warning'.Alternatively, you can get a detailed error code using the Windows Update Minitool, which is basically a 3rd party tool interfacing with Windows Update.For me, both Windows Update and the Windows Store seemingly started downloading but got stuck at 'Download pending' and would not continue or show an error code.The Windows Update Minitool finally gave me two error codes, the important of them being:

Windows 7 Takes Forever To Download Updates Free

• 0x80240022 (which turns out to be certificate related, i.e. the certificate expired or certificate chain broke)

The solution seems to be rather simple, if you are able to find a working manual.Kaspersky is offering a rather decent one over here.This is especially helpful, as the rootsupd.exe tool is rather difficult to find.And despite Kaspersky telling you to get the certificate store backup from a working device, feel free to just get the latest list of certificates from Microsoft.For some reason, I was not able to use those certificates without rootsupd.exe - the certificate management applet would show the certificate list, but would deem it broken.When I used the rootsupd.exe to extract and import the contents of authrootstl.cab, my Windows Update finally started working again.

Windows Update Takes Forever Fix

Not the answer you're looking for? Browse other questions tagged windows-7updates or ask your own question.

Windows 7 Update Package Download

• Find Free Books

• Tech To Make Life Easier

• Connect To Entertainment

• Fix It Yourself

Most of the time, Windows Update does its job with little if any attention from us.

While we might check and install updates manually from time to time, most Windows 10 computers are configured to apply important updates automatically, while older versions like Windows 7 and Windows 8 usually apply these fixes the night of Patch Tuesday.

Sometimes, however, when the patch, or maybe even service pack, is being installed during shutdown or startup, the update installation gets stuck — freezes, locks up, stops, hangs, clocks... whatever you want to call it. Windows Update is taking forever and it's clear something needs to be done.

The installation of one or more Windows updates is probably stuck or frozen if you see one of the following messages persist for a long time:

You might also see Stage 1 of 1 or Stage 1 of 3, or a similar message prior to the second example. Sometimes Restarting is all you'll see on the screen. There might also be some wording differences depending on which version of Windows you're using.

If you don't see anything at all on screen, especially if you think the updates might have been installed completely but could be the cause of whatever you're experiencing, see our How to Fix Problems Caused by Windows Updates tutorial instead.

Cause of a Frozen or Stuck Windows Update

There are several reasons why the installation or finalization of one or more Windows updates can hang.

Most often, these types of problems are due to a software conflict or a preexisting issue that simply wasn't brought to light until the Windows updates started installing. Much more rarely are they caused by a mistake on Microsoft's part regarding the update itself, but it does happen.

Any of Microsoft's operating systems could experience freezing issues during Windows updates including Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, and others.

There's an actual issue with Windows that can cause Windows Update installations to freeze like this but it's only applicable to Windows Vista and only if SP1 hasn't yet been installed. If your computer fits that description, install Windows Vista SP1 or later to solve the problem.

Make Sure the Updates Are Actually Stuck

Some Windows updates can take several minutes or more to configure or install, so you want to make sure the updates are truly stuck before moving on. Trying to fix a problem that doesn't really exist might just create a problem.

You can tell if Windows updates are stuck if nothing happens on screen for 3 hours or more. If there's any wonder after that long, take a look at your hard drive activity light. You'll see either no activity at all (stuck) or very regular but very short flashes of light (not stuck).

Chances are that the updates are hung before the 3-hour mark, but this is a reasonable amount of time to wait and longer than I've ever seen a Windows update take to successfully install.

How to Fix a Stuck Windows Update Installation

1. Press Ctrl-Alt-Del.

   In some situations, the Windows update(s) might be hung at a very particular part of the installation process, and you could be presented with your Windows login screen after executing the Ctrl-Alt-Del keyboard command.

   If so, log on as you normally would and let the updates continue to install successfully.

   If your computer restarts after the Ctrl-Alt-Del, read the second Note in Step 2 below. If nothing happens (most likely) then move on to Step 2.

2. Restart your computer, using either the reset button or by powering it off and then back on using the power button. Hopefully, Windows will start normally and finish installing the updates.

   I realize that you're probably explicitly told not to do this by the message on the screen, but if the Windows update installation is truly frozen, you have no other choice but to hard-reboot.

   Depending on how Windows and BIOS/UEFI are configured, you might have to hold down the power button for several seconds before the computer will turn off. On a tablet or laptop, removing the battery may be necessary.

   If you're using Windows 10 or Windows 8, and you're taken to the sign-in screen after the restart, try tapping or clicking the power icon on the bottom-right and choosing Update and Restart, if available.

   If you're automatically taken to the Advanced Boot Options or Startup Settings menu after restarting, choose Safe Mode and see the comments in Step 3 below.

3. Start Windows in Safe Mode.

   This special diagnostic mode of Windows only loads the minimum drivers and services that Windows absolutely needs, so if another program or service is conflicting with one of the Windows updates, the install might finish up just fine.

   If the Windows updates do install successfully and you continue to Safe Mode, just restart from there to enter Windows normally.

4. Complete a System Restore to undo the changes made so far by the incomplete installation of the Windows updates.

   Since you can't access Windows normally, try doing this from Safe Mode. See the link in Step 3 if you're not sure how to start in Safe Mode.

   During the System Restore, be sure to choose the restore point created by Windows just prior to the update installation.

   Assuming a restore point was made and System Restore is successful, your computer should be returned to the state it was in before the updates started. If this problem occurred after automatic updating, like what happens on Patch Tuesday, be sure to change Windows Update settings so this problem doesn't reoccur on its own.

5. Try System Restore from Advanced Startup Options (Windows 10 & 8) or System Recovery Options (Windows 7 & Vista) if you're not able to access Safe Mode or if the restore failed from Safe Mode.

   Since these menus of tools are available from 'outside' of Windows, you can try this even if Windows is completely unavailable.

   System Restore is only available from outside of Windows if you're using Windows 10, Windows 8, Windows 7, or Windows Vista. This option is not available in Windows XP.

6. While a System Restore is a more direct way of undoing changes, in this case of a Windows update, sometimes a more comprehensive repair process is in order.

   Windows 10 and Windows 8: Try a Startup Repair. If that doesn't do the trick, try the Reset This PC process (the non-destructive option, of course).

   Windows 7 and Windows Vista: Try the Startup Repair process.

7. It's possible that failing RAM could be causing the patch installations to freeze. Fortunately, memory is really easy to test.

8. Update BIOS.

   An outdated BIOS isn't a common cause for this problem, but it's possible.

   If one or more of the updates Windows is trying to install is involved with how Windows works with your motherboard or other built-in hardware, a BIOS update could solve the issue.

9. Clean install Windows. A clean install involves completely erasing the hard drive that Windows is installed on and then installing Windows again from scratch on that same hard drive. Obviously you don't want to do this if you don't have to, but it's a very likely fix if the steps prior to this one were unsuccessful.

It might seem likely that reinstalling Windows, and then these same exact Windows updates, will cause the same problem, but that isn't usually what happens. Since most lock-up issues caused by updates by Microsoft are actually software conflicts, a clean install of Windows, followed promptly by the installation of all available updates, usually results in a perfectly working computer.

Please let me know if you've had success escaping a hung Windows update installation using a method we don't have included in the troubleshooting above. I'd be happy to include it here.

Still Having Stuck/Freezing Issues Related to Windows Update?

If updates are stuck installing on or just after Patch Tuesday (the second Tuesday of the month), see our Details on the Latest Patch Tuesday piece for more on these specific patches.