Thanks for your feedback. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 7. Report abuse. I'm beginning to think that there is no way to disable it in XP SP3.
I think it's better to not disable it. That way you won't risk rendering your system unusable. Perhaps someone will find a surefire method of disabling it, but for now it seems that there is no way. I just found that. As for the google search, most if not all results will only apply to SP3 RC2. The article I found pertained to RC2, but I followed it and found that there was no difference in information.
Just follow the steps, either way, good luck. If you really need assistance, I can offer help via AIM. To previous posters about why you would want to disable Windows File Protection, for most moderate to experienced users - they don't require that Windows backs up critical operating files because they either format too often or they don't modify these files except for with hotfixes.
When you apply a hotfix, you could always download a previous version if you run into conflicts. Here you go, Slycer. If you wish to avoid having to do this in the future, create a new modified Windows XP cd using nLite which has an option to disable SFC. So when you install XP next time it will already be disabled! This folder has nothing to do with Windows file protection but everything with drivers and Windows update.
Restart your computer, boot windows in safe mode. Depending on your BIOS you will usually have to press a button during the start up process to access safe mode.
You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Win ME system file protection question. Share More sharing options Followers 0. Recommended Posts. ZortMcGort11 Posted February 17, WFP has to restore a file from a network share.
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.
0コメント