i want to get rid of win2k system file protection, now!
i cant get rid of the system file protection in win2k, i tried to copy the file into dllcache directory but it bloody gets replaced there to! how to get rid of that anoying protection? for ever! //Silent.
i cant get rid of the system file protection in win2k, i tried to copy the file into dllcache directory but it bloody gets replaced there to!
how to get rid of that anoying protection? for ever!
//Silent.
how to get rid of that anoying protection? for ever!
//Silent.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Hello,
what you want to do is quite simple (sorry i'm tranlating from french...) :
- open explorer;
- click on Tools;
- File options;
- Display;
- ... and finally uncheck the right option (you'll get a warning telling you it's not a good thing to do, just accept);
- Reboot as required;
-> done !
what you want to do is quite simple (sorry i'm tranlating from french...) :
- open explorer;
- click on Tools;
- File options;
- Display;
- ... and finally uncheck the right option (you'll get a warning telling you it's not a good thing to do, just accept);
- Reboot as required;
-> done !
The following is a quote from a thread over at ARS Techica:
"WARNING: Make sure you backup before you try this! You can hose your install if something goes wrong here!
Here you go:
1. Load a copy of SFC.DLL into your favorite hex editor.
2. Go to offset 6211h and you should see '8B' and 'C6' at offsets 6211h and 6212h. If the two bytes are not these values DO NOT proceed.
3. Change both bytes to '90'.
4. Save your changes.
5. Boot into Safe-mode and replace the original SFC.DLL with your hacked version.
Now the 'ffffff9d' regkey will work as it did before.
Reghack to disable SFC:
Step 1. Open Regedit.exe and navigate to [HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows NT \CurrentVersion \Winlogon]. You should see a DWORD value named "SFCDisable" with a value of "0". Change the value data of "SFCDisable" to "ffffff9d".
Step 2. Exit regedit and reboot the machine because this will make the registry change take effect. After the machine is rebooted, you should see Event ID 64032 in the System Event logs letting you know that Windows File Protection is no longer active."
Hope this helps
Glad midsommar...
/Toby
"WARNING: Make sure you backup before you try this! You can hose your install if something goes wrong here!
Here you go:
1. Load a copy of SFC.DLL into your favorite hex editor.
2. Go to offset 6211h and you should see '8B' and 'C6' at offsets 6211h and 6212h. If the two bytes are not these values DO NOT proceed.
3. Change both bytes to '90'.
4. Save your changes.
5. Boot into Safe-mode and replace the original SFC.DLL with your hacked version.
Now the 'ffffff9d' regkey will work as it did before.
Reghack to disable SFC:
Step 1. Open Regedit.exe and navigate to [HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows NT \CurrentVersion \Winlogon]. You should see a DWORD value named "SFCDisable" with a value of "0". Change the value data of "SFCDisable" to "ffffff9d".
Step 2. Exit regedit and reboot the machine because this will make the registry change take effect. After the machine is rebooted, you should see Event ID 64032 in the System Event logs letting you know that Windows File Protection is no longer active."
Hope this helps
Glad midsommar...
/Toby
The quote from Ars is from me and it's in reference to sp2 only. Pre-sp2 installs need only the reg-hack to turn off WFP. If you have issues with messing around in your registry you can use X-teq's "X-setup" tweaking program to disable it also. You can get it here. After you install it, go to "system>software intallation>windows file protection" and disable it. You gotta reboot for it to become effective.
Toby- no prob- I wasn't looking for credit, I just wanted to make clear that this tweak is in reference to sp2 only.
what are the advantages for diabling wfp
If you have peripherals for which the Windows 2000 device drivers are not 'certified' by Microsoft, the advantage of disabling Windows File Protection is that often those devices will not work or frequently malfunction without disabling Windows File Protection.
I had been using the registry hack to disable Windows File Protection before I applied Service Pack 2 and did not realize that Service Pack 2 causes the registry hack to not function any more.
In hindsight I should have realized what was happening since the warning that Windows File Protection is disabled quit appearing in the event log after I applied Service Pack 2.
After I applied Service Pack 2 every time I printed something from my computer I got a 'blue screen' and did not know why except it appeared to be driver-related.
The actual cause of the 'blue screens' was not the 'certified' parallel-port printer drivers but the 'non-certified' parallel-port flatbed scanner drivers.
After I edited the sfc.dll file as described above, Windows File Protection is disabled again, I get the warning messages in the event log that Windows File Protection is disabled, and I no longer have 'blue screens' every time I print.
In hindsight I should have realized what was happening since the warning that Windows File Protection is disabled quit appearing in the event log after I applied Service Pack 2.
After I applied Service Pack 2 every time I printed something from my computer I got a 'blue screen' and did not know why except it appeared to be driver-related.
The actual cause of the 'blue screens' was not the 'certified' parallel-port printer drivers but the 'non-certified' parallel-port flatbed scanner drivers.
After I edited the sfc.dll file as described above, Windows File Protection is disabled again, I get the warning messages in the event log that Windows File Protection is disabled, and I no longer have 'blue screens' every time I print.