You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\* Windows 7 or older will never be supported due to the way themes are implemented.
@@ -88,25 +88,31 @@ A: [Help: Step by step installing SecureUxTheme and a custom theme](https://gith
88
88
89
89
### **Q: I have 1909 or later, and the Address bar / Search bar is weird when clicked**
90
90
91
-
A: See [Issue #6](https://github.com/namazso/SecureUxTheme/issues/6)
91
+
A: Consider using OldNewExplorer which fixes this. Alternatively, see [Issue #6](https://github.com/namazso/SecureUxTheme/issues/6).
92
92
93
93
---
94
94
95
95
### **Q: Can you make themes per-program?**
96
96
97
-
A: Unfortunately, this is [close to impossible](https://github.com/namazso/SecureUxTheme/issues/9#issuecomment-611897882)
97
+
A: Unfortunately, this is [close to impossible](https://github.com/namazso/SecureUxTheme/issues/9#issuecomment-611897882). However for Office programs, there is a [plugin](https://github.com/matafokka/ExcelDarkThemeFix) for fixing this.
98
98
99
99
---
100
100
101
101
### **Q:**`SelectTheme: pTheme->GetVisualStyle failed with 80070002`
102
102
103
103
A: You probably installed a theme by opening / double clicking. Custom themes cannot be installed like that, they must be moved to `%WINDIR%\Resources\Themes` with all their accompanying files.
104
104
105
+
## Is it SecureUxTheme or ThemeTool? And what does it stand for anyways?
106
+
107
+
Naming has been pretty messy in this project, I admit that. Originally this project was for myself, and consisted of only the hooking dll, and required hex-editing the invalid signature to the themes. The project was named SecureUxTheme. In hindsight, this was a pretty bad naming. While it contains "secure" in the name, it is rather "safe" instead of "secure". The UxTheme part comes from the dll name (`uxtheme.dll`) which needed to be patched on XP when visual styles were introduced. This dll is no longer containing the signature verification code since Windows Vista, however the name stuck, and all software similar to this are called uxtheme-patchers. Anyways, after deciding to release, I added a new component named "ThemeInvalidSigner" for adding the invalid signature to themes, and also an NSIS installer so that you don't have to run .reg files. This was the initial release. Later I grew tired of various problems and issue reports with the built-in Personalization I was using for letting users set themes, and this is when ThemeTool was born. It originally was a proof-of-concept app for setting themes via the IThemeManager2 COM interface I reverse-engineered, however it soon got the capability of patching themes, and eventually replaced the installer too. This also improved on the virus detections, for unknown reasons.
108
+
109
+
**TL;DR**: SecureUxTheme is the project and the hook dll, ThemeTool is the installer / UI component.
110
+
105
111
## Building
106
112
107
113
### Requirements
108
114
109
-
* Visual Studio 2019
115
+
* Visual Studio 2019 with x86, x64, ARM64 toolchains
0 commit comments