Hi Peter,
Take a look at this post here for some help:
Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Page 8 - Windows 10 Forums
IMPORTANT NOTE: It is always prudent to
BACKUP ALL YOUR PERSONAL DATA TO EXTERNAL BACKUP MEDIA PRIOR TO MAKING CHANGES IN THE REGISTRY OR RUNNING SCRIPTS WRITTEN BY OTHERS IN POWER SHELL!".
You can also take additional precautions by enabling and creating a
SYSTEM RESTORE POINT just prior to making the changes suggested above. I would also suggest you run the
REGEDIT.EXE program if you're familiar with it, and create a Backup Registry File to your W10 desktop as well. If you are not familiar with how to use
REGEDIT.EXE, I would stay away from it, as it's a High-Risk program and home users are generally recommended to stay out of there unless your are an expert licensed Technician or Programmer. Both of these programs have a "Rollback" capability, which means you can undo any damage that might have occurred to your computer since the last time you remember it working prior to your problem. The
SYSTEM RESTORE POINT is certainly the easiest of all these methods I describe, and is designed for the Home User with basic or no computer knowledge.
The best thing you can do is to make a Full Hard Drive Image backup using
Macrium Reflect, Acronis TrueImage, or EASUS. We have tested all 3 of these products with various W10 machines. Personally I like Macrium Reflect the best, and I use it on all my Customer machines.
Prior to using any of these tools, we also suggest that it's prudent to unplug any and all USB devices such as external hard drives, flash drives, printers, webcams, etc. Often times devices such as these can cause issues with W10 registry because of poorly written drivers or outdated drivers. It is easiest to remove these devices, including Digital TVs, and ROKU type devices. Your error also suggests a conflict with NT Media Center Edition, which is no longer supported in W10. To me this indicates you have an old device plugged into your PC that is attempting to run drivers written in the XP-Win7 era, which did have support for Media Center Edition (this came out back in 2002 in the XP days).
If you get no results with none of the above I suggest the following:
(1.) Perform a
Windows10 in-place Upgrade Repair; you must have a
bootable W10 DVD disc or W10 USB stick in order to use this.
(2.) Perform a
Win10 Reset using
FACTORY RECOVERY DISCS or
BUILT-IN FACTORY RECOVERY PARTITION software stored in a hidden partition on your hard drive (
Drive_D: RECOVERY for example).
(3.) Perform a
Win10 Reinstallation using
FACTORY RECOVERY DISCS or
BUILT-IN FACTORY RECOVERY PARTITION software stored in a hidden partition on your hard drive (
Drive_D: RECOVERY for example).
It would also be prudent to
test your Hard Drive and RAM sticks prior to running any of these 3 options in case you have a hardware failure that is actually causing your problem. We highly recommend you do this prior to an in-place Upgrade repair or Windows Reset/Reinstallation.
Here's how to do it:
*****************************************************************************************************************************************************************
Next, you'll need to test your hardware; specifically your
Hard Drive, since it's most likely failed.
Link Removed Laptop drives begin failing as early as 2 yrs. old due to usage and age. After your
hard drive you'll need to test your
RAM memory. The following sections will help you to do this and tell you where to download the free programs to do so:
(1) Test RAM memory. If you are running Windows7, your computer is 4-5 yrs. old and is very likely to have 1 or more hardware failures to aging/usage. Download free
MEMTEST from link in my signature and test each RAM stick individually a
minimum of 8 passes. If
MEMTEST returns any errors, that RAM stick has failed and must be replaced.
Link Removed Repeat
MEMTEST on each stick until all sticks pass. Then reinsert all sticks into your computer and run
MEMTEST again for the 8 passes. Any failures reported by
MEMTEST must be corrected by replacing
RAM with matched-pairs or all sticks with new until
MEMTEST RETURNS NO ERRORS.Link Removed Once done, your
RAM has passed move onto Step #3.
(2) Test your HARD DRIVE. On a PC that's nearly 5 years old as is yours, it is
VERY likely your hard drive is failing or has failed and that's why you can't do a
SYSTEM RESTORE.
Link RemovedLink Removed Hard Drives are the #1 failed component in both desktops and laptops across all makes/models.Link Removed Download the free
SEATOOLS drive diagnostic from the link in my Signature below and run
BOTH short and long tests on your drive. If
SEATOOLS returns any errors your drive has
FAILED and must be
REPLACED. Link Removed If this is the case, you will need to start
Data Recovery to get all your Personal Data copied off that drive onto external media.
[Also, if you have a Toshiba, Hitachi, or HGST drive, SEATOOLS won't test those drives so you will have to go to WD's website wd.com and download the appropriate diagnostic, either DLG or HGST to test those 3 types of drives. Additionally if you have a SSD boot drive, you will need to download TRIM via google to test SSD drive].
*****************************************************************************************************************************************************************
Testing your Hard Drive and RAM sticks are especially important if your computer did not come with Win10 pre-installed from the factory, but rather you upgraded from an earlier edition of Windows, i.e.: Win7x/8x. The other thing that's really important here, is that when you attempt any of the destructive options #1-#3 above involving refreshing, resetting, or reinstalling Win10 is that
YOU HAVE ALL USB AND EXTERNAL DEVICES AND ANY INTERNAL SECONDARY HARD DRIVES (OR RAID DRIVES) DISCONNECTED PRIOR TO REINSTALLING OR REFRESHING WINDOWS!! People often forget about
TVs, SmartTVs, ROKU, or other network media storage or media streaming devices. You'd be amazed at how much stuff people plug into their computers!
The first thing I would do if you do the Win10 refresh/reset methods discussed above, is to fire up windows and check your Event Viewer for that same error you were getting previously. I would let that machine run for 48 hrs. continuous, to ensure that the Error is gone. Once that's the case, you can then begin plugging in your external usb devices, and secondary internal hard drives *if you have any*,
ONE AT A TIME, UNTIL THE ERROR REAPPEARS IN EVENT VIEWER. If the error reappears after reconnecting any one of these devices, it's very likely they are the cause of the error and the culprit. You can attempt to go the device manufacturer's website and download new Win10 drivers for that device; retest. If the new drivers resolve the error, you can assume you've fixed the device driver causing the error and continue the process and continue to plug in and test the next device, retest for the error, etc. etc.
If you run into the problem of one of your devices causing the error, but they either do not have an updated driver for Win10 on their website, or if they do have one and it fails to resolve the error, you can assume that device in no longer Win10 compatible and must be removed from your PC and replaced with a similar or new device that is Compatible with Win10.
If you have 10 devices plugged into your PC, and this is not unusual (I have more than that), it may take you days or weeks to find the offending device! Be Patient here!
Lastly, do not run off and begin installing previously installed programs, games, antivirus, etc. right after the Win10 refresh/reset. This will only complicate the troubleshooting of your system by injecting new software variables into the mix.
*WAIT UNTIL YOU FIND THE OFFENDING DEVICE, CORRECT IT, REMOVE IT, OR REPLACE IT WITH A WIN10 COMPATIBLE DEVICE PRIOR TO REINSTALLING ANY ALL SOFTWARE PROGRAMS!!* This is really, really important here. You want as clean a Win10 environment as possible, and many people install from 100-500 programs on their hard drive; you can see how all those extra programs can interfere with hardware driver level troubleshooting.
Best of luck to you.
Don't hesitate to post back with any questions you have.
<<<BIGBEARJEDI>>>