userpuser
Full Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Может кому-то пригодится, на тему:
Цитата: Друзья, как избавится от ошибки в журнале?
DistributedCOM 10ка х64 - 1803
------------------------------------------------
.......
Не в тему, есть же топик
Но если ошибка связана с Windows.SecurityCenter.WscBrokerManager - то можно вообще не обращать на неё внимание.
|
Но избавиться можно легко:
Цитата: Event ID 10016, DistributedCOM Windows.SecurityCenter.WscBrokerManager Solved - Page 2 - Windows 10 Forums
9 октября 2018 г.
20:40
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.
|
|
Всего записей: 557 | Зарегистр. 22-12-2005 | Отправлено: 05:26 10-10-2018 | Исправлено: userpuser, 17:46 10-10-2018 |
|
