Ars Technica - Managing and Disabling Windows File Protection (7/2000)

Ars Technica - Managing and Disabling Windows File Protection (7/2000): "How to manage or disable WFP
As always, you continue on at your own risk. Be sure to do proper backups and have an rdisk handy before ever tweaking the registry.
Both registry keys in question are found at:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NTCurrentVersion\Winlogon
The two relevant keys are SFCDisable and SfcQuota. The size of the dllcache can also be manipulated at the command prompt.
To disable:
Set (or create) the SFCDisable to REG_DWORD 'ffffff9d'. (It should be currently set to '0')
Reboot.
Windows will not clean up the files, so if you want to trash them, you can, but leave the folder.
Check your event log and see that Windows has truly disabled it.
Other reports on the 'net indicate that a value of '1' will disable WFP, but this seems to reset after another reboot.

To manage the size of dllcache:
You have two options 1) the registry, and 2) the easier command prompt option:
In the registry, set SfcQuota to the hexadecimal value that's equivalent to the number of MB you'd like for the dllcache to take up.
If you don't know hex, here's some samples:
00000099 = 153 (MB).
0000004b = 75 (MB).
00000032 = 50 (MB).
0000000a = 10 (MB).
FFFFFFFF = Unlimited (default setting now)
When you're done, run sfc /snannow for good measure, and reboot.
Using the sfc command, it gets much easier. At the command prompt, type:
sfc /cachesize=X
where X is measured in MB. For instance, X=50 sets the cache to 50MB."

Comments

Popular posts from this blog

Cannot fetch a row using a bookmark from OLE DB provider 'OraOLEDB.Oracle

Manual de alarma Chevrolet

http://www.colombiasoyyo.org