F5F Stay Refreshed Software Operating Systems Windows requires a significant duration to shut down.

Windows requires a significant duration to shut down.

Windows requires a significant duration to shut down.

B
brobear7
Posting Freak
892
05-22-2016, 01:15 PM
#1
Over the last few days my computer has been having trouble shutting down completely. Whether I press the physical button, use the start menu, or run commands in cmd, it takes a long time before it finally turns off. I tried everything possible: ran sfc /scannow, DISM, TRON, and even reinstalling Windows, which I’d rather avoid. I’ve noticed this issue disappears if I shut down Windows right after it boots or at any point before logging into Windows Checking the event viewer reveals an Info entry from User32 indicating a log was created. Warning, this time DistributedCOM reported: After about 40 seconds another log appears, then after roughly 2 minutes a Service Control Manager entry shows up just before shutdown. I remember installing Process Hacker 2 before this, but it worked fine before and never caused problems. Any suggestions on what might be causing this?
B
brobear7
05-22-2016, 01:15 PM #1

Over the last few days my computer has been having trouble shutting down completely. Whether I press the physical button, use the start menu, or run commands in cmd, it takes a long time before it finally turns off. I tried everything possible: ran sfc /scannow, DISM, TRON, and even reinstalling Windows, which I’d rather avoid. I’ve noticed this issue disappears if I shut down Windows right after it boots or at any point before logging into Windows Checking the event viewer reveals an Info entry from User32 indicating a log was created. Warning, this time DistributedCOM reported: After about 40 seconds another log appears, then after roughly 2 minutes a Service Control Manager entry shows up just before shutdown. I remember installing Process Hacker 2 before this, but it worked fine before and never caused problems. Any suggestions on what might be causing this?

N
Nikos3434
Member
133
05-22-2016, 03:11 PM
#2
In reality, none of those logs directly explain the delay in shutdown except the first one. The most frequent issue seems to be either a recently installed software preventing the shutdown process or a USB device causing driver conflicts. This idea is supported by the fact that quick shutdowns often fail. It’s possible third-party services haven’t started yet. I recommend disconnecting all devices except your monitor and keyboard to test if shutdown times improve.
N
Nikos3434
05-22-2016, 03:11 PM #2

In reality, none of those logs directly explain the delay in shutdown except the first one. The most frequent issue seems to be either a recently installed software preventing the shutdown process or a USB device causing driver conflicts. This idea is supported by the fact that quick shutdowns often fail. It’s possible third-party services haven’t started yet. I recommend disconnecting all devices except your monitor and keyboard to test if shutdown times improve.

K
Kayzan_
Senior Member
252
05-30-2016, 07:36 PM
#3
Thanks for your response and the log details. I attempted the USB method, but nothing seemed to improve. I suspect a corrupted file might be the issue, though none of the tools like sfc or dism detected it. It's also possible since I haven't installed any updates besides Process Hacker 2.
K
Kayzan_
05-30-2016, 07:36 PM #3

Thanks for your response and the log details. I attempted the USB method, but nothing seemed to improve. I suspect a corrupted file might be the issue, though none of the tools like sfc or dism detected it. It's also possible since I haven't installed any updates besides Process Hacker 2.

C
cally1900
Member
165
06-17-2016, 10:37 PM
#4
It doesn't always need to be brand new; updates can cause issues too. You might want to test Windows in Safe mode to check if the problem persists there. If it doesn’t, you know the issue isn’t with Windows itself but with the software. It could be a third-party program. You’ve already excluded USB devices.
C
cally1900
06-17-2016, 10:37 PM #4

It doesn't always need to be brand new; updates can cause issues too. You might want to test Windows in Safe mode to check if the problem persists there. If it doesn’t, you know the issue isn’t with Windows itself but with the software. It could be a third-party program. You’ve already excluded USB devices.