When you try to install updates from the Windows Update Web site or from the Microsoft Update Web site, you receive the following error code:

This issue occurs if Windows Update or Microsoft Update cannot verify the update.inf file.

To resolve this issue follow these steps:

Step 1: Set the Cryptographic Services service to automatic

To set the Cryptographic Services service to automatic, follow these steps:

1. Click Start, click Run, type services.msc, and then click OK.
2. From the list of available services, right-click Cryptographic Services, and then click Properties.
3. In the Startup type drop-down list, select the Automatic option, and then click Apply.
4. In the Services status section, click Start.
5. Try to install the updates again.

Note Windows 2000 does not list the Cryptographic Services service in the Services Administrative Utility.

If you still cannot install the updates, continue to step 2.

Step 2: Reregister DLL files that are associated with the Cryptographic Services service

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: To register the .dll files that are associated with the Cryptographic Services service, follow these steps:

1. Start Notepad. To do this, click Start, click Run, type notepad, and then click OK.
2. Copy and then paste the following commands into Notepad:
   regsvr32 /u softpub.dll /s
   regsvr32 /u wintrust.dll /s
   regsvr32 /u initpki.dll /s
   regsvr32 /u dssenh.dll /s
   regsvr32 /u rsaenh.dll /s
   regsvr32 /u gpkcsp.dll /s
   regsvr32 /u sccbase.dll
   regsvr32 /u slbcsp.dll /s
   regsvr32 /u mssip32.dll /s
   regsvr32 /u cryptdlg.dll /s
3. Save the Notepad file on the desktop as register.bat. To do this, follow these steps:
   1. In Notepad, click File, click Save As, and then type register.bat.
   2. In the Save in list, click Desktop.
   3. In the Save as type list, click All files, and then click Save.
4. On the Desktop, double-click the register.bat file.
   
   Note When you do this, the registry keys will be added to the Windows registry.
5. Click OK, and then try to install the updates again.
6. If the issue is resolved, delete the register.bat file that you saved in these steps.

If the issue is not resolved, continue to step 3.

Step 3: Rename the Catroot2 folder

Important These steps apply to Windows XP and Windows Server 2003 only. Skip this method if your computer is running Windows Vista, Windows 2000, or Windows Server 2008.

To rename the Catroot2 folder, follow these steps:

1. Start Notepad. To do this, click Start, click Run, type notepad, and then click OK.
2. Copy and then paste the following commands into Notepad.
   net stop cryptsvc
   cd %systemroot%\system32
   ren catroot2 catroot2old
   net start cryptsvc
3. Save the file as rename.bat. To do this, follow these steps:
   1. In Notepad, click File, click Save As, and then type rename.bat.
   2. In the Save in list, click Desktop.
   3. In the Save as type list, click All Files, and then click Save.
4. On the Desktop, double-click the rename.bat file to register the Windows Update files.
5. Try to install the updates again.
6. If the issue is resolved, you can safely delete the rename.bat file that you created in these steps.

Note If you still have problems, contact support. For information about how to contact support, visit the following Microsoft Web site:

Advanced troubleshooting

If the general troubleshooting steps in this article did not resolve the issue, follow the advanced troubleshooting steps in article 822798.

For more information about advanced troubleshooting steps for installing updates, click the following article number to view the article in the Microsoft Knowledge Base: