Processing your request, Please wait....

To resolve this problem, use the following methods. After you perform the steps in each method, test to see whether the problem is resolved before you go on to the next method. If the problem is resolved by any method, you do not have to use the remaining methods.

Method 1: Restart your computer, and then try to install the updates again

Close all programs that are running, restart your computer, and then try to install the updates again.

Note: Restarting the computer will make sure that all previous installations have completed and that there are no remaining processes that require a system restart before they can be completed.


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

1. 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, click the following article number to view the article in the Microsoft Knowledge Base

947821 Description of the System Update Readiness Tool for Windows Vista, for windows Server 2008, for Windows 7, and for Windows Server 2008 R2

2. Try to install updates again

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

%systemroot%\logs\cbs


Method 3: Run the System File Checker utility (SFC.exe)

1. Start an administrative command prompt

2. At the command prompt, type sfc /scannow, and then press Enter

3. Once the scan completes, Try to install updates again


Method 4: Reset content of the Catroot2 folder

1. net stop cryptsvc

2. md %systemroot%\system32\catroot2.old

3. xcopy %systemroot%\system32\catroot2 %systemroot%\system32\catroot2.old /s

4. Delete all contents of the catroot2 folder but leave the catroot2 folder in place

5. net start cryptsvc


Method 5: Remove incorrect Registry values that may exist

1. Click start, in the search box, type regedit

2. In the programs list, click regedit.exe

3. Find and then click on the following registry subkey

HKEY_LOCAL_MACHINE\COMPONENTS

4. Right click on COMPONENTS

5. Click Export

6. In the File Name bvox, type COMPONENTS

7. In the save in box, click Desktop , and then click Save, to save the file to your desktop

8. In the details pane, right click PendingXmlIdentifier, and then click Delete. If the value does not exist go to the next step

9. In the details pane, right click NextQueueEntryIndex, and then click Delete. If the value does not exist go to the next step

10. In the details pane, right click AdvancedInstallersNeedResolving, and then click Delete. If the value does not exist go to the next step.

11. Restart the computer

12. Try to install updates again.


Method 6: Register the Windows Update files

1. Start and administrative command prompt

2. At the command prompt, type the following commands

REGSVR32 WUPS2.DLL /S
REGSVR32 WUPS.DLL /S
REGSVR32 WUAUENG.DLL /S
REGSVR32 WUAPI.DLL /S
REGSVR32 WUCLTUX.DLL /S
REGSVR32 WUWEBV.DLL /S
REGSVR32 JSCRIPT.DLL /S
REGSVR32 MSXML3.DLL /S


3. Try to install updates again.


Method 7: Make sure that your antivirus application does not scan certain files

Make sure that your antivirus application does not scan the files in the %windir% \SoftwareDistribution directory on any computer on which the Windows Update Agent is installed.


Note: These files are not at risk of infection. If you scan these files, serious performance problems may occur because some files may be locked. If a specific set of files is identified by name, exclude only those files instead of the whole folder. Sometimes, the whole folder must be excluded. Do not exclude any of these items based on the file name extension. For example, do not exclude all files that have a .dit extension. Microsoft has no control over other files that may use the same extensions as these files.
• Files that are related to Microsoft Windows Update or to Automatic Update
• The Windows Update database file or the Automatic Update database file
Note: This file (Datastore.edb) is located in the following directory:
%windir%\SoftwareDistribution\Datastore
• The transaction log files
Note: These files are located in the following folder:
%windir%\SoftwareDistribution\Datastore\Logs
Exclude the following files:
• Edb*.log
Note: The wildcard character indicates that there may be several files.
• Res1.log
• Res2.log
• Edb.chk
• Tmp.edb


Method 8: Rename the Software Distribution folder
To rename the Windows Update temporary SoftwareDistribution directory follow these steps:

1. Start an administrative command prompt.
2. Run the following commands hitting enter after each line:
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 do this:
• 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 re-select this option from the Windows Update Web site.
Note: If the issue is resolved and you can successfully download and install updates, you can safely delete the SoftwareDistribution.old directory to recover disk space.

Method 9: Clear the BITS queue of any current jobs
1. Start an administrative command prompt
2. Run the following commands hitting enter after each line
Net stop bits
Net stop wuauserv
Ipconfig /flushdns
cd “documents and settings\all users\application data\microsoft\network\downloader”
Del qmgr0.dat
Del qmgr1.dat
Net start bits
Net start wuauserv

Note: When you do this the BITS queue is cleared

3. Try to install updates again


Method 10: Download and install the update manually 958056
1. Determine the Microsoft Knowledge Base article number of the failed update. To do this, do one of the following:

View the error code message.

View the update history on the Windows Update Web site or on the Microsoft Update Web Site, to do this follow these steps:

Visit the following Microsoft Update Web site:
http://update.microsoft.com
Under Options, click Review your update history.
In the Update column, determine the Microsoft Knowledge Base article number of the failed update.

2. Visit the following Windows Download Web site:
http://www.microsoft.com/windows/downloads/default.aspx
3. In the Search box on the Downloads Web page, type the article number that you located in step 1, and then click Go.
Note: Do not include the letters 'kb' when typing in the article number. e.g. kb123456 should be 123456.
4. Browse through the list of returned content, and locate the Knowledge Base article that has a link to the download.
Note: You may be prompted to validate Windows. If you are prompted, follow the instructions to validate Windows, and then continue to download the update.
5. Click Download, and then click Save when you are prompted to save the download. Save the download to your desktop.
6. After the download has finished, click Open to install the update.
Note: the installation of the update may fail if the update is incorrect for your version of Windows.

Method 11: Rename Pending.xml
1. Open an elevated command prompt
2. At the command prompt type the following command:
takeown /f C:\Windows\winsxs\pending.xml
3. Rename c:\windows\winsxs\pending.xml using the following command:
Ren c:\windows\winsxs\pending.xml pending.old


Method 12: Run Check disk (chkdsk) on the OS partition
1. Open an elevated command prompt
2. At the command prompt type the following command:
Chkdsk volume: /f /r

Here’s to Good Karma