BUG - Takes long time to shutdown computer due to DistributedCom events
For a long time i have noticed that some days it takes several minutes for my computer to shutdown instead of a few seconds. I have seen this with many iterations of Windows 10 and see it now with Win 10 Pro, 1909, 18363.476.
Some days ago i noticed that each day the computer takes minutes to shutdown i have a massive ammounts of Errors in Windows Event Viewer registered during the shutdown phase.
Yesterday i got a whopping 1560 Events in a row dating from 2019-12-11 22:16:00 - 2019-12-11 22:18:35. All of them says "The server {1EF75F33-893B-4E8F-9655-C3D602BA4897} did not register with DCOM within the required timeout." and a quick Google search points out that this is related to True Image.
This was supposed to be fixed in TI2019 but is back again in TI2020. How to fix it without uninstalling TI2020?
Enchantech wrote:Once the computer restarts go about your regular tasks, then see if the issue persists when you choose to shutdown.
If you did not install the app as an administrator then this may be at root of the issue.
The isse has been going on for a long period of time, so a restart wont solve it. I have one account only on the computer and shut the computer down every night. I reinstalled Win 10 a while ago but the issue came back. It was a clean install, iow formatting the HDD before installing Win 10.
I will try to un-install TI2020 and re-install it as an administrator. I will wait a couple of days since i tried this fix after i posted the initial post: https://kb.acronis.com/content/62200
I shut down the computer using Alt+F4 but different methods gives the same result as well. I shall add that it does not happen every shut down, it seems to be some randomness to this issue.
Roger,
As information in Win 10 a Shutdown and Restart are not the same thing. A Restart closes all applications and dumps the Hyperfil.sys information.
A Shutdown leaves the Hyperfil intact so that you as a user enjoy a faster startup of Windows. This can be problematic in how Windows performs.
If this was not known to you then I suggest the applying the Restart method I outlined so that the next user logon will have a clean start.
Roger A wrote:The isse has been going on for a long period of time, so a restart wont solve it. I have one account only on the computer and shut the computer down every night. I reinstalled Win 10 a while ago but the issue came back. It was a clean install, iow formatting the HDD before installing Win 10.
There are two problems here. The DCOM error event has, in fact, been around since Win 10 was released and is a constant irritation. A restart won't fix it. I have never followed the explanations and (temporary) fixes for the DCOM registration error, but apparently the error being raised is not a matter of concern.
However, thousands of the DCOM error being provoked, and having this slow down shutdown is a matter of concern. If something in ATI is causing this, then a restart of the computer is a good first step in trying to solve the problem.
Enchantech wrote:A Shutdown leaves the Hyperfil intact so that you as a user enjoy a faster startup of Windows. This can be problematic in how Windows performs.
I assume that you mean Hiberfil.sys instead of Hyperfil.
If yes, i have turned off the Fast Startup feature since the first install of Win 10 so it has nothing to do with Hibernation. I turn off Fast Startup once Windows is installed. So my computer takes, as expected, a tad longer to start up that it does with the default settings were Fast Startup is enabled. I have also disabled Hibernation fully on my computer approx three weeks ago using the "powercfg.exe /hibernate off" command. I did disable Hibernation since that´s one common issue for long shut downs.
I restart the computer using the Restart option in the Shut Down Windows dialog two to three times a week so i really don´t see any need in doing that since it does not matter. I have this problem for weeks, so a restart now won´t help. Or, what do i miss in this restart-treatment? :)
Sounds like you have the issue with Hiberfil (excuse my spelling) so that is not working obviously. Just trying to eliminate the easy first.
Have a look at this link for a more down and dirty solution that should fix it. I recommend a backup of your registry prior to making these changes.
Roger, can you check the Schedul2 logs to see what may be happening at the time of the problem. I've checked all my logs of all types and the Schedul2 log seems to be the only one logging during the time I last experienced this issue. Unfortunately in my case I didn't see anything fundamentally different between the day it gave me 40 or so DCOM errors and a day when it gives me none.
There can be tasks that run on system shutdown. You may want to download the Acronis Scheduler Manager to see if perhaps a task was running at that time. One warning.. the page referred to has a command to set the logging to support level and then says to disable logging by "set logflags 0". When starting, run "get logflags" so instead of setting to 0 you can set it back where it was.
Another thing you can do is get more logging according to 58243: Acronis True Image: Collecting Debug Logs.
Let us know if it gets you anywhere.
Enchantech wrote:Sounds like you have the issue with Hiberfil (excuse my spelling) so that is not working obviously. Just trying to eliminate the easy first.
Don´t get me wrong, but i think you are wrong about the hiberfile.sys in this case. As i wrote i have turned Hibernation and Fast Startup off completely and since Hibernation and Fast Startup is the only features that creates/uses hiberfil.sys i do not even have any hiberfil.sys on my computer. Since i don´t have the file, it cannot be an error in that file, since the file does not even exist. :) (See the attached file.)
I will try the link you gave me later. I did apply the Acronis-fix yesterday and want to use it a couple of days until a un-install TI2020 and install it as an administrator, give that a couple of days and then use the regedit-fix you were kind to provide. :)
BrunoC wrote:Roger, can you check the Schedul2 logs to see what may be happening at the time of the problem.
Yes, i will try that. I have time to install it tomorrow. I will post updates. :)
Roger A wrote:Enchantech wrote:Sounds like you have the issue with Hiberfil (excuse my spelling) so that is not working obviously. Just trying to eliminate the easy first.
I meant to write- Sounds like you have the issue with Hiberfil (excuse my spelling) set so that it is not working obviously. Just trying to eliminate the easy first.
Don´t get me wrong, but i think you are wrong about the hiberfile.sys in this case. As i wrote i have turned Hibernation and Fast Startup off completely and since Hibernation and Fast Startup is the only features that creates/uses hiberfil.sys i do not even have any hiberfil.sys on my computer. Since i don´t have the file, it cannot be an error in that file, since the file does not even exist. :) (See the attached file.)
I will try the link you gave me later. I did apply the Acronis-fix yesterday and want to use it a couple of days until a un-install TI2020 and install it as an administrator, give that a couple of days and then use the regedit-fix you were kind to provide. :)
Sorry for the omissions, let us know how things turn out.
Since i applied the fix outlined in https://kb.acronis.com/content/62200 DCOM errors related to Acronis seems to be totally gone.
I have learned along the way that just shutting Windows down does not just shut down Windows even if Fast Startup and Hibernation is disabled. That made me understand why my laptop draws power from the battery even if the computer has been shut down. There are two ways of how Windows treat a shutdown...
Glad you got it sorted. You are correct about Windows shutdown.
I have solved my issue by closing background apps in Task Manager.
My issue is fixed by closing startup Items through Task Manager.
Robert Smith wrote:My issue is fixed by closing startup Items through Task Manager.
Hello Robert!
Thanks for sharing the workaround!