|
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: 117
OS: Windows 11 Pro 21H2
Theme: Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB
GPU: RTX 2070 S
Member is Online
|
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.
AnyKey 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: 117
OS: Windows 11 Pro 21H2
Theme: Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB
GPU: RTX 2070 S
Member is Online
|
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.
AnyKey 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: 117
OS: Windows 11 Pro 21H2
Theme: Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB
GPU: RTX 2070 S
Member is Online
|
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: 117
OS: Windows 11 Pro 21H2
Theme: Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB
GPU: RTX 2070 S
Member is Online
|
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.
|
|