Error - Event ID: 10016; DistributedCOM

When you say your PC shuts down it leads me to believe that it may be related to your Power Settings. Some come 'out of the box' or 'stock' to shut down after so many minutes. It could be sleep settings or hard drive settings to name a few. Those two need to be set to NEVER. Double check your Power Settings and make sure that they aren't set to shut down things. You'll have to go through each an every one setting them to the way you want when finished create your own personal power settings while there so if need be you can just click on that to reset them back to the way you want.

As far as DCOM errors go you'll have to find which GUID is being generated in the Event Viewer showing those errors. Then you'll have to go into the registry file an 'take ownership' which means you'll change the Permissions to Administrators to allow you to change those settings. Some times they are default set to Trusted Installer, by changing those you'll be able then to go to the Group Policy Editor and add SYSTEM to that group (along with Administrators) that will stop those DCOM errors in W10. It usually is a RunTimeBroker setting that needs to be 'tweaked' Here is a link I used to fix those DCOM errors. I also had one other GUID showing so I copied that from Event Viewer and searched regedit changed those permissions to Administrator along with the greyed-out RunTime in GPO (Group Policy Editor) 

note these tips where taken from a blog site found on Google

Regedit Take Ownership

You will need to take ownership then set rights against two different keys.  The keys are:

HKEY_CLASSES_ROOT\AppID{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

HKEY_CLASSES_ROOT\CLSID{D63B10C5-BB46-4990-A94F-E40B9D520160}

Open Regedit with Administrators privileges and navigate to the keys above (remember you have to do this twice)

WinKey + X >> Command Prompt (Admin) >> Type in Regedit

Right click the key >> permissions

Click advanced

At the top change the Owner to COMPUTERNAME\Administrators

Please note if you are domain joined you’ll have to change where you are searching from to your local computer

Look in the Permission Entries field

If the local system administrators group is listed ensure it has full control

if the administrators group is not listed add it and give it full control.  (note you can only do this if you are a member of the administrators group and it is now the owner)

Click okay a lot >> Ensure you apply permissions to all child objects

Change DCOM Permissions

Need to ensure DCOM permissions are setup

Open DCOMCNFG as an Administrator

WinKey + X >> Command Prompt (Admin) >> Type in DCOMCNFG

Navigate to Component Services >> Computers >> My Computer >> DCOM Config

Find the RunTimeBroker  >> Right Click >> Properties >> Security Tab

Launch and Activation Permissions >> Edit >> Add System and give it full control

I also added the Administrators group just for testing

While changing permissions I was prompted several times to remove bad account references.  I did this as the computer knows which accounts have been removed.

Summary

At this point you should have sorted the DCOM errors.  Give your computer a reboot.

It can be a bit daunting at first I know it took me several tries til I felt comfortable with it. The main thing is getting the DCOM error App ID & GUID from the Event Viewer errors and finding them in the Registry.

Sorry but I'm not especially tech savvy. And I'm a tad confused. Got my computer three days ago and it has shutdown twice and restarted with the 10016 error. I have version 1709. From what you said, should I go ahead and apply the fix, or leave it alone?

Something similar occurred with a previous laptop I had for only a week before returning it. Any assistance would be great as I wouldn't like for this to start cutting out more often.

I agree...did the Fall Update (1709) tried to get rid of Windows.MiracastViewer logged errors (following tips an tricks all over the net)  an it caused all sorts of DCOM issues. So (an for other various reasons) I reinstalled the 1703 version an dealt with DCOM errors on a  per GUID (& APP ID) basis which is to say thru permissons (i.e. took ownership) on an individual basis without using Local Policy Group Editor or changing those settings. Doing so eliminated all the DCOM Event errors for me. (but you just never know theses days if that sort of thing will re-emerge) 

At this point in time 1709 (Redstone 3?) is not running smoothly for me, with those DCOM an other Event Viewer errors so going back to 1703 an working through the DCOM (much fewer) as stated on an individual basis eliminated them. There was a 'fix' for DCOM 10016 errors on another site that went as follows:

1. Type or paste ‘regedit’ into the Search Windows box.
2. Navigate to ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole’.
3. Delete these four keys if they appear, DefaultAccessPermission, DefaultLaunchPermission, MachineAccessRestriction, MachineLaunchRestriction.
4. Reboot your computer. 

What doing this did (for me) was cause MORE DCOM errors both in 1703 AND 1709 OS versions. Seems like the latest iteration of Win10 (1709) hates any tinkering with the registry files or trying to change installed apps settings; plus I found windows settings changed not to my liking in 1709 an can only be changed back using Local Group Policy (which I find odd in that they were not tinkered with in the earlier OS version)

This does NOT work in all circumstances for people getting Access Denied errors, they need to use the true admin account to make these changes.

Furthermore, DCOM errors can resurface with different CLSID's or APPID's

In my case I had a new APPID which was associated with about 10 different CLSID's.

The process for resolving is the same, if you get access denied use the true admin account.

AND DO NOT use the APPID's or CLSID's given in all of these guides as they may be different from PC to PC.