[Release] Universal UXTheme Patcher v2.1


Recommended Posts

October 11, 2006 - Version 2.1

Hopefully this is the last update until a new unsupported uxtheme file comes around. Anyway this update fixes a few small bugs and I managed to make it 22kb smaller than 2.0. (66.5kb vs 88kb)

October 8, 2006 - Version 2.0

I have updated the Universal UXTheme Patcher to v2.0. This release adds support for every uxtheme file currently out in existence and INCLUDES 64-BIT SUPPORT! I reworked the layout a little and fixed some file versions. Rafael Rivera had a few mistakes in his uxtheme repository that I notified him about and it has been updated as well. Every file found in the uxtheme repository is supported in this release (minus Vista).

screenshot.jpg

About

The Universal UXTheme Patcher is a tool that allows you to use unsigned, 3rd party visual styles in Windows XP, without having to use a program such as StyleXP. It works by patching out the part of uxtheme.dll that checks for the signature. This means that once the file is patched, that is it. The tool does not run in the background or anything like that.

The utility is only 66.5kb. Since this tool is so small, I am granting permission for any visual style (msstyle) creators to include it in their visual style releases. The only thing I ask is that you credit me (flyakite) in your release notes somewhere.

System Requirements

This tool will work on any operating system based on XP (Tablet, MCE, Server 2003) including 64bit versions.

Features

The utility also supports silent patching. Simply run the installer with the "/S" switch (case sensitive). During silent patching, if the patch is successful you will not be notified, it will simply remain silent. If the patch is unsuccessful however, the utility will notify you even with the /S switch.

Credits

Logo designed by Fer

Supported by Rafael Rivera (vorte[x])

What's different from this and WindowsX' patcher?

If you are wondering why I made this when there is already a tool out for this, it is because I wasn't satisfied with WindowsX version. It is slow, often alerts users about weird nt setup files on the C:\, and replaces files in a very uneffecient manner that results in Windows File Protection dialogs. My tool does none of that. His tool is also is 569kb and is less successful at doing the same thing my tool does at 65.5kb.

DOWNLOAD

Edited by flyakite

Just a quick update. I spent the entirety of last night installing Windows XP x64 in VMware and doing some research and hex comparisons, and am in the process of updating the installer to support 64bit Windows uxtheme files. I have tested it and it works successfully. You can expect v2.0 probably later today or tomorrow morning.

Updated to v2.1 (fixed a few bugs I missed when adding 64bit compatibility), and figured out a way to do some things differently so that I could make the tool even smaller (66.5kb total now). Supports all uxtheme files (other than Vista) and takes about 1 second to patch.

Edited by flyakite

Such a big word for edited text, huh? Who actually want to blame you for making one more patcher? There're plenty ones out there already even before I made it. Don't take it so personally, dude. Anyway, there's bug in your patcher. If user runs it multiple times, PendingFileRenameOperations registry will be appended again and uxtheme.dll file will be lost.

Edited by Windows X

Such a big word for edited text, huh? Who actually want to blame you for making one more patcher? There're plenty ones out there already even before I made it. Don't take it so personally, dude. Anyway, there's bug in your patcher. If user runs it multiple times, PendingFileRenameOperations registry will be appended again and uxtheme.dll file will be lost.

Uhh what? Okay I changed it to say "What is different from this and WindowsX' patcher?" The reason I even put the info in the release at all is because if I don't everyone's first comment is "What's different about yours from WindowsX' version?" I'm not saying yours sucks, I'm saying why I made mine, and what it does differently than yours. I also made mine originally for internal use with FlyakiteOSX, so I wouldn't have to rely on other people to keep their patchers updated and so that it could be run silently. Since then I've released the tool publicly and have been trying to keep it as updated as possible.

I don't think yours sucks, but there are definitely flaws, most notably Windows File Protection dialogs and NT Setup file warnings.

Also, as to the PendingFileRenameOperations business, I just tested it by running the patcher 4 times without restarting, so I had 4 sets of entries in PendingFileRenameOperations. Restarted, still had Luna. Downloaded a 3rd-party VS, and it worked fine. You do NOT lose uxtheme.dll. Actually test it before you comment please.

Edited by flyakite

WindowsX,

