UxTheme.dll Unlocked... step by step


Recommended Posts

I got tired of all the lame people asking for cracks or serials to TGTsoft's StylesXP. StylesXP was originally a modified dll, and a dll you can make yourself. I even provided that dll to people so they could use any msstyle they want, however these same people insisted on being lame and wanting to warez stylesxp even after I provided the legal unlocked dll. I was even accused of working for TGTsoft after I stated that you can do this yourself and provided the dll. Those lame people just don't get it, maybe I should have named this thread "Make your own warez."

Satire aside, here is how you all can make your own UxTheme.dll that allows you to use any .msstyle theme without StylesXP. This just removes the MS requirement for digital signing on the dll. I was not the original genious who figured out where in the dll the digital signing resided.

1) Backup UxTheme.dll to UxTheme.000

2) Don't blame me if you screw this up, these directions are as is in their somewhat correctness and I am not responsible for the government raid that will happen if you conduct this change. I have tested this and it works for me and the 500 other folks who have used this method. Do not put tinfoil in the microwave.

This is very simple to do and amuonts to changes to 17 values and takes less than five minutes to do. This also assumes you don't have StylesXP installed on your system and that you are working with the original UxTheme.dll

3) Open UxTheme.000 in a hex editor, not resource hacker.

4) Replace the following 4 sections in the hex code with the values I provide. You will need to use the

search function in the editor to find the exact address within the file to perform each edit

Adress: 0x00009C27

Original: 02

New Value: 00

Address: 0x0000B624 --> 0x0000B629

Original: 0F 8C 80 00 00 00

New Value: 90 90 90 90 90 90

Adress: 0x0000B6BB --> 0x0000B6C2

Original: 81 EC 80 00 00 00 56 57

New Value: 33 F6 8B C6 C9 C2 08 00

Address: 0x0000B71E --> 0x0000B71F

Original: 7C 38

New Value: 90 90

5) Check your changes, make sure you did not use the letter O in place of zero. SAVE

6) Reboot to safe mode, rename UxTheme.dll to UxTheme.bak ... and rename UxTheme.000 to UxTheme.dll

7) Let me know if it works, I just made this up so I am curious to see what happens.

Link to comment
https://www.neowin.net/forum/topic/8368-uxthemedll-unlocked-step-by-step/
Share on other sites

when your computer first boots up, and the white bar starts to scroll across your screen (before the boot logo pops up), jam on the F8 key. A menu should come up, just select Safe Mode and press [Enter] and that should do it.

Originally posted by mmaacckkoo

I'm not an ideot, but I do not know how to boot into Safe Mode in XP. Can anyone help?

Ishmael, I love you man!! That's a huge help.

also... I have UxTheme.dll and UXtheme.dll.tgtback which should I use?

Use the one without tgtback. Erm... that would mean you won't have to edit the dll file yourself.. cos that one is already modified.

Yeah I don't know which UxTheme.dll to use if you have many copies left over after uninstalling StylesXP. The reason being that over the versions of StylesXP, once they moved to version 4 they stopped patching the dll. Over the various versions if you just kept installing them I imagine it did different replacements each time. I do not know if they replaced the previously patched dll with the original though.

The test is: if you uninstall StylesXP and can still use all your themes, it did not replace the patched dll with the original. You therefore do not need to do my hack.

I used Hex Workshop to compare my revisions to the original dll and make this guide. It is a fine hes editor. I also use XV132, which is a great hex editor.

Ishmael

also... I have UxTheme.dll and UXtheme.dll.tgtback which should I use?
Uxtheme.dll.tgtback is the orignal dll file which is backed up during the install of Styles XP, when you uninstall styles XP it puts the orginal back.

For Hex editor go to download.com and download any freeware hex editor that you like.

) Let me know if it works, I just made this up so I am curious to see what happens.

So this whole thread is BS is what your saying.....

I am not responsible for the government raid that will happen if you conduct this change. I have tested this and it works for me and the 500 other folks who have used this method. Do not put tinfoil in the microwave.

HAAAAAHHHAAA funny sh*t....put your hands up and come out with the illegal uxtheme.dll

A friend put a pop tart in the microwave in the wrapper didn't know there was tinfoil in it and it fried the microwave......pretty cool light show though!

I've had reports from some visitors that this is a warez post.. IMHO its not so long no-one posts a hacked dll on this forum. Im not sure how Microsoft responds to tutorials on hacking a dll in Windows but will leave it for now until told otherwise.

This was a F.Y.I only so don't take it the wrong way. Its a means to show that I did not ignore the emails that were sent in.

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

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do; get an innate understanding of the night sky or a "quicker" path to astrophotography end results. I put "quicker" in quotes because with my Dwarf 3, I easily spend 3-4 hour sessions, half an hour driving to an un-light polluted place, setting up the smart scope + tripod for equatorial tracking, spending a few hours shooting, merging photo sessions, etc. It's something I still need to set aside a good part of an evening to do, all in all. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!