Stardock Forums
I need a theme on ux theme patcher to complement windowblinds. Will they conflict?
Hello,
I am not sure since I don't use UX theme Patcher. Perhaps someone with more knowledge on it will come in and share some information.
Thank you.
Basj,
Stardock Community Assistant.
In my view using UX Theme Patcher is a risk. Unless you really know what you are doing, and know how to back up your important files and registry, not to mention knowing how to create restore points and how to use system restore, I would not go there. You would be a lot safer to just use Windowblinds alone. Now, as to whether the two have a conflict, I am not sure, but to use both on the same system seems risky to me. I wouldn't.
Leo, the Brave browser AI says WB and SecureUX work on different levels so will probably not conflict, if you decide to try it, please report back.
WB is the safest way to customize. Add Start11 to it.
Bear in mind that AI isn't always correct. Also, create a restore point and a backup before installing.
Also, despite the claim SecureUX doesn't alter system files, run sfc /scannow after uninstalling SecureUX Theme Patcher if you encounter problems with WB.
Supposedly it won't break Windows updates, but I don't know if that applies to 24H2 or not.
It will 100% break windowblinds. Most custom themes out there now a days use modified dll files for file explorer to render certain elements. I definitely would not recommend using it alongside windowblinds. Windowblinds is the safest way to theme windows without breaking things. Windowblinds was designed for Vanilla windows (unmodified) Adding any other tweaks out there adds more ways for things not rendering properly.
According to Brave's A.I. Leo:
"Based on the provided search results, SecureUxTheme patcher does not use a ux.dll replacement file. Instead, it employs an in-memory patching approach, which means it modifies the system’s behavior without altering the original uxtheme.dll file.
As mentioned in the search results, the patcher hooks and stubs out only signature verification import calls from uxtheme.dll and other related DLLs, without relying on any internal code or binary layout of these files. This approach allows the patcher to work across different Windows versions, including Windows 11, without requiring a replacement file.
Additionally, the project’s GitHub repository and documentation emphasize the in-memory patching mechanism, stating that the current code does not depend on any code, binary, or memory layout of uxtheme and related DLLs, making it compatible with future changes to how themes work in Windows.
Therefore, to summarize, SecureUxTheme patcher does not use a ux.dll replacement file, instead opting for an in-memory patching approach to enable custom theme installation without modifying the original system files."
I looked at several sources, as well and Leo is accurate as to the non-usage of ux.dll replacements, and does not alter system files.
That, in and of itself, doesn't mean it'll play nicely with Windowblinds, but on that specific question, Leo answered they won't interfere with each other, FWIW.
Nah Im talking about the actual theme dll files. The one in question is under:
"C:\Windows\Resources\Themes\aero\Shell\NormalColor\shellstyle.dll"
A lot of themes use some hacky dlls to do things such as add custom details pane stuff back to control panel and to also add multi colored panes, animations etc.. These 100% break on Windowblinds since it does not know what to do with the added lines of code. I know this stuff as I use to make custom themes before Windowblinds. It was never about the theme patchers, but the dll files in the themes along with the msstyle.
According to Brave's A.I. Leo:
"Based on the provided search results, SecureUxTheme patcher does not use a ux.dll replacement file. Instead, it employs an in-memory patching approach, which means it modifies the system’s behavior without altering the original uxtheme.dll file.
As mentioned in the search results, the patcher hooks and stubs out only signature verification import calls from uxtheme.dll and other related DLLs, without relying on any internal code or binary layout of these files. This approach allows the patcher to work across different Windows versions, including Windows 11, without requiring a replacement file.
Additionally, the project’s GitHub repository and documentation emphasize the in-memory patching mechanism, stating that the current code does not depend on any code, binary, or memory layout of uxtheme and related DLLs, making it compatible with future changes to how themes work in Windows.
Therefore, to summarize, SecureUxTheme patcher does not use a ux.dll replacement file, instead opting for an in-memory patching approach to enable custom theme installation without modifying the original system files."
Ah. No argument there. They, unlike WC have no strict Moderation and get posted on all sorts of sites.
Not truth at all. I have both uxtheme.dll patched and Windowblinds 11 installed on Win 11
The both working fine. However,every new system updates from MS,it broke patched uxtheme.dll,since it returned to default one. Of course Windowblinds 11 has none of this issue which is much superior.
Again please read. It has nothing to do with uxpatch. But with theme .dll files inside the theme folder you download. These are touched by most custom themes out there (I have made custom themes from winxp to win10, you can easily verify these with a resourcehacker tool). It has been like this since windows xp up until now. You can apply themes and have windowblinds enabled but you will encounter issues. And for good measures, stardock recommends you do not try to mess with system files as it can have adverse effects. A lot of the time you will see new threads popped up here asking why some things are not skinning or running, its due to the fact that people tend to run other hacks while trying out windowblinds/start11.
Not truth at all. I have both uxtheme.dll patched and Windowblinds 11 installed on Win 11
The both working fine. However,every new system updates from MS,it broke patched uxtheme.dll,since it returned to default one. Of course Windowblinds 11 has none of this issue which much is much superior.
i will try this. but before i will make a system restore point. thanks everyone!
Again,I have since done so from XP,has no any problem regarding MS theme and WIndowblinds. They are different engine which run in tandem fine. Your fearmongering just busted.
Gasparshooters, SimplexDesigns is not referring to the engine. I misunderstood him as well. He is referring to the themes themselves. Their dll files (many of the themes' dlls) are sloppy and not built well and they cause the problems.
I understood that. The thing is that weren't the problem running patched uxtheme.dll with Windowblinds on the system from user point of view. So he claimed ".....dll files in the themes along with the msstyle. These 100% break on Windowblinds" is 100 % false. However,I am not a skinner whom making skins for MSStyle or Windowblinds,so mayhe he was referred to that situation that I don't know.
What im talking about is not the theme patcher, but inside the themes themselves. Each theme downloaded off the internet uses custom dlls that can and will break with windowblinds. Stardock does not in fact code windowblinds to use those custom hacks. When you make a custom msstyle for windows, you are not just changing images, you are altering the code for the various sections inside the theme's hex codes, thus altering how it displays. Its more than just msstyles for themes you know, it also has custom dll files inside this area that also gets altered. (I have done theming for a really long time and I know a lot of stuff behind the scene on the windows customization scene)
"C:\Windows\Resources\Themes\aero\Shell\NormalColor\shellstyle.dll"
You usually end up with various elements that windowblinds renders as classic mode or just not at all, this stuff just breaks things thus why stardock says its best not to use other 3rd party altering methods along with windowblinds. Things break and there is no buts about it. Im not fearmongering, I spitting straight facts. It has been an issue on here for a long time. There are tons of threads throughout the years of post with issues running windowblinds due to them using various hacks/tools.
People can choose to do so but dont come posting here asking why something is not working when its been told time and time again why. I have said my peace and moving on.
Still peddling non-facts. 
It's fine that your experience has been great with UX theme patchers, Gaspershooters, but I have been trying out a lot of these UX patchers for more than 20 years - always with Windowblinds installed alongside - and absolutely none of them have worked 100% with Windowblinds. None. And most of them have caused system errors or ceased to function at all after a Windows update or something else. My 2 cents.
I think I said it before that after Windows updates,it broke patched custom MS themes not render rightly....................never mind.
Welcome Guest! Please take the time to register with us.
WinCustomize Forums