Thinking UxTheme? STOP AND READ.


Recommended Posts

i really don't see how Replacer/batch files/manual installation seems to work for some and not for others..

in my case (and everyone whom i patched uxtheme on XPPro) manual installation as described by vorte[x] has worked every single time without errors.. i've only done that like 5 or 6 times tho.. the rest, Replacer is the easiest, fastest, and most reliable way to do it..

if a certain method doesn't work for you (and there's no hardware issues, obviously) you're just not doing it right..

i can understand vorte[x]'s frustration and i can just picture the countless messages he gets just because some idiot is dumb enough to get in stuff way over his head..

right on brother (Y).. i hope this will be the last time (christ, it's been 3 years since people started patching uxtheme) you'll have to explain this..

spread the joy.

  • 2 weeks later...

Just an addendum to vortex's original post.....

For anyone with doubts as to the safety of patched uxtheme.dll files I highly suggest that you patch your own original source file. Fire up a hex editor and search for 81EC800000005657 (for xp, xpsp1 and some earlier builds of sp2) or 81EC88000000A124 (for sp2 build 2126 (realy not sure when they changed the sub routine) and replace it with 33F68BC6C9C20800 (it's at offset 0x13250 in sp2 build 2126) . Save it and swap it using the manual method.

That way you have complete control over the modding and replacing of your file. :)

.....Hey vortex, is the changing of the last 2 bytes of the file some sort of mark for you?? Just curious.

... and when it doesn't work, you'll be the first to complain so. Do it the manual way and save yourself troubleshooting any problems down the line. :yes:

eh. if you use replacer correctly it works 100% just like any other method.

Before you continue, please don't misinterpret my bluntness as being "full of myself". I'm not, ask around - This is just me.

I'm sick and tired of the constant spewing of misinformation from message board to message board, therefore I took the time out of my schedule to write this up for all current and future users. Read this before wasting someone's time with your stupid questions.

Common Questions

= = = = = = = = = = = = = =

https://www.neowin.net/forum/style_images/N...-674/icon11.gif *grumble* Why does Microsoft keep changing the uxtheme.dll?

What are you talking about? This file has undergone very minor alterations. Did you not realize that this file is replaced after the application of a service pack? The signature analysis subroutine that is patched hasn't changed (or changed much) since late Whistler builds.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif Why would I use this altered DLL? This compromises overall security!

The subroutine that's patched simply and effectively skips over the theme signature check. Nothing more nothing less. You should be more worried about letting users use your floppy disk drive. If you still feel uncomfortable using the patched file, then don't and shut up. Spare us having to read your babble.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif Is there a patch for X? Where do I get it?

You can always find the latest UxTheme patches on my site at http://vReality.net (or http://vortex2050.dyndns.org:8080) I do not distribute my patches anywhere else - Mirrors claming such are lying.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif Are you the uxtheme vorte[x]?

Yes and no. I am not the originator of the patch however I do patch newer files to keep current. As far as I know, the original patch was rolled out by TGTSoft as a temporary solution at bypassing the signature checking subroutine (I say temporary because they now use kernel mode drivers/etc. to do the patching on-the-fly).

I do, what I do, to continue offering the public with a totally free alternative to their StyleXP product.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif Do you test your patches? It doesn't (insert adjective here) work!

You obviously do not know what you're doing and/or didn't install it correctly. I have only screwed up one UxTheme in my life, and I rectified the issue and pulled down the invalid file that same hour. It's unlikely you have a bad patch, trust me.

Installation, the correct way.

= = = = = = = = = = = = = =

Ok, now that we cleared that up, here's how you PROPERLY install the patched uxtheme.dll in 3 easy steps. Throw away/delete your silly patchers and whatnot as they're too slow to keep up with new releases. You DO NOT need safe-mode for this - Don't be silly.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif 1) Remove (delete) the uxtheme.dll files in the following directories in the correct order:

- C:\Windows\ServicePackFiles\i386 (if path doesn't exist, ignore)

- C:\Windows\System32\Dllcache (hidden directory, duh)

https://www.neowin.net/forum/style_images/N...-674/icon11.gif 2) Copy the patched uxtheme.dll file into C:\Windows\System32\Dllcache folder.

https://www.neowin.net/forum/style_images/N...-674/icon11.gif 3) Rename the uxtheme.dll file in C:\Windows\System32 to uxtheme.original and reboot (ignore windows file protection errors)

An alternative to using the steps above would be to use a simple batch script (put in same dir as patched uxtheme.dll)

@echo off
del /q c:\windows\servicepackfiles\i386\uxtheme.dll
del /q c:\windows\system32\dllcache\uxtheme.dll
echo Allowing WFP to do it's work... (cheap sleep hack)
@chkdsk >nul
copy uxtheme.dll c:\windows\system32\dllcache\uxtheme.dll
ren c:\windows\system32\uxtheme.dll c:\windows\system32\uxtheme.original
@shutdown -r -c "Restarting! shutdown -a to abort!" -t 10

Hope that helps clear up some things - I'll add onto this, should the need arise!

Revision 01: Spelling mistake of the word 'compromises'.

Revision 02: Fixed batch (Thanks Liquid)

Revision 03: Added disclaimer to beginning of post

Revision 04: Cleared up batch file usage.

Thanks for creating this FAQ. Mods, please make this a sticky.

It's for source control.

Yeah, I gathered that after I posted.... vx=vortex.

Anyway, thanks for responding, and thanks for the patched files. :yes:

On a off topic note.............

You wouldn't happen to know the offset/s for sfc_os.dll xpsp2 build 2126, would ya?

  • 4 weeks later...

Hi friend Vortex 2050

Congratulations, congratulations and again congratulations

YOU are the best friend on the WEB is true, why I never more have problems with Uxtheme.dll since first builds of SP2, your patch is perfect without comments, only congratulations.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
    • It is clear from this aricle that "Time Is On My Side" no matter which direction it is flowing., https://noai.duckduckgo.com/?i...m%2Fwatch%3Fv%3DsEj8lUx0gwY
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      577
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!