Windows 11. Getting alot of error event ID 10010 and 10016 that are causing a lot of disconnections

Question

It will just boot me from my game, or if I am playing online poker it will disconnect me over and over again. I have tried going through regedit and there are a few restrictions that it won't let me replace all child object permission entries with inheritable permission entries from this object. Change to administrators and followed the directions to change for my control It may not be the issue, but the frequent disconnects are getting alarming. I have always had this issue with this pc, I have done a factory reset and a reset that kept files, I had other issues along with this. Maybe I just need to reinstall drivers I don't know

Name resolution for the name t-s2-ring.msedge.net timed out after none of the configured DNS servers responded. Client PID 11912.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

Windows.SecurityCenter.WscDataProtection (can't change child object permissions)

and APPID

Unavailable

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} (can't change child object permissions)

and APPID

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

to the user jasonspc\jsh16 SID (S-1-5-21-4107777124-612541152-3490830075-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} (can change child object permissions)

and APPID

{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Name resolution for the name wpad timed out after none of the configured DNS servers responded. Client PID 3796.

I created a saved event id log, but I don't know how to attach the file I can't find it when searching, imagine it's to big, currently named

event id errors.evtx

Answer 1

1

Click your Start Button, type cmd and choose Command Prompt

Run this command and hit Enter:

ipconfig /flushdns

Run this command and hit Enter:

ipconfig /registerdns

Run this command and hit Enter:

netsh winsock reset

Run this command and hit Enter:

netsh int ip reset

Close Command Prompt

Open the Settings App

Go to Network and Internet

Click the Network Reset button

Wait for your PC to automatically restart after 5 minutes, do not manually restart your PC.

2

If that does not resolve the problem, go to the support page for your PC on the manufacturers website, then from there, download and reinstall (not update) the version of network drivers they provide.

If you have any difficulty locating that support page, click your Start Button, then just type msinfo and press Enter, please provide a screenshot of the resulting System Information window.

Click your Start Button, then just type msinfo and press Enter, please provide a screenshot of the resulting System Information window.

Answer 2

Event ID 10010/10016 DCOM errors are not the root cause of the disconnects and should not be “fixed” by changing permissions. They are expected, mostly harmless events and are usually unrelated to network drops.

1. What the 10016 events mean

• These events are logged when Microsoft components try to access a DCOM component without the required permissions on the first attempt.
• The code then retries with a different set of parameters and continues normally.
• This pattern is by design and does not break Windows features or network connectivity.
• Official guidance is that these events can be safely ignored because they do not adversely affect functionality.
• Modifying DCOM permissions or registry ACLs to remove these events is not recommended, as it can have unintended side effects.

2. Why changing COM/registry permissions is a bad direction

From the context:

• Extensive permission changes in the registry and file system can’t be cleanly rolled back and may cause serious problems or weaken security.
• The only guaranteed way to return to out‑of‑box security/permissions is a full OS reinstall.

Given that:

• Trying to “fix” 10016 by forcing ownership and changing child object permissions in the registry is risky.
• The fact that some keys “won’t let” child permissions be replaced is normal for protected system keys and should be left alone.

3. How to deal with 10016 if they are just annoying

If the events are only bothersome in Event Viewer:

• They can be filtered out instead of fixed.
• In Event Viewer, create a custom view and edit the XML query to exclude Event ID 10016 (and 10010 if desired) or specific CLSID/APPID combinations.
• This hides them from view but does not change system behavior.

4. Where to focus for the real issue: disconnects and DNS timeouts

The symptoms that matter for the disconnects are:

• “Name resolution for the name t-s2-ring.msedge.net timed out after none of the configured DNS servers responded.”
• “Name resolution for the name wpad timed out after none of the configured DNS servers responded.”

These point to DNS or general network reliability problems, not DCOM security. The likely areas to investigate are:

• DNS servers: intermittent or slow responses from the configured DNS servers.
• Network adapter drivers: outdated or unstable drivers causing brief drops.
• Router/ISP: momentary loss of connectivity or packet loss.
• Security/VPN software: firewalls, antivirus, or VPN clients interfering with DNS or game traffic.

5. Practical direction forward (without touching DCOM/registry ACLs)

Based on the provided context, the supported guidance is:

• Do not continue changing registry or DCOM permissions to resolve 10016/10010.
• Treat 10016 as expected noise and either ignore or filter them in Event Viewer.
• Focus troubleshooting on network/DNS, adapter drivers, and any third‑party networking/security software.

If the system has already had multiple resets and still shows the same network behavior, a clean OS reinstall with default permissions and then careful driver installation (chipset, network, GPU from the OEM) is often the most reliable way to eliminate any lingering permission misconfigurations.

---

References:

• DCOM event ID 10016 is logged in Windows