Persistent Event Viewer Error

Page 2 of 2 FirstFirst 12

  1. Posts : 2,832
    Windows 10 Pro X64
       #11

    Hi,

    Could you post a screenshot of the error message in event viewer.
    I suspect it's a number of services that try to restart at shutdown.

    Cheers,
      My Computers


  2. Posts : 318
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
       #12

    fdegrove - Hope you can open the attached - is a zip of a doc. Had to delete some of the screenshots to meet 10 Forum's limit.

    Copy of DCOM errors - screenshots 1-2-16.zip
      My Computer


  3. Posts : 2,832
    Windows 10 Pro X64
       #13

    Hi,

    That's the typical DCOM error that's been around for awhile.
    Follow the instructions as described in a previous post here of mine and you should get rid of it forever.

    Cheers,
      My Computers


  4. Posts : 318
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
       #14

    fdegrove - vaio's post was the first thing I tried a few days ago. Unfortunately, when I get to "then open the Launch and Activation permissions Edit button", either that Edit button is greyed out or I get a warning that (from another post) if I ignore I'll brick my Win 10.
    Another MS mess.
      My Computer


  5. Posts : 2,832
    Windows 10 Pro X64
       #15

    Hi,

    If when in DComcnfg the edit buttons are greyed out that would be an indication that the editing rights are still with Trusted Installer and not Administrators.
    Assuming you have admin rights on that machine, you first need to grant yourself permission by following the steps described in Vaio7's instruction which I copied here before.

    Once that's correctly set for both hive keys you can then edit permissions in Dcomcnfg by right clicking on the runtimebroker symbol.
    Should dcomcnfg pop up a message then just agree with what it suggests it does no harm whatsoever.

    After editing dcom you then grant back ownership to Trusted Installer by editing the same keys in the registry once more. Reboot to see if the error's gone. It should.

    Anecdotally, I just finished a clean install of Win10 and of course the same event id error popped up. It's fixed now simply by following the very same instructions.


    Cheers,
      My Computers


  6. Posts : 5
    Windows 10 x64
    Thread Starter
       #16

    I think it depends on each specific component whether it is triggered by shutdowns or restarts, or just happens periodically. Surely microsoft could have fixed it in a service pack by now?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:28.
Find Us




Windows 10 Forums