aubymori
Sophomore Member
👅👅👅👅👅
Posts: 150 
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 Jul 13, 2024 19:00:47 GMT -8
As Windhawk is unreliable with hooking conhost.exe, I modified the source code for it (which is available in the Microsoft Terminal source code as OpenConsole) to have client edge and classic theme (optional).
To make it use classic theme, follow the instructions provided in the repository's README.
|
|
|
|
Post by anixx on Jul 13, 2024 19:57:48 GMT -8
I thought, the Classic Conhost mod is reliable.
|
|
|
|
Post by ephemeralViolette on Jul 13, 2024 20:30:32 GMT -8
I thought, the Classic Conhost mod is reliable. No. It's a decent solution, but Windhawk inherently has troubles injecting into conhost, because it manages early injections by hooking process creation from the spawning process. Because conhost is most often opened by privileged code, Windhawk cannot intercept the process creation, and so mods inject asynchronously. This is almost always after any windows are already created. |
|
|
|
Post by diegomaster on Jul 14, 2024 1:47:26 GMT -8
can a option to use SetThemeAppProperties(0) instead of SetThemeAppProperties(STAP_ALLOW_NONCLIENT)be added? it work better on some setups
Attachments:
|
|
AnyKey
Sophomore Member
Posts: 243
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 Jul 17, 2024 0:03:09 GMT -8
So many crash dumps were made but is this expected?
|
|
aubymori
Sophomore Member
👅👅👅👅👅
Posts: 150
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 Jul 20, 2024 8:14:20 GMT -8
can a option to use SetThemeAppProperties(0) instead of SetThemeAppProperties(STAP_ALLOW_NONCLIENT)be added? it work better on some setups
If you're already running classic theme on your whole system, you're fine just setting ClassicTheme to 0. |
|
|
|
Post by cetav13115 on Jul 30, 2024 10:12:55 GMT -8
As Windhawk is unreliable with hooking conhost.exe, I modified the source code for it (which is available in the Microsoft Terminal source code as OpenConsole) to have client edge and classic theme (optional).
To make it use classic theme, follow the instructions provided in the repository's README.
Not sure if it's a Windows build issue since I'm running an up-to-date build of datacenter 1607 and the terminal repo states "Windows Terminal requires Windows 10 2004 (build 19041) or later"  Any icu.dll I tried so far either gave me a "The application was unable to start correctly (0xc000007b)" or "The procedure entry point SetThreadDescription could not be located in the dynamic link library" |
|
|
|
Post by ephemeralViolette on Jul 31, 2024 20:20:40 GMT -8
As Windhawk is unreliable with hooking conhost.exe, I modified the source code for it (which is available in the Microsoft Terminal source code as OpenConsole) to have client edge and classic theme (optional).
To make it use classic theme, follow the instructions provided in the repository's README.
Not sure if it's a Windows build issue since I'm running an up-to-date build of datacenter 1607 and the terminal repo states "Windows Terminal requires Windows 10 2004 (build 19041) or later" View AttachmentAny icu.dll I tried so far either gave me a "The application was unable to start correctly (0xc000007b)" or "The procedure entry point SetThreadDescription could not be located in the dynamic link library" I would just chalk this up to 1607 being too old for this conhost build to run on. |
|
