Policy to Set the Installation Point for Windows File Protection Does Not Exist

View products that this article applies to.

This article was previously published under Q243516

Expand all | Collapse all

SUMMARY

A policy to set the installation point for Windows File Protection (WFP) does not exist in a Windows 2000 Group Policy Object (GPO).

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.

WFP uses the installation path to look for a file that needs to be copied back, in the event it is replaced with a non-signed file. WFP first searches the Dllcache folder, then the Driver.cab file (located in the %WinDir%\Driver Cache\i386 folder), and then finally for the installation point. This value is located in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup
Value: SourcePath
Data Type: REG_SZ

If this location changes (for example, you rename a server or move a computer to a location where the existing share is no longer accessible), you must reset this value for WFP to work properly.

NOTE: Setup also uses this value to locate the source files when you add a new component to the computer.

To change this value, use the appropriate method:

Manually edit the registry to point to the updated location.
Use a Regedit or Regini file to import the correct value into the registry by using a login scripts or a runonce command. For information about using Regedit or Regini, please consult the Microsoft Windows 2000 Resource Kit.
Create a custom .adm file to use within a Group Policy.