Windows 10: Persistent EVENT ID 10016

Hello, every hour I get this error:

I've followed this guide: http://www.itexperience.net/2017/01/...on-with-clsid/ but didn't fixed the issue.I've the latest Windows build. Do you have any suggestion?

:)

 

Kernel-Power (63) id:41 key words : (70368744177664),(2)

The Event ID 6008 is logged to the System event log when a shutdown operation is initiated automatically by a program. Meanwhile, the
DCOM event ID 10016 is related to certain processes not having permissions to the DCOM components that are mentioned in the event logs.
The specific communications that are blocked are determined to have no adverse functionality other than generating 10016 event logs. We highly recommend that you just ignore these errors because they don't adversely affect functionality. You may
refer to this support article for more information:
DCOM event ID 10016 is logged in Windows.

We hope the information we provided helps.

 

After Windows 10 Creator's update the screensaver no longer goes away when moving mouse or pressing a key

The event log you provided can be resolved by following the resolution provided in
this article that specifically addresses DCOM event ID 10016.

 

Are you sure you have follow the instructions correctly, far as i know this error can only be repaired by following instructions at the website.

1. Type Regedit into Start Menu.
2. Go to HKEY_Classes_Root\CLSID\*CLSID*.
Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {D63B10C5-BB46-4990-A94F-E40B9D520160}.
3. Right click on it then select Permission.
4. Click Advance and change the owner to Administrators. Also click the box that will appear below the owner line.
5. Apply full control.
6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.
Note: *AppID* is the ID that appears in your event viewer. In your case it's {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}.
7. Right click on it then select permission.
8. Click Advance and change the owner to Administrators.
9. Click the box that will appear below the owner line.
10. Click Apply and grant full control to Administrators.
11. Close all tabs and go to Control Panel --> Administrative tool.
12. Open component services.
13. Click Computer, click My computer, then click DCOM Config.
14. Look for the corresponding service that appears on the error viewer.
Note: For this step, look for the one that appeared at the right panel of the RegEdit. For example, the AppID Registry (316CDED5-E4AE-4B15-9113-7055D84DCC97) contains the "Immersive Shell" Data with a (Default) as a name. Now look for "Immersive Shell".
15. Right click on it then click Properties.
16. Click security tab then click Customize in the Launch and Activation permissions section. Click Edit. Click Add. Add Local Service. Then apply.
17. Tick the Local Activation box.

 

If you still have the error it means you omitted/improperly applied step(s) along the way. Carefully retrace the steps

 

You might also wish to have a read of this (long) thread.

 

To be honest I've done a mess with those settings, I followed the short guide posted above and didn't worked.
The Mail is broken and Cortana won't show app icons... sfc scannow and DISM won't fix anything... should I re-install the entire system?

 

You should first try repair install of Windows 10, all your settings, personal files and installed programs will not be deleted you get to keep them if you do a repair install.

How to Do a Repair Install of Windows 10 with an In-place Upgrade

 

It ended up re-installing the entire system so I did a clean new FCU Windows 10 install. The problem is that I'm getting a lot of appcrash randomly

I first installed with a local account then I logged with my MS one. Also DISM and sfc /scannow say no errors.

 

You will get these errors even on a clean install. I would just leave them alone until MS fixes the issues. Beware of trying to fix these 'errors' since nobody apart from MS is aware of problems which may arise when fiddling with the permissions.

 

Same here and Restore stopped working. I've given up,hoping MS will fix it.