Windows 10: Event 10010 for E44E9428-BDBC-4987-A099-40DC8FD255E7

Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 30/11/2021 16:57:01 Event ID: 10010 Task Category: None Level: Error Keywords: Classic User: PZ-DESKTOP\a_lex Computer: Pz-DESKTOP Description: The server {E44E9428-BDBC-4987-A099-40DC8FD255E7} did not register with DCOM within the required timeout. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 10010 0 2 0 0 0x8080000000000000 7688 System Pz-DESKTOP {E44E9428-BDBC-4987-A099-40DC8FD255E7}My system specsWindows 11 OS Build 22000.348Core i9 9900kAsus ROG Strix Z390-F Gaming updated to latest bios 2004Ca

:)

 

Host file hijack

It sounds like something set your default program for no extension files to be ME2. If you feel comfortable editing the registry, (there is a potential for damage here so follow things exactly), you can navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts and then left-click on the "." in there. This will highlight it and now you should right-click on it. Click on the "Export" option and save that file to the desktop, (this will give you a backup point should anything go wrong for the key that you have highlighted). After that, click on the "+" plus sign to open up the folder and make sure the only folder in there is: "OpenWithList". After you do that, delete all of the entries except for "Default". The only thing in default should be: (value not set). Really it shouldn't matter if there's anything else in the default entry, so don't fret if there is.

If you have a problem after doing any of this, then double-click on the file you exported at the start to undo the damage you may have done to that key. Mind you, if you did any thing not listed in here, then that damage will not be undone by the file you exported and you may be in trouble.

Edit:
I should have been a little more specific, so I apologize for that. On the right hand side of the Regedit window there could be some entries as well, make sure you delete those as well. I've posted a screen shot of both folders for you. The right hand side should only have the default entries.
Screen shot.

Edit 2:
Okay, it looks like I was a bit off on what I told you earlier, so I apologize for that. The method above fixes files with a "." period at the end of a file name and no extension. You need to reset the file association with no period at all. If you look at: HKEY_CLASSES_ROOT\Unknown, you'll probably see that your game is listed in one or more of the entries inside of there. Left click on Unknown then right-click on it and export that key entry to somewhere safe, (always backup before messing with the registry). Next open up notepad or your plain text editor of choice and paste this into it, (this version is for Windows 7):

Or if you have Windows 10, use this one instead:

Next save it as: "UnknownReset.reg", please note that the quotations are needed as notepad will automatically add the .txt extension if you don't have quotes around the file name. Next, double-click on the newly created file and that should fix your issue. If it saved the file with a .txt extension, then you'll have to remove the extension and try again, or manually import the data in Regedit. To manually import, you can open Regedit, then click on the File menu and then Import. Choose All files from the drop down and then choose the file you put the above code in. So long as it was properly pasted into the file, it should work.

 

System Event ID 10010

Try this:
PRB: ASP pages do not process and DCOM event 10010 appears in the system event log

 

Are you getting DistributedCOM Event ID: 10010 errors with 11.4?

For those that updated to Cat 11.4 could you check the event viewer's Administrative Events (type Event Viewer in Start's search box, click on it, let it load, then select Custom View then Admin. Events) to see if you are getting: DistributedCOM Event ID: 10010, E10F6C3A-F1AE-4ADC-AA9D-2FE6552566 errors? To check if you are continuing to get them pick a specific time to reboot and once back up to desktop check the event viewer again to see if the error pops up again at the time the PC shutdown.