|
|
Post by OrthodoxWin32 on Jan 30, 2024 8:37:29 GMT -8
As a result, the ApplicationFrameHost problem is resolved. The remaining problem with this mod is that it applies to all user sessions. Overall, this mod is too "invasive" and the Cassic theme per process mod is not invasive enough.
|
|
|
|
Post by anixx on Jan 30, 2024 8:49:53 GMT -8
As a result, the ApplicationFrameHost problem is resolved. The remaining problem with this mod is that it applies to all user sessions. Overall, this mod is too "invasive" and the Cassic theme per process mod is not invasive enough. Changing the permissions string you can include and exclude user groups. |
|
|
|
Post by OrthodoxWin32 on Jan 30, 2024 8:51:28 GMT -8
Changing the permissions string you can include and exclude user groups. Thanks I will try. |
|
clara
Sophomore Member
Posts: 118 
|
Post by clara on Jan 30, 2024 9:11:50 GMT -8
The remaining problem with this mod is that it applies to all user sessions. To me its a feature, not a bug, to be honest, considering that multi-user version of SCT never left beta, I was waiting for something like that.
The fact that permissions can be adjusted is a nice option too.
|
|
|
|
Post by OrthodoxWin32 on Jan 30, 2024 10:43:16 GMT -8
To me its a feature, not a bug, to be honest, considering that multi-user version of SCT never left beta, I was waiting for something like that.
The fact that permissions can be adjusted is a nice option too.
Otherwise, I can also use CTT (ClassicThemeTray) in multi-user mode. The only issue is that it doesn't work when multiple sessions are connected simultaneously. |
|
kirta
Freshman Member
Posts: 59
OS: Windows 10 LTSC 2021
|
Post by kirta on Jan 31, 2024 6:15:58 GMT -8
Was using this mod prior, yes, know that it exists, i was the one who figured out that this mod works better with critical files injection permission. Still doesn't apply classic theme to parts of the system, so, considering Ingan121 's mod exists now, the issue at hand is solved. yeah I was using it and it doesn't apply classic theme to "Network Connections" don't know why tho, am using classicthemetray for now. |
|
aldon
Freshman Member
Posts: 56
|
Post by aldon on Feb 10, 2024 6:52:11 GMT -8
Hello anixx (and clara)! How this new way ("This mod works just like the ClassicThemeTray.exe utility and fully replaces it.") replaces (or is related to) your earlier tutorial: winclassic.net/thread/990/windows-classic-theme-on-1903 ? Could you please write tutorial for proper using of Windhawk method? (Or windhawk + ExplorerPatcher? Dunno...) I am little lost now...  Thanks for your great support here! |
|
|
|
Post by anixx on Feb 10, 2024 7:31:55 GMT -8
Hello anixx (and clara)! How this new way ("This mod works just like the ClassicThemeTray.exe utility and fully replaces it.") replaces (or is related to) your earlier tutorial: winclassic.net/thread/990/windows-classic-theme-on-1903 ? Could you please write tutorial for proper using of Windhawk method? (Or windhawk + ExplorerPatcher? Dunno...) I am little lost now...  Thanks for your great support here! The tutorial has been updated already. |
|
aldon
Freshman Member
Posts: 56
|
Post by aldon on Feb 10, 2024 7:40:09 GMT -8
Ah yes! TYVM!
|
|
|
|
Post by nonameneeded on Feb 16, 2024 17:05:12 GMT -8
Doesn't work (the classic theme mod)...
Even with the changed setting to insert code somewhere it simply doesn't do anything.
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Feb 16, 2024 19:16:10 GMT -8
Doesn't work (the classic theme mod)... Even with the changed setting to insert code somewhere it simply doesn't do anything. Sorry to ask a stupid question, but have you restarted your PC after enabling it? |
|
|
|
Post by nonameneeded on Feb 16, 2024 20:11:22 GMT -8
No, I just logged off and back on. Is it necessary to restart your PC?
Edit:
I've just restarted the PC. Doesn't change anything. Still doesn't work.
|
|
|
|
Post by OrthodoxWin32 on Feb 17, 2024 3:54:32 GMT -8
No, I just logged off and back on. Is it necessary to restart your PC?
Edit:
I've just restarted the PC. Doesn't change anything. Still doesn't work. Are you sure that Windawks has permission to hook Winlogon.exe?
Check if it is not in the exclusion list.
|
|
|
|
Post by nonameneeded on Feb 17, 2024 6:42:58 GMT -8
No, there is nothing in the exclusion list.
|
|
|
|
Post by nonameneeded on Feb 17, 2024 16:47:25 GMT -8
Ok, I finally got it to work. It's important to remove <critical_system_processes> from the exclusion list. It is not necessary to change the setting for "Load mods in critical system processes". which is not the same. It doesn't even help (and that's what I did, which is why it didn't work).
Maybe it would be useful to mention that in the tutorial.
So I added this <critical_system_processes> exclusion to every single mod and I also had to alter the inclusion lists in order to ensure the mods still work (because when you use the lists, they will override the settings found in the code). So it's not really very practical but at least you don't need a registry setting and 2 (to 3) tasks in the task planner to use the classic theme, maybe that's an advantage.
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Feb 17, 2024 18:00:06 GMT -8
Ok, I finally got it to work. It's important to remove <critical_system_processes> from the exclusion list. It is not necessary to change the setting for "Load mods in critical system processes". which is not the same. It doesn't even help (and that's what I did, which is why it didn't work).
Maybe it would be useful to mention that in the tutorial.
So I added this <critical_system_processes> exclusion to every single mod and I also had to alter the inclusion lists in order to ensure the mods still work (because when you use the lists, they will override the settings found in the code). So it's not really very practical but at least you don't need a registry setting and 2 (to 3) tasks in the task planner to use the classic theme, maybe that's an advantage.
After you get it to work it boots instantaneously, doesn't require explorer restart to be applied and allows other intrusive mods like DWM ghost windows to work (it also requires critical system processes to be removed from exclusions, which caused massive comflicts with non-windhawk classic theme methods), so i think overall, if you really want classic theme, this is the slickest method.
To be fair, the fact that you said that exclusion list is empty, confused me a great deal, since i thought you removed the critical process exclusion already and it somehow did nothing, But i can see how it being a default may lead to such a miscommunication.
|
|
|
|
Post by nonameneeded on Feb 17, 2024 18:02:48 GMT -8
What are DWM ghost windows?
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Feb 17, 2024 18:11:24 GMT -8
What are DWM ghost windows? A mod by ephemeralViolette . Disabling theming on Windows still leaves frozen applications with metro theme borders, so when it happens it can break the UX of the classic theme, this mod fixes this inconsistency. However, removing <critical_system_processes> from exclusion list with SCT/CCT as a main method sends system in a graphics card glitch flavored login loop. With windhawk as a sole method that isn't an issue. Adding to this set UWP border mod that works with classic theme on Win10 (there are some issues on 11 because 11 sucks) makes the look as consistent as it can be.
I notice that i do sound like a sales person a lot when i speak of Windhawk but it just keeps amazing me, just a few month ago once again there were voices how disappointing and janky classic theme experience is and just a few months later community has overall reached "smooth as butter" territory (at least, regarding base necessities). Nothing to sneeze at.
|
|
|
|
Post by nonameneeded on Feb 17, 2024 18:17:41 GMT -8
Ah ok, I think I remember that.
Didn't really work that well, so I just didn't use it.
I use as few mods as possible.
And even the ones I use I restrict to certain processes only.
Because you just don't want loads of code injected into every process, even if it makes no sense.
Just causes problems.
|
|
|
|
Post by ephemeralViolette on Feb 17, 2024 21:46:09 GMT -8
What are DWM ghost windows? A mod by ephemeralViolette . Disabling theming on Windows still leaves frozen applications with metro theme borders, so when it happens it can break the UX of the classic theme, this mod fixes this inconsistency. However, removing <critical_system_processes> from exclusion list with SCT/CCT as a main method sends system in a graphics card glitch flavored login loop. With windhawk as a sole method that isn't an issue. Adding to this set UWP border mod that works with classic theme on Win10 (there are some issues on 11 because 11 sucks) makes the look as consistent as it can be.
I notice that i do sound like a sales person a lot when i speak of Windhawk but it just keeps amazing me, just a few month ago once again there were voices how disappointing and janky classic theme experience is and just a few months later community has overall reached "smooth as butter" territory (at least, regarding base necessities). Nothing to sneeze at.
In fact, it's just not possible to disable theming on DWM in any other way. DWM requires themes to be enabled to start, and keeps the handles as long as it's running. You'll also notice this if you start something like ClassicThemeTray and then force quit dwm.exe.
Since the ghost windows are owned by DWM, my mod is the only way to do it. I use a technique to force classic appearance while keeping the theme engine loaded. |
|
