Access Violation in Update.exe When Installing Windows 2000 Service Pack 2 (301556)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2

This article was previously published under Q301556
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

You may receive an access violation in Update.exe when you install Windows 2000 Service Pack 2 (SP2).

CAUSE

This issue can occur if the default value in the following registry value has been changed to a valid path:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Currentversion\Setup\Drivercachepath

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, restore the default value in the following registry value:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Currentversion\Setup\Drivercachepath

The default value is:

%SystemRoot%\Driver Cache

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

Modification Type:MajorLast Reviewed:12/4/2003
Keywords:kbbug kberrmsg kbfix kbsetup kbWin2000sp3fix KB301556