|
|
Post by isaachacks on Dec 19, 2020 15:55:45 GMT -8
When I terminated winlogon.exe, before I went to the sign in screen, for a brief 10 seconds the classic theme was displayed and dwm was killed, without all those black windows like dwm killed normally. Why does this happen? Is there a way that this can be exploited for a better classic theme?
|
|
ihatemetro
Regular Member
I hate the forced UWP/Metro/Tablet UI in Windows 10, I wish they kept at least the Control Panel.
Posts: 358
OS: Windows 10 LTSB 2016 x64 edition, FreeBSD x86_64, BlissOS 11.13 x86_64, MacOS 10.15 & Arch Linux x86_64 | Bootloader: rEFInd
Theme: Windows: Windows 7 Theme on 250% HI-DPI Scaling (Aero Glass Win 8 RP borders) | Arch Linux: KDE Plasma with a ton of blur | rEFInd: A mix of rEFInd-theme-regular and rEFInd-glassy
CPU: Intel Core i7-8565U
RAM: 16GB 2666Mhz DDR4
GPU: Intel UHD 620 & NVIDIA MX150
|
Post by ihatemetro on Dec 20, 2020 7:10:34 GMT -8
Winlogon has a "themesection" handle. When you terminate Winlogon, themes don't work. We already use this method, except by closing the handle instead of terminating winlogon.
|
|
