Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Hi,

I have read here and in many other places to suppress event 10016. That is, if you as me, a bad approach.

In this case, with Windows.SecurityCenter it is not as easy to fix as the old classics with the RuntimeBroker, ShellWindows etc which is solved by giving full rights to Administrator in registry and then give SYSTEM, Local Service or whatever launch permissions in DCOM Config. The reason is that you, in this case, don't have any ApplicationId to play around with.

The problem in this case is that the service for Windows SecurityCenter (wscsvc) have a delayed autostart while "things" like the WscBrokerManager and WscCloudBackupProvider tries to initiate very early in the startup process. It will fail with error event 10016. wscsvc will initiate after ~2 minutes and then everything will be instantiated as normal so you will have no side effects of these errors in the event log but it's annoying.

You solve this by changing the service wscsvc from delayed autostart to normal autostart. You don't (normally) have permission to do it from the services app so you must do it in the registry.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc

Change the DWORD DelayedAutoStart from 1 to 0.

Have a nice day!

Hi,

Many thanks for the tip @dougy4t . My eventviewer logs are now entirely error free.

Cheers,

Did as above stated but still get 10016 every time I start chrome browser. Can this just be stopped with logger as well.

csmdew said:

Did as above stated but still get 10016 every time I start chrome browser. Can this just be stopped with logger as well.

Just ignore it. I have 2 PC:s and they both spam this same error with Chrome or Chromium based browsers like Opera and Vivaldi.

Hey, speaking of dcom issues, I have the following question:

Is there any chance that DCOM issues can prevent a computer from shutting down? Because frankly, I only have dcom errors in my event log..

I've turned on verbose status messages, and what happens is it runs through all the things it needs to do, and then it just stops at "shutting down" and does nothing. Sometimes it will take like 4 minutes to shut down, sometimes way more/it doesn't at all. Once, I noticed that it would run through everything it needed to do, then it just said "shutting down" for minutes, and then it again said "stopping services" very briefly.. and then it did finally shut down.

Atm I've enabled fast startup as a workaround.. but I really do want to actually solve the issue.

I've already run a battery of tests, and the problem genuinely doesn't seem hardware related. Also, the problem isn't present in safe mode.

f14tomcat said:

@rEEEEleaseMEE

That may be just the opposite of what you need to do. Sounds like you enabled Fast Startup because it was not enabled. There also is the hibernation file, hiberfil.sys, that the system writes to on shutdown. Do this command in an Admin Command Prompt. Just copy and paste it exactly, and hit enter. It will disable Fast Startup and delete the hiberfil.sys. Then try your shutdown.

powercfg -h off

I know how to hard disable hibernation. I've only enabled this because everything I've tried to genuinely fix the problem of windows not shutting down hasn't done anything, and I need a way to be able to turn the computer off at the end of the day.

edit: that is to say that it was set the way you're suggesting before and I had 0 issues.. and then suddenly I did and I had to enable fast startup just to be able to shut the machine down.

f14tomcat said:

Ok, was only a suggestion.

Sorry, I didn't mean to come off as unfriendly. It's been a trying week with a bunch of other annoying stuff happening as well.