|
|
Post by TechSalt on Sept 18, 2022 3:21:47 GMT -8
Windows "ghosts" a window when it's not responding, when this happens, it gives the window a modern border with the text on the titlebar "(Not Responding)". To disable ghosting, rename DWMGhost.dll to something else. For me, nothing breaks (except window ghosting, which is what we want to do) Log off and log back in. Open taskmgr, see if it's not responding. If done correctly, it will not have a modern border when a program hangs. Fun fact: Killing a program (with XP x64 taskmgr) that hangs with ghosting disabled will trigger this dialog: |
|
|
|
Post by OrthodoxWin32 on Sept 18, 2022 5:43:56 GMT -8
Windows "ghosts" a window when it's not responding, when this happens, it gives the window a modern border with the text on the titlebar "(Not Responding)". To disable ghosting, rename DWMGhost.dll to something else. For me, nothing breaks (except window ghosting, which is what we want to do) Log off and log back in. Open taskmgr, see if it's not responding. If done correctly, it will not have a modern border when a program hangs. Fun fact: Killing a program (with XP x64 taskmgr) that hangs with ghosting disabled will trigger this dialog: Hello TechSalt, Which DWMGhost should be renamed ? Because there are several. |
|
|
|
Post by TechSalt on Sept 18, 2022 5:44:55 GMT -8
Windows "ghosts" a window when it's not responding, when this happens, it gives the window a modern border with the text on the titlebar "(Not Responding)". To disable ghosting, rename DWMGhost.dll to something else. For me, nothing breaks (except window ghosting, which is what we want to do) Log off and log back in. Open taskmgr, see if it's not responding. If done correctly, it will not have a modern border when a program hangs. Fun fact: Killing a program (with XP x64 taskmgr) that hangs with ghosting disabled will trigger this dialog: Hello @windowstechspots, Which DWMGhost should be renamed ? Because there are several. DWMGhost.dll in System32 |
|
|
|
Post by OrthodoxWin32 on Sept 18, 2022 5:51:34 GMT -8
I don't have DWMGhost.exe in system32. However, when I search with Everything, it appears, but not in the folder. In Winfile it does not appear either. As much for me, it appears in Winfile. However, it's weird that it doesn't show up in Explorer, even with the "show hidden files" and "show system files" boxes checked. |
|
|
|
Post by TechSalt on Sept 18, 2022 6:26:03 GMT -8
I don't have DWMGhost.exe in system32. However, when I search with Everything, it appears, but not in the folder. In Winfile it does not appear either. As much for me, it appears in Winfile. However, it's weird that it doesn't show up in Explorer, even with the "show hidden files" and "show system files" boxes checked. Not the exe, the dll |
|
|
|
Post by OrthodoxWin32 on Sept 18, 2022 6:36:04 GMT -8
I don't have DWMGhost.exe in system32. However, when I search with Everything, it appears, but not in the folder. In Winfile it does not appear either. As much for me, it appears in Winfile. However, it's weird that it doesn't show up in Explorer, even with the "show hidden files" and "show system files" boxes checked. Not the exe, the dllI meant dll, not exe. It is a typing error. Anyway, I renamed the dll with Winfile, it seems to work. Thanks for the tip. |
|
|
|
Post by The Jackal on Sept 18, 2022 7:34:23 GMT -8
Windows "ghosts" a window when it's not responding, when this happens, it gives the window a modern border with the text on the titlebar "(Not Responding)". To disable ghosting, rename DWMGhost.dll to something else. For me, nothing breaks (except window ghosting, which is what we want to do) Log off and log back in. Open taskmgr, see if it's not responding. If done correctly, it will not have a modern border when a program hangs. Fun fact: Killing a program (with XP x64 taskmgr) that hangs with ghosting disabled will trigger this dialog: Confrimed working on my end, really nice find Tech. |
|
jackalretro.neocities.org/