Jump to content

Recommended Posts

Posted

If you want to disable windows file protection then do this

Download This

ok after that unzip the files and replace the sfc_os.dll in the dll cache with the downloaded one then go into the system32 folder and rename sfc_os.dll to sfc_os.old and put the downloaded sfc_os.dll in its place then run the reg file that was with the download.

And Re-boot and Your Done NO MORE STUPID FILE PROTECTION.

:)

I will post an update when i have done it for Windows Sever 2003 and Windows 2000 Pro SP4


Posted

I don't think the file protection is a stupid system. It is more safe to do a Safe Boot restart and put the files you think to be OK then to straight disable it. But well, depends what you want to do heh :)

Posted

Say you have a unattended Windows XP Pro CD and you want to copy the the uxtheme.dll patch or your own shell32.dll but very time you do Windows File Protection stops you and restores the old version so you see why i have posted this becuase some people like to have they own icons and hacked version of thing and this help to do that.

ok its maybe not stupid be it can be.

:)

Posted

you will need this as well

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"SFCDisable"=dword:ffffff9d

If you didnt know you can throw the sfc_os.dll in the oem dir.

$OEM$\$$\SYSTEM32\sfc_os.dll

$$ is the windows dir. I have a modified system.ini and my wallpaper in there.

I have a inf folder in $$ with a modified sysoc.inf.

It replaces the sfc_os.dll without any copy commands and you could use it as well for your uxtheme.

Posted

I suggest you to reenable WFP after replacing system files, importing this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"SFCDisable"=0

WFP isn't stupid at all for me :)

Posted
:) snooz that why i posted this so other people could do the same as you and me without having to hex edit it them else or make the reg file i post a download link.
Posted
you will need this as well

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"SFCDisable"=dword:ffffff9d

If you didnt know you can throw the sfc_os.dll in the oem dir.

$OEM$\$$\SYSTEM32\sfc_os.dll

$$ is the windows dir.  I have a modified system.ini and my wallpaper in there.

I have a inf folder in $$ with a modified sysoc.inf.

It replaces the sfc_os.dll without any copy commands and you could use it as well for your uxtheme.

i no that you can do it with the sfc_os.dll but say i had a hacked explorer.exe could i put that in there and in would work?

Posted

This sysoc.inf i thought you could just put the file in the $OEM$\$$\SYSTEM32 folder and it did it by its self but you say you modifed the sysoc.inf to copy over the orinagl in setup or am i miss reading your post?

Posted

Terminator3: is that sfc_os.dll hacked for xp os xp-sp1? cus you have to change different offsets for xp & sp1.

Windows XP (no Service Pack)

At offset 0000E2B8 (0E2B8h) you should find the values "8B" and "C6".

Windows XP (Service Pack 1)

At offset 0000E3BB (0E3BBh) you should find the values "8B" and "C6".

please let us know which one

Lee

Posted
you will need this as well

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"SFCDisable"=dword:ffffff9d

If you didnt know you can throw the sfc_os.dll in the oem dir.

$OEM$\$$\SYSTEM32\sfc_os.dll

$$ is the windows dir.  I have a modified system.ini and my wallpaper in there.

I have a inf folder in $$ with a modified sysoc.inf.

It replaces the sfc_os.dll without any copy commands and you could use it as well for your uxtheme.

i no that you can do it with the sfc_os.dll but say i had a hacked explorer.exe could i put that in there and in would work?

Yeah, I'd like to know as well. What are the limitations? Can we replace any system file by just placing it in the correct $OEM$ folder?

Posted
If you didnt know you can throw the sfc_os.dll in the oem dir.

$OEM$\$$\SYSTEM32\sfc_os.dll

$$ is the windows dir.  I have a modified system.ini and my wallpaper in there.

I have a inf folder in $$ with a modified sysoc.inf.

It replaces the sfc_os.dll without any copy commands and you could use it as well for your uxtheme.

If i put the edited sfc_os.dll in the $OEM$\$$\system32 folder, do i still have to apply the reg for it???

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"SFCDisable"=dword:ffffff9d

if so, when is the best time to enter it??? at the beginning of my setup.cmd script, also do i still have to eject the cd or will it no longer matter????

OH yeah, the wallpaper, does it need a certain name???? and type???? ie: wallpaper.bmp

Thanks for your help

Lee.......

Posted

Terminator 3:

i no that you can do it with the sfc_os.dll but say i had a hacked explorer.exe could i put that in there and in would work?

If you put a hacked explorer.exe in the root of $$ yes it would replace it.

This sysoc.inf i thought you could just put the file in the $OEM$\$$\SYSTEM32 folder and it did it by its self but you say you modifed the sysoc.inf to copy over the orinagl in setup or am i miss reading your post?

I placed it in the INF folder inside $$. It then writes over it.

Geckotek

Yeah, I'd like to know as well. What are the limitations? Can we replace any system file by just placing it in the correct $OEM$ folder?

Yes.. $$=Windows dir so to replace sfc_os.dll create a SYSTEM32 and put the dll in there.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...