Windows 10: New Error in Event Log

Anybody know how to fix this issue please?

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user DALE-PC1\Dale SID (S-1-5-21-4124590474-3230443324-182549641-1000) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.Cortana_1.6.1.52_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742). This security permission can be modified using the Component Services administrative tool.

:)

 

Windows 10 Settings: Screen Lock

One more investigative step you might want to pursue is to first check the event logs for your computer. Look for errors or other anomalies which are noted. Start by doing a normal login first thing on a new day. Log in and let the PC do its thing unattended
and go into its dormant mode. Either complete power down, hibernation, or a sleep mode.

Then power up again and when it is in a normal state go to the event logs using an administrator account to access the Event logs looking for errors or other warnings that may have been recorded starting with that days entries.

Run the Event Viewer, and start reviewing the system event message entries. Any number of events can trigger warnings or errors which standout. But normal entries may also give clues to what startup items are in place for system power management. So pay
attention to both normal as well as abnormal events.

 

E71 - Putty Error

attached is the log





=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2009.06.25 18:45:45 =~=~=~=~=~=~=~=~=~=~=~=

Event Log: Writing new session log (SSH packets mode) to file: c:\putty.log

Event Log: Looking up host "10.192.99.142"

Event Log: sk_namelookup: Looking up 10.192.99.142

Event Log: sk_namelookup: Resolved to 10.192.99.142

Event Log: sk_namelookup: No reverse found

Event Log: sk_new: Connecting to 10.192.99.142, port 23, family 2048

Event Log: sk_new: Done

 

The error probably does not matter, I have one or two like this and live with them until MS get around to fixing the issues.

There is a very long thread on this here: Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Might be worth reading through it and deciding if you want to try the fixes mentioned. Yours is the Immersive Shell version that needs fixing as described on page 4 posts #38 and #39 and the following ones that describe the changes to @lx07 powerscript method.