flyakite has developed the only patcher that patches the correct bytes, 100% of the time. All the other patchers out there, including your own, search for a hard-coded pattern of bytes. As I've told you before, this method puts the user at risk of patching the wrong set of bytes. :no:

  • 2 weeks later...
  • 1 month later...

I ran the patcher, restarted. Place the msstyle in the resources folder under windows...nothing. Restarted thinking it had to refresh?...still nothing. Any suggestions :)

*Edit: never mind, it was just the theme i was trying to install...was nice too :( :p

Edited by Elessar
  • 1 month later...

This is my first post on this forum, so excuse my ignorance. I'm assuming this Theme Patcher can be implemented into a good unattended install (my definition of good may differ from yours).

I got a late start on the whole unattended install bit, so I'm still working on making an unattended install disk that does everything. I've hit a lot of roadblocks, but --thus far-- there have been work-around. For instance, on Microsofts knowledge base site, it said that XP wouldn't boot and install from a DVD.... not true. It can be done.

The purpose is to have the unattended install, updates, hotfixes (if needed), configuration, and third party security software all installed using one disc with no interaction. Getting closer. Third party security software has taken some time to get familiar with the command line switches for proper install using some batch file(s), and then the batch file has to pull a script to set the 3rd party prog up with the correct options. I found it intriguing at first, but now just want to have something that works.

Sorry to ramble, the question was: Can this (any of these "theme changers" be implemented directly using the unattended crap (automated supplied by MS), or will I be writing more batch files?

Hi :)

My first post so be gentle!

I just tried to use the Neowin UXTheme Multi-Patcher v4.0 to allow a female friend to use the Quevista style on her PC but it brings up a error stating something about a 16 bit MSDOS subsystem...

Any ideas what could have caused this?

Also.. will this patcher be a better option?

Thanks for any help :)

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

    • No registered users viewing this page.
  • Posts

    • Google are hyprocrites for signing this. They have been pulling the same dirty tactics as Microsoft, only they do it on Android and ChromeOS.
    • In some countries the law has forced Microsoft to display a menu on a fresh install of Windows which asks which web browser you want and it will install that browser. This doesn't add any bloat to Windows. It simply an additional step when setting up a new PC.
    • Chrome is also a first party browser on Android and ChromeOS. And on those systems, Google is pulling the same dirty tactics as Microsoft does on Windows.
    • Unofficial script lets you install unreleased Windows 11 features without Microsoft Account by Sayan Sen Microsoft has been steadily evolving the Windows Insider Program over the years, introducing new channels and testing paths that allow enthusiasts to experience upcoming and yet-to-be-released Windows features (some interesting hidden ones too) before they reach the public. However, one long-standing requirement has remained largely unchanged as users are generally expected to enroll in the Program and with a Microsoft account. That's where a third-party tool called "OfflineInsiderEnroll" can help. OfflineInsiderEnroll is said to be a lightweight script that enables access to Windows Insider Program builds on systems that are not signed in with a Microsoft account. Essentially the tool configures the necessary Insider settings locally and hence allows users to select and switch between available preview channels while continuing to receive builds through the normal Windows Update channel. If you are wondering how it manages to do so, it is made possible by a Registry value known as TestFlags. When configured to"0x20", Windows stops communicating with Microsoft's online Insider enrollment services thus preventing locally configured Insider settings from being overwritten. This allows the script to apply its own channel configuration directly through the Registry as Windows Update does not verify whether a device has been officially enrolled in the Insider Program or not. Previously the utility has had already supported the traditional Insider branches including Dev, Beta, and Release Preview. However following Microsoft’s recent restructuring of its preview channels, the script has now been updated. The latest OfflineInsiderEnroll version, 2.6.6, adds support for the newly introduced Insider channel lineup. As such, users can now choose from several Experimental channels in addition to Beta and Release Preview options. The update also retains tools for refreshing the Insider cache, resetting Insider settings, and completely stopping Insider enrollment when needed. Keep in mind though that will need elevated privileges when running the script (run as Admin). You can get the latest version of OfflineInsiderEnroll from this page on its official GitHub repo.
    • The "Classic" Outlook has done that for a few years as well. The option to even change that is really hidden away too... It really shouldn't be hard to respect user defaults. Sadly we are the product now, not Outlook. To change in the Classic Outlook: File > Options > Advanced > change "Open hyperlinks from Outlook in"
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!