|
|
Post by anixx on Sept 27, 2016 4:17:11 GMT -8
Some people prefer having DWM off. There are programs to this effect. This is a dummy DWM one can use instead of the system one: www.mediafire.com/download/llvplxlrtlu917x/NODWM8.1.7zThis is an utility that replaces DWM: www.mediafire.com/file/52aets4mzz3aqu3/stop+DWM+temp.7zAlternatively, the file rundll32.exe can be used in place of dwm.exe. Make sure you enabled auto-login before disabling DWM because the logon screen will not work without DWM running. On Windows 10, the UAC promt requires DWM, so one has to install a replacement utility, such as SuRun: sourceforge.net/projects/surun/After disabling DWM, to get to the Classic theme, rename the Windows\Resources folder. Besides this, it is recommended to disable the Charms bar because it causes problems when no DWM is running. To do so, rename or delete these two files from System32 folder: Windows.Shell.Search.UriHandler.dll
Windows.UI.Search.dllThe above instruction is tested on Windows 8.1 |
|
|
|
Post by R.O.B. on Oct 11, 2016 11:15:19 GMT -8
|
|
|
|
Post by 6sicsix on Feb 14, 2017 13:11:58 GMT -8
I just use rundll32.exe as a dummy exe
|
|
|
|
Post by anixx on Feb 16, 2017 15:02:32 GMT -8
I just use rundll32.exe as a dummy exe The guys say that renaming the theme is enough. |
|
|
|
Post by 6sicsix on Mar 1, 2017 2:49:56 GMT -8
If you only rename the theme (I actually rename C:\Windows\Resources\ to C:\Windows\Resources.old\) dwm keeps restarting instaed of terminating and you don't get past the logon screen at the next boot (Win 8.1 Pro x64) I have made a script btw youtu.be/nnFZmULsko0 |
|
|
|
Post by anixx on Mar 1, 2017 5:51:22 GMT -8
|
|
|
|
Post by 6sicsix on Mar 1, 2017 11:23:23 GMT -8
Hmm.. If they can't get the autologin to work after renaming the theme, how do they know it works  The problem is that the login screen keeps reloading when dwm restarts instead of terminates. |
|
|
|
Post by Splitwirez on Mar 1, 2017 18:11:18 GMT -8
Hmm.. If they can't get the autologin to work after renaming the theme, how do they know it works I don't. In fact, I know it doesn't. What I said I know is that you don't need to manually disable DWM in order to enable the classic theme via removal of visual styles, as removing all available visual styles prevents DWM from starting, eliminating the need to alter DWM itself. The problem is that the login screen keeps reloading when dwm restarts instead of terminates. Yeah, not much we can do about that .__________. |
|
|
|
Post by 6sicsix on Mar 3, 2017 1:27:26 GMT -8
? Yes, but when you only remove the visual styles you can't get past the logon screen. So even though dwm teschnically isn't running (or is constantly restarting), don't you kind of need to replace dwm so you can use windows? Or am I missing something lol?  - Biggesst ramaining issues I have: deskn.cpl/rundll32.exe freezes on apply 64 bit windows (on some installs, I can't figure out the cause) window theme is reset if you press ctrl-alt-del (resets back to aero grey/blue/white) invisible fullscreen windows notifications (battery low etc) logon screen / ctrl-alt-del screen (I know I saw a console mode logon screen on a win8 / win2012 beta, still searching for it) network pane |
|
|
|
Post by Splitwirez on Mar 3, 2017 10:24:02 GMT -8
? Yes, but when you only remove the visual styles you can't get past the logon screen. So even though dwm teschnically isn't running (or is constantly restarting), don't you kind of need to replace dwm so you can use windows? Or am I missing something lol? Replacing DWM doesn't fix the login screen .____. (I know I saw a console mode logon screen on a win8 / win2012 beta, still searching for it) WAT O.O |
|
|
|
Post by anixx on Mar 3, 2017 14:24:13 GMT -8
|
|
|
|
Post by Splitwirez on Mar 4, 2017 14:43:16 GMT -8
...this thing is made by the same person as that crappy Windows 10 ViStart skin. You're sure it's the original DP executable and not a port? .-.
|
|
|
|
Post by anixx on Mar 4, 2017 16:42:12 GMT -8
...this thing is made by the same person as that crappy Windows 10 ViStart skin. You're sure it's the original DP executable and not a port? .-. One can try oneself if it works to substitute this executeble. |
|
|
|
Post by anixx on Mar 7, 2017 14:27:28 GMT -8
? Yes, but when you only remove the visual styles you can't get past the logon screen. So even though dwm teschnically isn't running (or is constantly restarting), don't you kind of need to replace dwm so you can use windows? It seems to me that Splitwirez is renaming the theme file while you are renaming the whole folder. That may be the reason he can login even after renaming. |
|
|
|
Post by 6sicsix on Mar 8, 2017 23:43:13 GMT -8
? Yes, but when you only remove the visual styles you can't get past the logon screen. So even though dwm teschnically isn't running (or is constantly restarting), don't you kind of need to replace dwm so you can use windows? It seems to me that Splitwirez is renaming the theme file while you are renaming the whole folder. That may be the reason he can login even after renaming. But I thought they said autologon doesn't work if he doesn't replace the dwm file? And I know it doesn't fix the login screen lol, but I can't logon without it. So that's why I'm still searching for the console version of logonui (sure it was a registry edit on the windows 8 consumer preview) |
|
|
|
Post by 6sicsix on Mar 11, 2017 6:34:59 GMT -8
So I want to clarify, you just rename the aero.msstyles and Aero Lite.mssyles and reboot? And that's it? Is this on windows 8 or windows 10?
My results are:
Win 8.1:
rename .msstyles files and keep dwm - login screen black and does not autologon because dwm.exe keeps crashing
rename .msstyles files and delete dwm - login screen black and does not autologon because logonui keeps crashing
rename .msstyles files and replace dwm with rundll32.exe - login screen black but autologon works
Win 10:
rename .msstyles files and keep dwm then reboot - login screen does not work at all (even consolemode) - windows boots into recovery mode after three reboots
rename .msstyles files and delete dwm then reboot - login screen does not work at all (even consolemode) - windows boots into recovery mode after three reboots
rename .msstyles files and replace dwm with rundll32.exe then reboot - login screen does not work at all (even consolemode) - windows boots into recovery mode after three reboots
!!! WORKING !!!
Win 10:
rename .msstyles files and replace dwm with rundll32.exe, enable console mode, enable legacy UAC prompt, logoff and on, then reboot
login screen works in consolemode, autologon not needed - no transparent windows
|
|
|
|
Post by Spitfire_x86 on Mar 11, 2017 11:17:27 GMT -8
|
|
|
|
Post by Aesthetic Classic on Mar 11, 2017 20:35:28 GMT -8
I'm going to have to update that whenever I can since Windows Defender thinks that DWM dummy file is some sort of malware and it removes it which is a pain if it happens to remove the placeholder file that is in place for the actual DWM (leaves you with a black screen if no dwm.exe file is present upon log out, even with the dummy exe I generated is later on detected as some form of malware). For now, you can copy the rundll32.exe as mentioned previously above which I didn't even think of before and name it dwm_placeholder.exe. Will have to get the script to copy rundll32 instead of requiring some dodgy converted batch file to exe used as a placeholder.
Edit: The scripts now make a copy of rundll32.exe straight from the System32 directory to use as a placeholder rather than using those converted batch files as a placeholder which can sometimes be detected as a malware by some software (which ends up breaking if you are logged out or reboot when no placeholder file is in place because it got removed). Thanks 6sicsix for pointing out that the rundll32 file can be used instead! Also, there's some Registry tweaks in there that I added from before to switch off some Immersive features so they work without DWM just to make it less of a pain to search for those Registry tweaks. Edit 2: Another thing to note that is this does not break the taskbar as you can login with theming enabled before running the ClassicTheme utility. However, you may get a blank Explorer window upon resuming login where killing the Explorer process seems to be the only way to remove it. You'd have to use the ObjDir permissions method if you want to restart Explorer without breaking the taskbar without having to log out and log back in. |
|
|
|
Post by 6sicsix on Jul 4, 2017 23:52:05 GMT -8
Renaming the .msstylea and replacing dwm.exe with rundll32.exe no longer seems to work on the creators update.
I cannot proceed further than the login screen without dwm.exe running.
I have not yet tried the console mode logon but I am not hopeful.
|
|
Fang
New Member
Posts: 1
OS: Arch Linux & LTSC 2021
Theme: Vista
|
Post by Fang on Feb 5, 2022 22:37:21 GMT -8
Sorry for the necro, but it's possible to use this method (sorta) of replacing dwm.exe with a dummy through a registry tweak. Basically it's like you replaced dwm.exe while leaving the files themselves intact, it's a redirect of sorts (no idea what is actually going on honestly) Can't remember where I found this.
I don't suggest doing this on versions of Windows 10 after 1607 as unfortunately too many things start breaking to allow a usable system.
Login screen breaks unless you rename Windows.UI.Logon.dll (in system32) to something like Windows.UI.Logon.dll- (though I have yet to test the registry thing on it, but not sure if it works for non executables)
I can't remember how to solve the login screen breaking on 8.1
I also normally rename the ShellExperiences and SystemApps folders inside the Windows folder as I find things normally break and crash pretty quickly if I don't, this is also usually done on the LTSB branch of 1607 as it comes with minimal UWP apps. Lots of the time renaming those folders gives errors so you'll have to take ownership through the security tab, I've tried scripting it but it's never been as reliable as manually doing it and one or two processes may also need to be killed if you get folder is in use or whatever errors
Also half of the reason for renaming those folders is it'll also help prevent misclicking some UI elements that will break things if dwm is disabled, I also always apply the old clock/uac/alt-tab/volume/etc tweaks, old context menu is another good one.
Open with menu breaks but there's some weird mod for it I found but it sorta advertises other programs
I think I outlined everything to make this not break instantly but I can't remember and there's someone talking in my headset this entire post so focus is hard
Oh and lastly renaming the two folders inside the Resources folder in the Windows folder will force the classic theme.
If you turn dwm back on you HAVE to put the folders in resources back to their original names otherwise it bricks
It doesn't prevent bricking or anything so still be wary of that (I've done it a lot)
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\dwm.exe]
@="\"C:\\Windows\\System32\\rundll32.exe\""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dwm.exe]
"Debugger"="\"C:\\Windows\\System32\\rundll32.exe\""
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dwm.exe]
"Debugger"="\"C:\\Windows\\System32\\rundll32.exe\""
Sorry for how terribly organized this post is and if this is already well known info
|
|
