At the time, I was not aware that the Xbox 360 wireless controller could be part of the problem. Plus it stopped the dwm.exe errors from happening at shutdown. Disabling it didn't seem to make a difference.
I initially found boot times in Windows 10 with fast startup enabled to be abysmally slow in comparison to what they were in Windows 8. "After some additional thought, I do not consider turning of fast startup to eliminate the issue to be an acceptable solution to this problem. So for me the convenience of being able to leave the controller plugged in outweighs my need for a slightly faster boot time. Since I'm booting from an SSD, my system boot time is about the same with or without "Fast Boot" enabled. I found that when "Fast Boot" is disabled in the power configuration setup screen, DWM.EXE no longer fails at shutdown when the X-box 360 controller is connected. I may have accidentally stumbled across an alternative way to fix the problem that doesn require the controller to be unplugged. I decided to leave the controller plugged in and live with the error as it was more of an annoyance than a real problem. As others have already noted, I found that it went away when the X-box 360 wireless controller was unplugged. "I had the same issue with DWM.EXE failing at shutdown.
When I disabled the driver through my device manager I stopped getting the error." For me it looks like the issue was related to the driver for my xbox controller. "I was having the same error and have been trying to solve it for a while. Once I removed the controller I never got the error again." Once I removed Kaspersky Internet Security the error changed to something like which then led me to think it was the Xbox 360 controller I had recently hooked up. For some reason the original error never pointed in the direction of the controller. I did a clean boot and was still getting the error. "This is exactly what I came to as also the cause recently. Googled and found out that Xbox 360's controller is actually causing people to have the same crash of the 2 things together. Never had this issue when i was in WIndows 8.1.ĭid a little investigation, and My computer event log points to "combase.dll" "dwm.exe" to be the culprits. Im having this issue, and I'm new on Windows 10.