[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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • 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
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!