Article ID: 258862 - View products that this article applies to.
This article was previously published under Q258862
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you use Riprep.exe to create an image of a Windows 2000 Professional installation and the OemPnpdriversPath key is specified in the Sysprep.inf file, the entries placed in this registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows: DevicePathare duplicated when placed in the registry. For example, an OemPnpDriversPath key that has the value
OemPnpDriversPath = drivers\nic;drivers\videoresults in the following values being entered into the OemPnpdriversPath registry key:
This behavior occurs because Riprep.exe incorrectly enters the values supplied by the OemPnpDriversPath key into the registry.
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.
Having these duplicate values in the registry can make the setup process take a few moments longer depending on the number of paths that were specified using the OemPnpDriversPath key. The duplicate values do not seem to adversely affect Setup in any other way. However, because the paths specified are used throughout the life of the computer when new hardware is installed, you may want to change these values.
To change the duplicate values, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.