|
|
Post by anixx on Mar 10, 2024 5:44:43 GMT -8
This is the case for some mods. For example, I manage with this mod I am able to obtain the console with a classic theme frame before starting the session. You know, all theme data is stored in the area located in the current session of a user. The mod cannot close the theme section handle before the session starts, because it does not exist yet, the theme is not yet loaded!
The system session 0 has no theme section.
|
|
|
|
Post by nonameneeded on Mar 10, 2024 6:27:45 GMT -8
A couple of days have passed now. I didn't have any dwm crashes since the 3rd of March so it's quite likely that the problem is somehow related to the handle mod. The handle mod is an automatic (AI) translation of ClassicThemeTray from C# to C++. I believe you. However, there has to be some kind of difference that causes the issues.
|
|
|
|
Post by OrthodoxWin32 on Mar 10, 2024 7:02:16 GMT -8
You know, all theme data is stored in the area located in the current session of a user. The mod cannot close the theme section handle before the session starts, because it does not exist yet, the theme is not yet loaded!
The system session 0 has no theme section.
I agree, I exploit this behavior myself with scheduled tasks. This means that the DWM crashes on the handle mod are linked to something else. I don't really see what this could be linked to... I would have to test that.
I think aubymori 's mod (to disable the theme in console) works before login because it doesn't use the theme handle.
|
|
|
|
Post by anixx on Mar 10, 2024 7:55:26 GMT -8
I think aubymori 's mod (to disable the theme in console) works before login because it doesn't use the theme handle.
As I said, before login screen there is nothing to untheme because the themes are not loaded yet. The memory area is located in the session memory area as you can see on the screenshot above. Before the login screen there is no session and no Themesection. |
|
|
|
Post by OrthodoxWin32 on Mar 10, 2024 8:00:26 GMT -8
As I said, before login there is nothing to untheme because the themes are not loaded yet. The memory area is located in the session memory area as you can see on the screenshot above. Before the login there is no session and no Themesection. However, by default, the console login screen appears themed. |
|
|
|
Post by anixx on Mar 10, 2024 8:16:51 GMT -8
As I said, before login there is nothing to untheme because the themes are not loaded yet. The memory area is located in the session memory area as you can see on the screenshot above. Before the login there is no session and no Themesection. However, by default, the console login screen appears themed. Possibly, it runs in non-zero session. |
|
aubymori
Sophomore Member
👅👅👅👅👅
Posts: 160 
OS: Windows 10 IoT Enterprise LTSC 2021
Theme: Windows 10 Default
CPU: Intel Core i5-9300H
RAM: 8GB
GPU: Intel UHD Graphics 630 / NVIDIA GeForce GTX 1650
|
Post by aubymori on Mar 10, 2024 13:38:03 GMT -8
You know, all theme data is stored in the area located in the current session of a user. The mod cannot close the theme section handle before the session starts, because it does not exist yet, the theme is not yet loaded!
The system session 0 has no theme section.
I agree, I exploit this behavior myself with scheduled tasks. This means that the DWM crashes on the handle mod are linked to something else. I don't really see what this could be linked to... I would have to test that.
I think aubymori 's mod (to disable the theme in console) works before login because it doesn't use the theme handle.
That mod doesn't touch theme section at all. It simply uses a hack to disable uxtheme for just conhost. |
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Mar 12, 2024 0:17:29 GMT -8
A couple of days have passed now. I didn't have any dwm crashes since the 3rd of March so it's quite likely that the problem is somehow related to the handle mod. Checked the Event Viewer for the last couple of weeks. anixx's mod on. No DWM crashes of any sort recorded since February 20th. I don't think it's that conclusive at all. |
|
|
|
Post by anixx on Mar 15, 2024 2:40:51 GMT -8
I agree, I exploit this behavior myself with scheduled tasks. This means that the DWM crashes on the handle mod are linked to something else. I don't really see what this could be linked to... I would have to test that.
I think aubymori 's mod (to disable the theme in console) works before login because it doesn't use the theme handle.
That mod doesn't touch theme section at all. It simply uses a hack to disable uxtheme for just conhost. Please, please, make a step forward and submit your mod (Classic theme per process) to the Windhawk repo. |
|
clara
Sophomore Member
Posts: 118
|
Post by clara on Mar 15, 2024 3:35:02 GMT -8
That mod doesn't touch theme section at all. It simply uses a hack to disable uxtheme for just conhost. Please, please, make a step forward and submit your mod (Classic theme per process) to the Windhawk repo. wasn't it ephemeralViolette's mod? |
|
|
|
Post by anixx on Mar 15, 2024 4:08:57 GMT -8
Please, please, make a step forward and submit your mod (Classic theme per process) to the Windhawk repo. wasn't it ephemeralViolette's mod? Oh, maybe I confused it. Anyway, would be glad to see it in repo. |
|
|
|
Post by nonameneeded on Nov 10, 2024 17:51:36 GMT -8
I still wonder if there is a way to prevent the DWM crap from logging the user off when this piece of shit of DWM crashes too often...
|
|
