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

ID: Q243516

The information in this article applies to:
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server

SUMMARY

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


MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

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.


Additional query words: prompt distribution share

Keywords : kbenv
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbinfo


Last Reviewed: December 29, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.