UxStyle Core Beta bits now available
In March, I announced that my unsigned theme patch-less vision was being realized. Today, I’m happy to let everyone know beta bits of UxStyle Core are now available for public testing!
UxStyle Core does not currently have a theme manager or even a UI. UxStyle Core is exactly what it sounds like – the absolutely bare minimum (core) needed to enable third-party theme usage. Nothing more, nothing less. Later in the beta, we’ll push out a “bundle”, containing both the core software and a theme manager developed by our close partners.
Install UxStyle Core. Download some themes. Give them a whirl, everything should “just work”. Let us know how it went, bad or good, in the forums.
Thank God, no more patching.

That’s an awesome tool. I’m sure now using 3rd party themes would be a lot easier for people.
Awesome let me test this on Win vista and win 7 thanks for the share..
Awesome.
Superb !!
thanks Rafael :)
Thats wonderful, Rafael !
Checking it out.
An Awesome, Quick and Simple tool. Great work :)
thats a good job rafael, now i dont need to crack my head for theme patch….
SV33T!!!
Worked great on a copy of Xp that uses only 40mb of ram, next to test it on FLP and beta releases too =P
Awesome tool but ugly logo.
I like the logo.
What I don’t get is, why switch from a simple file patch to a kernel driver and added overhead (vs. zero overhead)
@ASF: Because a patched file has to be repatched every time you update windows, whereas a kernel driver “patches” while starting
I found another great use for this: Windows 7’s XPM, skin your XP to look _kinda_ like your current install, you don’t get glass, but it will still be an improvement over the ugly XP theme.
Installed it on Windows Seven RC without a problem and reposted this stuff on my blog.
And thanks a lot for including the short version of license, with stuff that actually makes sense. If only the big companies started doing this :sigh
Rafael,
Your name is all over the web because of this. Its a great tool and I really enjoy it. Thanks for sharing with the world. Also I was able to go back to Hawaii for a couple weeks. Good times, went back to Schofield and saw how much it has changed.
Thanks for it. I will give it a shot.
Why does this app try to make internet contact ?
hey men, i don’t know what i do wrong, but it’s don’t work in my vista ultimate x86… A problem stop the run32dll process :(
what am i doing wrong?
I don’t speak in inglish sorry about errors!
@pizzaboy192: You should probably know what you’re talking about before you correct someone. If you patch in memory you don’t have to redo anything if you patch in memory. Only when you replace the uxtheme.dll physically do you have issues. We’ve patched in memory and installed 2 Service Packs and made sure all updates were downloaded and never once had to fix the patch we use which was created by Andreas of AVEDESK. So get your facts straight first.
@Jeff: I’m a bit confused. Isn’t that what pizzaboy192 said?
@jeff: And I quote myself
“pizzaboy192 June 22, 2009 at 12:27 pm
@ASF: Because a patched file has to be repatched every time you update windows, whereas a kernel driver “patches” while starting”
what you said is basically a lengthier version of the same comment I made, but yet making it sound like I’m an idiot… I congratulate yourself for that amazing effort on your part for reading and comprehending someone else’s comment.
Sounds a lot like he’s saying the patch would break and have to be repatched due to failure.
“@ASF: Because a patched file has to be repatched every time you update windows, whereas a kernel driver “patches” while starting”
I’ve updated Windows numerous time and have never had an issue. What’s the difference of patching automatically in memory when Windows starts up or patching the kernel when Windows starts up?
No. What you’re saying is wrong pizzaboy. You do not have to repatch every time you update Windows when you do it in memory. I have never come across a single update that broke the patch we’re using. Not one. And i’ve installed plenty of Windows updates where i didn’t have to reboot and nothing broke.
@Jeff:
There isn’t a difference, being that they are the same thing. The program you use is also a kernel driver, like Rafael’s, and the difference between a Kernel driver and a patched system file (like what Rafael used to do) is that a system file (Uxtheme.dll) will be overwritten every time you update.
You don’t patch the kernel with Rafael’s patches, you just patch a single system file.
The advantage to using a Kernel driver (A.K.A. Program) is that you don’t need to download the latest patch, or repatch and hope Windows Update doesn’t kill your patched file.
First, do you have a name other than pizzaboy?
I’ve never seen our patch get killed. It’s been over a year since we’ve been doing this. Now when i hear of someone saying you have to repatch i’m reminded of the days of StyleXP where every single time there was a SP, StyleXP died a sudden death. Just not that way with our stuff.
Not sure what was meant so I’ll help clarify by outlining the pros/cons…
Offset-driven patches (on disk) [e.g. VistaGlazz, all the popular patchers]
Pros: No running services, drivers
Cons: Difficult to do, error prone, invalidates Windows baseline, could cause instabilities if updates are not in sync, not-cross-platform.
Offset-driven patches (in memory) [e.g. PC Tools]
Pros: No replacement of files needed, easy to install
Cons: Could cause instabilities if updates are not in sync., not-cross-platform, increased developmental effort
Dynamic disassemblers (in memory) [e.g. UxStyle]
Pros: No replacement of files needed, easy to install, works across platforms granted no major structural changes
Cons: Increased developmental effort
@jeff: I do have another name, but I don’t use it for security purposes…
As for the patches, any program, weather it be your’s, Rafaels, StyleXP (yes, it is a kernel driver), TuneUp utilities, or “Uber 1337 Patch” (as an example) are all programs that instead of physically patching a file, they modify Windows’ memory to allow it to load unsigned themes. (That is my guess, I don’t code, and am too lazy to ask for a real answer, so correct me if I’m wrong)
The person who asked why Rafael’s program is so much better than his patches gets the simple answer: Because the patched file (Uxtheme.dll) is replaced in every startup. A program, wether Rafael’s or not, that “patches” for you, does not apply to those rules, since it doesn’t physically modify the system files. Rafael’s files are\were there for those who didn’t mind re-copying the files, but it is just easier for Rafael to write a program that does all the dirty work for him, and that way he isn’t bugged with emails every Patch Tuesday saying “OMG TEH PATHC BROK! FIX IT NAO” (lame attempt at humor there).
Your program is (in theory) the same as Rafael’s, but is nowhere near what Rafael’s patches did.
So… just to clarify, Rafael’s program is not a patched system file, but a kernel driver, used to “trick” windows into letting you load custom themes. His program does the same thing (in theory) as any of those programs you pay for to allow you to run your favorite theme on XP, Vista, 7, FLP and many others (I’m just guessing again, haven’t had a chance to see if they work on whistlers or longhorns yet)
Well that’s just it. I have never seen “instabilities”. Ever. Considering I’ve done every single update all the way to SP 3 and have never seen our patch break, I’m not sure how you can state this as a “clarifying” fact. Now if you said: “in some cases…” :-)
In the end, seriously who cares how its patching as long as its safe and it works? Like i’ve said the patch process we use for XP has performed flawlessly. That’s all i care about. I don’t sell software, i sell the themes we create. The software is made so that i have my own distribution platform to release them on.. theme, icons, etc. If Rafael’s works great, then awesome. But i don’t want people saying his way is the only really good way since its not. It may be good but its certainly not the only way that works. That’s all i’m saying. In the end, to me, its all about the themes not what makes them run.
Thanks A Ton Rafael!!! Works great on Win 7…
I could finally test msstyles I created on the builds u havn’t released patches for….
I personally like the disk-file patches since they don’t require extra constantly-running services or drivers. I try to trim as much as I can (although I tend to avoid trimming drivers since that’s asking for trouble if I trim the wrong thing) and I have my XP system down to 3 svchosts and a few other service processes.
Not sure if I agree with your cons about disk patches Rafael. As long as proper hashing is done before and after a patch, and the original file is backed up, I wouldn’t see a problem since any patching errors would be caught before the system file is replaced. Only con I can see is that if MS releases a Windows Update that overwrites the file then a new patch has to be created. Uxtheme on XP isn’t updated all that often though, I think it was just every SP for the most part. But yeah the big con is that a patch has to created for every individual DLL build… quite tedious, as I’m sure you know. :)
Hey By the way my visual styles worked great(prev comment above) after I stoppd the uxsms service & started it..
But After the first reboot the visual style stopped working & windows reverted to classic style…
Whatever it was, I reinstalled uxstyle again but I wasn’t able to get my visual style to work…win 7 build 7201…can you help out?
Is this the Win7 Starter bg image workaround you spoke about before?
Yo does this work on server 08 R2?
Nevermind.
Doesn’t work on my windows 7 :(
Now using 3rd party theme is not painfull, thanks for this.
Great job! It just works! Congrats. No more annoying patches. HURRAY!!!!!
Installed it on 7 6.1.7600 cannot find any trace of it. dunno how to even find where to open the thing