Article ID: 949384 - View products that this article applies to.
When you try to install Windows XP Service Pack 3 (SP3), you may receive the following error message:
After you click OK in the error message, you receive the following error message:
An internal error occurred
Additionally, you may see the following errors that are logged in the C:\Windows\Svcpack.log file:
Service Pack 3 installation did not complete
Note Throughout this article, the C:\Windows folder represents the folder where Windows XP is typically installed.
165.672: An internal error occurred. 165.672: Service Pack 3 installation did not complete. 165.672: Update.exe extended error code = 0x1ffe054f 165.672: Update.exe return code was masked to 0x643 for MSI custom action compliance
The errors that are mentioned in the "Symptoms" section can occur because of files that are not trusted or because of corrupted registry keys. You can verify the cause by searching for related entries in the Svcpack.log file. Specific entries will identify specific causes of the issue, as noted in the following "Cause" sections.
Cause 1Determine whether the following entries are logged in the Svcpack.log file:
These entries indicate that the cause of the issue is the Licdll.dll file. The Licdll.dll file may have been altered, is corrupted, or is not trusted. The Licdll.dll file is located in the following folder:
142.391: CheckVLKForBlock: LIC.dll not trust verified 142.578: Trying CheckVLKForBlock again 142.594: CheckVLKForBlock: LIC.dll not trust verified 142.594: Error: CheckVLKForBlock failed
Cause 2Determine whether the following entries are logged in the Svcpack.log file:
These entries indicate that incorrect product ID information in the registry is causing the issue.
211.890: IsSPBetaKey:pLA->lpVtbl->GetProductID Failed: 0x80004005 213.125: Trying CheckVLKForBlock again 214.468: Error: CheckVLKForBlock failed
Cause 3Determine whether the following entries are logged in the Svcpack.log file:
These entries indicate that corrupted or altered registry keys in preinstalled programs are causing the issue.
299.031: Trying CheckVLKForBlock again 299.531: Error: CheckVLKForBlock failed
Note One program that is known to cause this issue is Micrografx - Picture Publisher Professional 10. To work around this issue, see the "Workaround for Cause 3" section.
To resolve or to work around these causes, use the resolution or the workaround that corresponds to the cause.
Resolution for Cause 1To resolve this issue, you must replace the current copy of the Licdll.dll file by using a copy from the original Windows XP media. To do this, follow these steps:
Resolution for Cause 2To resolve this issue, you must replace the incorrect product ID registry entry with the correct product ID. To do this, follow the steps in the "Locate and note the product ID" and "Identify and change the product ID registry entry" sections.
Locate and note the product ID
Identify and change the product ID registry entryImportant 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:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Resolution for Cause 3To resolve this issue, you must delete the InprocServer32 registry subkey. To do this, follow these steps:
Workaround for Cause 3One program that is known to cause the issue that is mentioned in Cause 3 is Micrografx - Picture Publisher Professional 10. To work around this issue, temporarily uninstall the Micrografx program, and then install Windows XP SP3. After Windows XP SP3 installation is complete, reinstall the Micrografx program.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Contact us for more help
Connect with Answer Desk for expert help.