Recommended Posts

These files are ready for an unattended CD and SFC_OS.DLL/UXTHEME.DLL can be used to replace an existing file on a system with SP3 installed (you'll need a Replacer program).

Service Pack 3 ENU (5.1.2600.5512)

Disable Windows XP File Protection permanently without registry

Unlock Windows XP Setup - Enable edition of syssetup.inf

Unlock Windows XP Visual Styles (Themes)

--------------------------------------------------------------------------------

Service Pack 3 FRA (5.1.2600.5512)

D?sactiver la Protection de fichiers Windows de fa?on permanente sans registre

D?verrouiller l'Installation de Windows XP - Permettre l'?dition de syssetup.inf

D?verrouiller les Styles Visuels de Windows XP (Th?mes)

Edited by janedoe
Link to comment
https://www.neowin.net/forum/topic/636532-sp3-patched-files/
Share on other sites

I don't know if these files are legitimate especially since you're a resident one post wonder. Still, I'd test out the files but at the moment I don't have a machine with Windows XP SP3 installed. :/

I don't know if these files are legitimate especially since you're a resident one post wonder. Still, I'd test out the files but at the moment I don't have a machine with Windows XP SP3 installed. :/

Anaron,

These files are from the SP3 RTM and I use the same patching since SP2 but to be honest I didn't test them if they worked with SP3. One thing is sure... the same patches for SP2 worked great and was time tested.

I'm gonna test these new files on my side to be sure of the quality.

jdoe

Anaron,

These files are from the SP3 RTM and I use the same patching since SP2 but to be honest I didn't test them if they worked with SP3. One thing is sure... the same patches for SP2 worked great and was time tested.

I'm gonna test these new files on my side to be sure of the quality.

jdoe

I see. Be sure to post back soon!

  • 1 month later...
These files are ready for an unattended CD and SFC_OS.DLL/UXTHEME.DLL can be used to replace an existing file on a system with SP3 installed (you'll need a Replacer program).

...

Can you describe a systematic procedure to patch the SFC_OD.DLL file in any language? Here is reported a method that disable WFP on SP3 RTM, but it works only with a registry mofication.

Thanks

Can you describe a systematic procedure to patch the SFC_OD.DLL file in any language? Here is reported a method that disable WFP on SP3 RTM, but it works only with a registry mofication.

Thanks

I can't have a look of all languages version of this dll but if it can help, I'll try to give you the informations that you *should* need.

To avoid the need of a registry edits to make the patch working, all other values of SFCDisable must be skipped. This is why my patch do a jump where it have to, like if SFCDisable was FFFFFF9D all the time (no matter what the real value is).

At the hexadecimal offset EC84 (or around this offset) you should find the following assembly...

cmp eax, FFFFFF9D ; 83F89D

jne 76C1F891 ; 7508

xor eax, eax ; 33C0

inc eax ; 40

Which is translate to machine code as 83F89D750833C040

You need to search for this byte patterns and replace these 8 bytes by 3BC0EB3290909090

cmp eax, eax ; 3BC0

jmp 76C1F8BA ; EB32

nop ; 90

nop ; 90

nop ; 90

nop ; 90

Hope it helps

I can't have a look of all languages version of this dll but if it can help, I'll try to give you the informations that you *should* need.

To avoid the need of a registry edits to make the patch working, all other values of SFCDisable must be skipped. This is why my patch do a jump where it have to, like if SFCDisable was FFFFFF9D all the time (no matter what the real value is).

At the hexadecimal offset EC84 (or around this offset) you should find the following assembly...

cmp eax, FFFFFF9D ; 83F89D

jne 76C1F891 ; 7508

xor eax, eax ; 33C0

inc eax ; 40

Which is translate to machine code as 83F89D750833C040

You need to search for this byte patterns and replace these 8 bytes by 3BC0EB3290909090

cmp eax, eax ; 3BC0

jmp 76C1F8BA ; EB32

nop ; 90

nop ; 90

nop ; 90

nop ; 90

Hope it helps

Sure, it helped.

Thanks.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!