Update (05.10.07): If you wish to disable SFC, I'd recommend a program like nLite to do it as it is more advanced than this. This no longer exists and my website either.

Update (27.05.05): I've noticed a lot of people are still coming to my website for these instructions. At the moment, our website is undergoing a redesign and this information is currently not available. I suggest using a program like nLite for this purpose. Thankyou.

EDIT: FIXED HEX EDIT. PLEASE REDOWNLOAD!!

Here is my SFCSetting hack for WFP...

At offset (00000F82) change:

CODE

44 00 69 00 73 00 61 00 62 00 6C 00 65

to:

CODE

53 00 65 00 74 00 74 00 69 00 6E 00 67

At offset (0000ECE9) change:

CODE

33 C0

to:

CODE

EB 01

Simple as that. I've also attached the hacked SFC_OS.DLL for use on the Windows XP CD.

Follow the instructions at http://unattended.msfn.org for the hacked SFC_OS.DLL file but replace it with this file instead...

Edit: Re-attached the SFC_OS.DL_ file with better compression (thanks RyanVM).

Edit2: The attached file can be placed straight in the I386 folder WITHOUT modification.

Edit3: For people getting confused about how to apply this properly and what version it's for, follow the instructions at http://www.mantrasoftware.net/index.php?a=xpsp2. The files there and the file attached here are for Windows XP Service Pack 2 RTM (Build 2180).

Edit4: You DO NOT need the sfcfiles.dll file, found in this thread, to disable WFP. The sfcfiles.dll file only allows you to delete files and folders in the Program Files directory. It doesn't disable WFP.[attachment=2301:SFC_OS.DL_]

This post has been edited by Denney: Oct 4 2007, 10:22 PM

How would I go about removing a certain directory (in this case Program Files and everything under it) from being watched by WFP? There was post with a hacked dll for SP1 a while back, but I didn't find it in a search. Besides, I don't remember there being much in the way of instructions for making a new version of the dll.

Use the information on the unattended page here (just replace the file there with this file here):

http://unattended.msfn.org/xp/wfp.htm

RaveRod again, eh. Why am I not surprised?

Thanks, Mate! You always are watching out for us lazy ones! Perhaps I need not ask ... but have these been PEModified?

Sure have. Just put the file on the CD and away we go!!

Edit: Make sure you have the registry edit as well.

Has this version be properly modified so that setup won't complain? (Like what running ModifyPE does)

sry 4 being noob, but what file is doing exactly?

+1

what does it for?

+2

@ Adiel, OMERZEN & DaLurker:
If you would just follow the link provided you would find the answer t oyour question.

If you look on the unattended website (like I said), you would know that it allows you disable Windows File Protection so you can overwrite/delete protected files during and after Windows setup.

@captdilly: Yes is has. I stated that in my last post when GreenMachine asked me.

NOTE: The file you download from here can be put onto your Windows XP CD WITHOUT modification.

TO THE ~100 DOWNLOADS, PLEASE REDOWNLOAD!!! I DIDN'T TEST MY HEX EDIT!!!

The new version attached should work. Note: The old one WON'T work.

I should rephrase myself. I want WFP active, but I'd like to keep it from protecting everything in and including the Program Files directory (So I can, for example, remove an empty WMP directory ). There was a hacked sfc_os.dll for SP1 that did this, but there isn't a version for SP2 yet (that I know of). I was hoping someone could help me in editing sfc_os.dll to suit my needs. Oh well, I'm sure I'll figure something out.

Does the hive file have to be edited, or will adding the registry entry be enough? The hive file entry is only if you want it disabled during setup, right?

@Bachus: There is a post here that edits the "sfcfiles" file to remove protected directories. You cannot do what you want to do with the "sfc_os.dll" file.

@RyanVM: Yes the hive does need to be edited (or you can import the registry entry during "cmdlines". If you import the registry entry during "RunOnceEx", WFP won't be disabled until the second boot.

RaveRod
Hey
thaNX for the info. We're running SP2 build2179 & prefer to stick with this RTM release, which is working well for us. The value @ offset ECEA = C0 (not C9). All other values are as you posted for 2180...

...sorry - found the answer here

Is the manually applied registry value name "SFCDisable" or "SFCSetting"?

thaNX

@visitor: The "SFCSetting" registry value should be set to "ffffff9d" if you want to disable WFP. The "SFCDisable" registry value is now useless (just there to trick Windows).

Build 2179 isn't RTM by the way. It was going to be but they had to fix a few more little bugs and application compatibility. Build 2179, I think, will expire is 180 days.

Re-attached SFC_OS.DL_ file with better compression (thanks RyanVM).