crumble266
Freshman Member
Posts: 26
OS: Win10 LTSC 2021 (21H2)
CPU: i7-4790
RAM: 32GB
GPU: GTX 1060
|
Post by crumble266 on Jan 17, 2024 6:35:19 GMT -8
@clara i tried the "Eradicate Immersive Menus" mod instead of "Disable Immersive Context Menus". It worked ! thanks. anixx Indeed, i opened EP config, and the settings were not ticked. i tried to relaunch the .reg several time (and checked in regedit) but EP ignore them. So i have to tick the options manually. (I also tried to desinstall / reinstall) Maybe latest versions of EP store the settings elsewere ? It is starting to look pretty good except i have to restart explorer after bootup for the classic theme to be correctly applied. Is this possible that Windhawk launch too late (after explorer.exe) or something like that ?
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Jan 17, 2024 10:05:58 GMT -8
It is starting to look pretty good except i have to restart explorer after bootup for the classic theme to be correctly applied. Is this possible that Windhawk launch too late (after explorer.exe) or something like that ?
I actually decided to finally switch to windhawk method a couple of days ago, and this was indeed the case for me. However! Interesting thing regarding windhawk behavior, i had to allow windhawk to inject into critical system processes for the latest version of aeroexplorer and dwm ghost windows mod to work properly and now for me resetting explorer is not required, it starts up unthemed pretty cleanly. Not sure if allowing windhawk to do this is beneficial for the mod or is it just a fluke of my personal setup (im on 10 pro 22H2) but its worth looking into. If this is universal behavior, then windhawk is the cleanest method for enabling classic theme so far.
Be prepared for unexpected behavior though, when i was using SCT allowing windhawk to do this would lead to a login loop on reset, but i think it was just some incompatibility between the two. Trying this is safe, just be prepared to reboot in safe mode if something like this happens. Seems to be fine with windhawk script as theme disabler but i feel like some caution is needed just in case.
|
|
|
Post by anixx on Jan 17, 2024 11:03:50 GMT -8
Windhawk method does not untheme all windows, for instance, console window, quotes dialog, network properties... ClassicThemeTray works for all. It would be great if we could do the same but with Windhawk for easier setup.
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Jan 17, 2024 11:29:11 GMT -8
Windhawk method does not untheme all windows, for instance, console window, quotes dialog, network properties... ClassicThemeTray works for all. It would be great if we could do the same but with Windhawk for easier setup. Now that's peculiar, because i have network properties unthemed. Not sure why, most peculiar indeed.
So far i only have experienced theming issues with Premiere Pro and "program not responding" dialog when i was testing ghost windows, so its not like its flawless.
|
|
|
Post by anixx on Jan 17, 2024 11:31:33 GMT -8
Oh, maybe I was wrong about network properties, but what about the disk quotes ddialog and command prompt window (and its properties dialog)?
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Jan 17, 2024 12:04:40 GMT -8
Oh, maybe I was wrong about network properties, but what about the disk quotes ddialog and command prompt window (and its properties dialog)? Command prompt indeed remains themed without ClassicConhost mod, and its properties window remains partially themed:
Regarding theming of windows behind the UAC prompt, i actually just re-enabled it for testing and somehow it works. Quota dialog is unthemed.
I don't think you were wrong about Network properties or any other issues, i think it's undocumented mod behavior with more permissions. The fact that theming isn't 100% clean leaves room for improvement, but i think this is something worth testing by more people, if this is indeed a thing and not a one-off fluke in my case, we can at least do away with explorer resets and have a way more clean startup.
|
|
crumble266
Freshman Member
Posts: 26
OS: Win10 LTSC 2021 (21H2)
CPU: i7-4790
RAM: 32GB
GPU: GTX 1060
|
Post by crumble266 on Jan 17, 2024 12:12:30 GMT -8
However! Interesting thing regarding windhawk behavior, i had to allow windhawk to inject into critical system processes for the latest version of aeroexplorer and dwm ghost windows mod to work properly and now for me resetting explorer is not required, it starts up unthemed pretty cleanly. Not sure if allowing windhawk to do this is beneficial for the mod or is it just a fluke of my personal setup (im on 10 pro 22H2) but its worth looking into. If this is universal behavior, then windhawk is the cleanest method for enabling classic theme so far.
I went into Windhawk advanced settings and removed the default string <critical_system_processes> in "Process exclusion list" It seems to fix the issue ! Maybe it should be signaled on the 1st page ?
Everything seems fine now. I will do further testing and investigate the EP .reg importing issue.
I did not checked SysListView32 because i am ok with the win7 look. I will still need to get rid of the explorer w10 status bar (the other one is from open shell), try to customize some icons (mixture of Win7 and XP, i like the XP drive icons) and try to put back the colored "up" icon (i think that it was added by openshell explorer).
To nitpick there is some kind of double vertical bar effet between the tree pane and folder.
|
|
|
Post by anixx on Jan 17, 2024 12:33:14 GMT -8
Oh, maybe I was wrong about network properties, but what about the disk quotes ddialog and command prompt window (and its properties dialog)? Command prompt indeed remains themed without ClassicConhost mod, and its properties window remains partially themed:
You have some other mod running that unthemes windows content (but not the border).
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Jan 17, 2024 12:37:56 GMT -8
Command prompt indeed remains themed without ClassicConhost mod, and its properties window remains partially themed:
You have some other mod running that unthemes windows content (but not the border). Yes, it seems like it's Travis's mod. Glad that it worked for you! Getting rid of Win10 status bar is simple, you can just disable it in Folder options.
|
|
crumble266
Freshman Member
Posts: 26
OS: Win10 LTSC 2021 (21H2)
CPU: i7-4790
RAM: 32GB
GPU: GTX 1060
|
Post by crumble266 on Jan 17, 2024 15:32:42 GMT -8
My ExplorerPatcher seems to keep settings in HKEY_CURRENT_USER\SOFTWARE\ExplorerPatcher The ones imported in [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ExplorerPatcher] are ignored
|
|
|
Post by anixx on Jan 17, 2024 15:40:27 GMT -8
|
|
|
Post by anixx on Jan 17, 2024 15:46:05 GMT -8
My ExplorerPatcher seems to keep settings in HKEY_CURRENT_USER\SOFTWARE\ExplorerPatcher The ones imported in [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ExplorerPatcher] are ignored
Thanks, fixed this
|
|
crumble266
Freshman Member
Posts: 26
OS: Win10 LTSC 2021 (21H2)
CPU: i7-4790
RAM: 32GB
GPU: GTX 1060
|
Post by crumble266 on Jan 17, 2024 16:14:09 GMT -8
i reseted the Process exclusion list back to <critical_system_processes> and entered only "winlogon.exe" in the inclusion list and it works.
(Despite the "Only if targeted explicitly" option i still had to set it in the inclusion list)
|
|
|
Post by anixx on Jan 17, 2024 16:53:36 GMT -8
i reseted the Process exclusion list back to <critical_system_processes> and entered only "winlogon.exe" in the inclusion list and it works.
(Despite the "Only if targeted explicitly" option i still had to set it in the inclusion list)
A major problem with this: the UWP apps do not work. Also, for some reason, injecting any other process than Winlogon does not work.
|
|
crumble266
Freshman Member
Posts: 26
OS: Win10 LTSC 2021 (21H2)
CPU: i7-4790
RAM: 32GB
GPU: GTX 1060
|
Post by crumble266 on Jan 19, 2024 5:22:57 GMT -8
I think the 1st page guide should maybe also mention these fixes :
|
|
|
Post by spaghettiaero on Feb 16, 2024 14:07:10 GMT -8
so...i'm not an expert and should have known not to mess up with my pc like that, but i need to fix quite some things, like glitched buttons, a micro-sized taskbar and the colors changing to pee yellow and green, even if i imported that registry file. help me please...i'll be happy to explain further once i get a reply. thank you in advance.
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Feb 16, 2024 14:41:10 GMT -8
so...i'm not an expert and should have known not to mess up with my pc like that, but i need to fix quite some things, like glitched buttons, a micro-sized taskbar and the colors changing to pee yellow and green, even if i imported that registry file. help me please...i'll be happy to explain further once i get a reply. thank you in advance. Would be really nice if you could provide screenshots of the issues you are having, so it would be easier to suggest possible fixes.
Also, to start with, what method for classic theme are you using, CTT or windhawk, and if so, than which mod?
|
|
|
Post by spaghettiaero on Feb 17, 2024 9:59:41 GMT -8
so...i'm not an expert and should have known not to mess up with my pc like that, but i need to fix quite some things, like glitched buttons, a micro-sized taskbar and the colors changing to pee yellow and green, even if i imported that registry file. help me please...i'll be happy to explain further once i get a reply. thank you in advance. Would be really nice if you could provide screenshots of the issues you are having, so it would be easier to suggest possible fixes. Also, to start with, what method for classic theme are you using, CTT or windhawk, and if so, than which mod?
Alright, so I used every windhawk mod mentioned, and something changed when i restarted my laptop, but there are still problems as you can see in the pictures. hope this is enough info...
|
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Feb 17, 2024 13:19:37 GMT -8
No pictures seem to be in your post, unfortunately.
|
|
|
Post by spaghettiaero on Feb 18, 2024 1:24:30 GMT -8
No pictures seem to be in your post, unfortunately. oops, i'm new to this forum so i didn't know properly how to put them here. they must be there now.
|
|