[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

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!