Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Dyabzhee said:

Hey guys, there is actually quite an easy fix for the DCOM errors. This method solved them all for me !

In Group Policy Editor (run: gpedit.msc), go to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enable "allow local activation security check exemptions"

I just tried your suggestion, and still get the errors on start up.

Dyabzhee said:

Hey guys, there is actually quite an easy fix for the DCOM errors. This method solved them all for me !

In Group Policy Editor (run: gpedit.msc), go to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enable "allow local activation security check exemptions"

and that's it? no other side effects?

Dyabzhee said:

Hey guys, there is actually quite an easy fix for the DCOM errors. This method solved them all for me !

In Group Policy Editor (run: gpedit.msc), go to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enable "allow local activation security check exemptions"

It doesn't blanket exempt everything - you need to specify the appid as well (or add it to define Activation Security Check excemptions). It will also only work if their custom launch permissions do not contain specific LocalLaunch RemoteLaunch LocalActivate or RemoteActivate grant or deny entries for any users or groups

Define Activation Security Check exemptions | Windows security encyclopedia

But is MS aware of the issue? Because I didn't find a single report in Feedback Hub about Error 10016...
Started my own (please, vote +1): Error - Windows Insider Program
... and I've learned RuntimeBroker.exe is crucial to give UWP apps the required rights to do anything out of their sendbox.

Dyabzhee said:

Hey guys, there is actually quite an easy fix for the DCOM errors. This method solved them all for me !

In Group Policy Editor (run: gpedit.msc), go to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enable "allow local activation security check exemptions"

Actually got more errors relating to DCOM after that suggestion; repair this one day and back a week later, endless cycle.

Most users seem to have these 'errors'. I just ignore them now since they don't appear to impact the PC's performance and I can't be bothered to fix them.

alexncfc said:

ID 636 - "wuaueng.dll (1144) SUS20ClientDataStore: Flush map file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.jfm" will be deleted. Reason: ReadHdrFailed."

ID 640 - "wuaueng.dll (1144) SUS20ClientDataStore: Error -1919 validating header page on flush map file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.jfm". The flush map file will be invalidated. Additional information: [SignDbHdrFromDb:Create time:08/10/2016 23:27:45.874 Rand:339180914 Computer:] [SignFmHdrFromDb:Create time:08/10/2016 23:27:45.868 Rand:82576924 Computer:] [SignDbHdrFromFm:Create time:08/10/2016 23:28:02.533 Rand:2986111576 Computer:] [SignFmHdrFromFm:Create time:08/10/2016 23:28:05.669 Rand:1313424785 Computer:]"

These are just a few examples of the errors that are constantly appearing in the event log viewer multiple times daily. I don't know if they are impacting performance but I would certainly like to rule them out. Anyone have any ideas how?

Any help much appreciated.

Alex

I was able to get rid of these two ESENT ID errors, 636 & 640.

The file always seems to be a .jfm file in question. I read on another forum that these are typically "auto form" files. Although I don't have the string anymore the ESENT errors I were getting were related to caching on Microsoft Edge and IE 11. It was always "readhdrfailed" "flush map invalidated" blah blah blah. Didn't matter how many times I cleared files and reset the browsers it they always came back. Funny thing I noticed, is they typically came back when I logged on to a web page. Facebook, or my gmail account for example. They would "auto fill" then when that error came back I always had to re-log into a page again. Something had to be deleting these files but I tried everything I could think of.

Long story short I was able to disable Windows Defender through the registry and these errors magically went away.

https://answers.microsoft.com/en-us/...6-da9a520f05f2

Windows Defender was screwing up my "auto fill" for whatever reason. I think in my case it was a conflict between browsers. It was deleting the .jfm files on both browsers. Not sure if this will help you, but it helped me.

Found one string. Just replace "Edge" with "Internet Explorer" and your set:

ID 636 - DllHost (???) Microsoft.MicrosoftEdge_8wekyb3d8bbwe_NOEDP_EDGE_IDB: Flush map file "C:\Users\Owner\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppData\User\Default\In dexed DB\IndexedDB.jfm" will be deleted. Reason: ReadHdrFailed.

Thanks!

This post is 28 pages long, way to long for me to read.
Around a week a ago I decided to fix all my error's and warnings on my Windows 10 pro.
This comparison helped me out a whole lot.
You may want to do the same thing.
I used the admin CMD and cleared the event log. (With this Code... This code is for command prompt not power shell)...
for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1"
I rebooted and took a snap shot with the snipping tool of the event viewer. Then I switched accounts and rebooted.
Then I cleared the event viewer again and rebooted, and took a look at the event viewer.
I discovered that when I logged in with my local account I was getting more errors and warnings then when I logged in with my Microsoft account.
Since I always login with my Microsoft account, I concentrated on repairing all the errors and warnings in this account only.
I'm glad to report that I have 0 errors, 0 warnings, and did not filter any in the event viewer.
This comparison may help or may not, but it's not going to effect anything on your machine.
It's just going to let you know if some of the errors are showing up because your logged in on a certain account...

Raner said:

This post is 28 pages long, way to long for me to read.

Perhaps you should mate.

No-one is asking how to clear the event log.