|
|
Post by OrthodoxWin32 on Mar 18, 2023 7:01:12 GMT -8
There may be a problem with the classic2 task, which causes userinit.exe to start (if userinit.exe does not start, you get a black screen). Maybe providing screenshots of classic2 task properties can help. What is the code of the last execution of the classic2 task ? Then Classic theme still would be on and Classic task would hot hang. I seem to have had a "false CTT execution" coupled with a userinit.exe startup failure. This was when I was experimenting with adding multi-user support to classic theme scheduled tasks. But I understand what you mean. |
|
|
|
Post by anixx on Mar 18, 2023 7:18:52 GMT -8
Then Classic theme still would be on and Classic task would hot hang. I seem to have had a "false CTT execution" coupled with a userinit.exe startup failure. This was when I was experimenting with adding multi-user support to classic theme scheduled tasks. But I understand what you mean. userinit.exe possibly does not start because the Classic task not finishes. In Classic task all commands finish instantly regardless of result, except the one which runs classicthemetray. It waits for classicthemetray to finish so that userinit started when classic theme is already enabled.
Since classicthemetray does not appear in the process list, this may indicate that the .net engine is waiting for it to compile.
|
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 18, 2023 9:24:20 GMT -8
ClassicThemeTray uses .NET framework and is built for "any architecture". This means, it should be compiled from .NET pseudcode to native architecture on the target system. Sometimes after .NET framework update it takes some time when .NET software on your computer gets re-compiled in the background. If you have a lot of .NET software, your .NET compiler may be overloaded for some time after the update. This is virtual machine and it is clean installation. There may be a problem with the classic2 task, which causes userinit.exe to start (if userinit.exe does not start, you get a black screen). Maybe providing screenshots of classic2 task properties can help. What is the code of the last execution of the classic2 task ?  |
|
|
|
Post by OrthodoxWin32 on Mar 18, 2023 11:03:01 GMT -8
Since classicthemetray does not appear in the process list, this may indicate that the .net engine is waiting for it to compile.
One way to test this might be to simply run classicthemetray by clicking on the icon, and see if it works. The classic2 task doesn't seem to have any problems. |
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 18, 2023 23:10:02 GMT -8
Since classicthemetray does not appear in the process list, this may indicate that the .net engine is waiting for it to compile.
One way to test this might be to simply run classicthemetray by clicking on the icon, and see if it works. The classic2 task doesn't seem to have any problems. It is working.
|
|
|
|
Post by anixx on Mar 19, 2023 2:07:01 GMT -8
So, when you start it via task scheduler manually, it does not start?
|
|
|
|
Post by anixx on Mar 19, 2023 2:10:37 GMT -8
What's with the Apps task?
|
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 19, 2023 3:49:25 GMT -8
So, when you start it via task scheduler manually, it does not start? When I ran Classic from task scheduler, some console windows was shown and closed immediately. And explorer window was shown. Then classic theme was applied after I relaunch the explorer.
What's with the Apps task?  |
|
|
|
Post by anixx on Mar 19, 2023 5:43:10 GMT -8
So, when you start it via task scheduler manually, it does not start? When I ran Classic from task scheduler, some console windows was shown and closed immediately. And explorer window was shown. Then classic theme was applied after I relaunch the explorer.
So, all works now? |
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 19, 2023 9:35:36 GMT -8
When I ran Classic from task scheduler, some console windows was shown and closed immediately. And explorer window was shown. Then classic theme was applied after I relaunch the explorer.
So, all works now? Maybe. Though I need to do strange thing to enable classic theme, classic theme itself seems to work as intended. |
|
|
|
Post by anixx on Mar 28, 2023 11:44:34 GMT -8
The tutorial is updated with new WindHawk capabilities.
|
|
gombau
Freshman Member
Posts: 77
|
Post by gombau on May 2, 2023 8:23:15 GMT -8
Well, so for those who are on Windows 10 21H2 and experienced problems such as a black screen with a cursor, task scheduler not running the tasks properly, or just explorer still using the main theme while other windows use the classic theme, I've finally found a solution after months and months of trying to fix it. I remember when I applied anixx's solution months ago and just showed a cursor on a black screen. The black screen problem seems to be related to the tasks not running on a specific user. I fixed this by checking "Run only when user is logged on" in "General" and in "Triggers" setting as trigger "At log on" and your user as a "specific user". You must do this to make the tasks run properly on your user account. Regarding explorer not using the classic theme while other programs do, seems to be related to the "classic2" task not running with the highest privileges. Explorer finally started up using the classic theme once I checked that. You must make sure both "Classic" and "Classic2" tasks run with the highest privileges so they run before explorer. You must make sure as well the Userinit registry key anixx stated is changed to what he wrote. So I started with a fresh Win 10 VM I followed the steps precisely. I did the following: - I installed classic Task Manager
- I put ClassicThemeTray.exe into C:\Classic
- I created the three Scheduled Tasks, copy and pasting each action exactly, and set them to run at any power source
- I manually set the Userinit registry key
I then ran the "Classic" Task. This is what I got  winver and notepad look "classic-ish", explorer looks the same as always. Did I miss a step? I think yours is that the explorer starts before Classicthemetray. Normally, it should be the opposite. Have you configured the task (the one that contains the three commands) with the "Execute with maximum authorizations" option and the "Execute only if the user is connected" option ? Not only should the task that contains the three commands (the Classic one) be run with maximum authorizations, but the "Classic2" task should as well. You must also specify your user and at logging on as a trigger apart from checking run only when user is logged on. Go to File Explorer Options and enable "Launch folder windows in a separate process". This will make file explorer have the classic theme. You also need OldNewExplorer. The ribbon is slightly broken in classic theme. Also, to make the theme look even more classic you need the classic desk.cpl and some registry file which allows you to select the colour schemes from said desk.cpl. Edit: If you also want the taskbar to be classic as well, use something like retrobar and create a scheduled task (or just a script) that restarts explorer after the classic theme gets enabled. To have retrobar start on startup simply just paste its exe into "shell:common startup" (just type that in the explorer address bar). Thank you for suggesting Oldnewexplorer, I finally fixed the back and forward buttons of the navigation bar, which sometimes showed up and sometimes not. However, to make it work you need to check on Folder Options launch folder windows in separate processes, the opposite thing of what Explorerpatcher needs (Given that when I checked so on Explorerpatcher, explorer showed the Ribbon again). Well, on 22H2, it does nothing even I logged on. Stuck on black screen. Press Ctrl + Alt + Del to run Task Manager and run Explorer, then the desktop will be shown. However, it's not Classic Theme. I checked anixx's tutorial again (especially Task Scheduler and Userinit section) but I couldn't see the problems. It is appreciated if someone could try to reproduce this issue. Yep, just what happened to me before. You must do what I said above, you must run both "Classic" and "Classic2" tasks with highest privileges, set for all tasks as trigger "At log on" setting your user in settings (Within the edit window of the trigger section of Task Scheduler, in "specific user") and in the General section check for all tasks "Run only when user is logged on". |
|
|
|
Post by The Jackal on May 5, 2023 14:06:39 GMT -8
Has anyone been able to achieve this without using ExplorerPatcher? I tried using the "Classic Theme Explorer" Windhawk mod which incorporates the Classic Theme mitigations portion of the EG? I've tried but it causes the taskbar buttons to not render correctly ( namely they are shifted upwards and shrink). |
|
mauro
Freshman Member
Posts: 57 
|
Post by mauro on May 19, 2023 5:15:39 GMT -8
is possible fix explorer on windows 11 22h2 using classic theme? im disable ribbon but not fullwork
on windows 10 run perfect explorer with classic theme
and taskbar using explorer patcher is possible disable labels?
in windows 10 using explorer patcher is perfect with no label screen down, how to leave in windows 11 like this too?
|
|
|
|
Post by OrthodoxWin32 on May 19, 2023 6:14:35 GMT -8
is possible fix explorer on windows 11 22h2 using classic theme? im disable ribbon but not fullwork
on windows 10 run perfect explorer with classic theme
and taskbar using explorer patcher is possible disable labels?
in windows 10 using explorer patcher is perfect with no label screen down, how to leave in windows 11 like this too?
All this is possible with ExplorerPatcher, indeed. |
|
aldon
Freshman Member
Posts: 56
|
Post by aldon on May 28, 2023 13:11:52 GMT -8
Hello! So which settings in EP are to fix this:  |
|
|
|
Post by ihatemetro on May 28, 2023 20:08:49 GMT -8
Hello! So which settings in EP are to fix this: ExplorerPatcher Properties > File Explorer > Control Interface: Change to "Windows 7 Command Bar" |
|
aldon
Freshman Member
Posts: 56
|
Post by aldon on May 29, 2023 0:00:06 GMT -8
Hello! Thanks for answer... Unf. I have it as you suggest...  So it must be smthng else, related to 22H2 maybe... EP is the latest + File Explorer restarted again, to be sure...    |
|
|
|
Post by OrthodoxWin32 on May 29, 2023 2:35:08 GMT -8
Hello! Thanks for answer... Unf. I have it as you suggest... So it must be smthng else, related to 22H2 maybe... EP is the latest + File Explorer restarted again, to be sure... In the " control interface" section select: Windows 10 Ribbon. After the ribbon enabled, use this tool : winaero.com/ribbon-disabler-for-windows-10-and-windows-8/After the ribbon disable, restart the computer to apply the changes. |
|
|
|
Post by The Jackal on May 29, 2023 13:29:40 GMT -8
I get the same thing with Chrome when I open an incognito window, which leads me to believe this new Explorer Command Bar is coded in webforms? |
|
So it must be smthng else, related to 22H2 maybe...