The Diagnose and fix program installing and uninstalling problems automatically troubleshooter may automatically fix the problem described in this article. This troubleshooter fixes many problems.Learn moreRun now
Let me fix it myself
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To fix this problem, follow these steps:
Confirm that the product is affected. To do this, follow these steps:
Find the software update registration of the product by opening the following registry subkey:
If the subkey is missing, the product is affected. Continue to step 2.
If the subkey exists, verify that the LocalPackage string value is set correctly, and that the package referenced by the LocalPackage string value also exists.
If the LocalPackage string value or referenced package is missing, the product is affected. Continue to step 2.
If the referenced package exists and no additional action is required.
Re-create software update cache registry details. To do this, follow these steps:
Search the %windir%\installer\*.msp for the software update that you tried to install. Verify that the software update has the correct Patch GUID in the Summary Information Stream and targets the correct product GUIDs. Note Because this directory serves as the cache for per-user installations and per-machine installations, you can simulate a software update in this directory by using a per-user installation.
Note It is a security risk to re-create the software update cache registry. However, this is the only way to repair the corruption. You can reduce the security risk by making sure that the software update is the correct software update. To do this, verify the checksum of the software update.
Create a LocalPackage string value in the registry subkey that you created step 2,b. Make sure that the LocalPackage string value is set to the path of the software update.
Delete remaining software update references. To do this, follow these steps:
Open the following subkey, and then remove <PatchSQUID> from the "AllPatches" multi-sz value:
This article is not specific for issues occured by Windows Update or Microsoft Update. For more information about troubleshooting Windows Update or Microsoft Update issues, visit following Microsoft Website:
Microsoft Windows XP Home Edition, Microsoft Windows XP Professional, Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Web Server 2008, Windows Vista Business, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Starter, Windows Vista Ultimate