Windows xp file protection registry

Create a free Team What is Teams? Learn more. Ask Question. Asked 9 years, 3 months ago. Active 6 years, 5 months ago. Viewed 28k times. Improve this question. Community Bot 1. Searush Searush 2 2 gold badges 9 9 silver badges 20 20 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. Kasius Kasius 1 1 gold badge 4 4 silver badges 10 10 bronze badges. Thanks for devcon and pnputil very much!

I will try them. They seem useful. What me do? Yes, you can create the value, but I don't think it will do you much good. You have to attach a kernel debugger before setting the value to 1 will actually do anything. If I am correctly reading the article I quoted, then yes. Microsoft recommends that before you ever edit the Registry, you always attempt to back up the Registry and understand how to restore it if a problem occurs.

In the Links and References section you will find an article that covers how to quickly back up the Registry so that if a mistake is made, you can at least have a backup of your system. Windows XP has the ability to protect itself from crashing from system instability infamously caused by third party software overwriting important system files.

Once overwritten, the system can become unstable and crash. Windows File Protection is always enabled by default. The scan starts and if you need to fix something, you will be prompted for the distribution media. As you can see from the file on a pre- SP2 system, this is what you want to see. If you have the SP2 version, then you will want to remove that.

This situation may occur if the file is not present in the Dllcache folder or if the file is corrupted. In this situation, WFP may not have the correct credentials to access the share from the network-based installation media.

At the end of GUI-mode Setup, the System File Checker tool scans all the protected files to make sure that they are not modified by programs that were installed by using an unattended installation.

The System File Checker tool also checks all the catalog files that are used to track correct file versions. If any of the catalog files are missing or damaged, WFP renames the affected catalog file and retrieves a cached version of that file from the cache folder. If a cached copy of the catalog file is not available in the cache folder, the WFP feature requests the appropriate media to retrieve a new copy of the catalog file.

The System File Checker tool gives an administrator the ability to scan all the protected files to verify their versions. The SfcScan value in the following registry key has three possible settings:. Default value. By default, all system files are cached in the cache folder, and the default size of the cache is MB.

Because of disk space considerations, it may not be desirable to maintain cached versions of all system files in the cache folder. To change the size of the cache, change the setting of the SFCQuota value in the following registry key:. The administrator can make the setting for the SFCQuota value as large or small as needed. There are two cases in which the cache folder may not contain copies of all protected files, regardless of the SFCQuota value:.

Not enough disk space. Network Install. Additionally, all drivers in the Driver. WFP can restore these files from the Driver. If WFP detects a file change and the affected file is not in the cache folder, WFP examines the version of the changed file that the operating system is currently using. If the file that is currently in use is the correct version, WFP copies that version of the file to the cache folder.

If the file that is currently in use is not the correct version, or if the file is not cached in the cache folder, WFP tries to locate the installation source. If WFP cannot find the installation source, WFP prompts an administrator to insert the appropriate media to replace the file or the cached file version.

To modify the cache location, you must add this value. For more information about the WFP feature, click the following article number to view the article in the Microsoft Knowledge Base:. Replacement of protected system files is supported only through the following mechanisms: Windows Service Pack installation using Update.

The network install path, if the system was installed using network install.