Windows 10: usocoreworker.exe ---> Error Event ID 1000 usoclient.exe since 1903.

After updating to the Windows 10 1903 update I have noticed usocoreworker.exe is relentlessly running in the background. While it might go away within a few minutes, it is coming back a little bit too frequently now. This is getting too much already.

After the usocoreworker.exe starts running in the background. My Event Log Viewer gets flooded with these errors Application Error Event ID 1000 Task Category (100).

Faulting application name: usoclient.exe, version: 10.0.18362.145, time stamp: 0x01699b36Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81Exception code: 0xc0000409Fault offset: 0x000000000006d3beFaulting process ID: 0x1168Faulting application start time: 0x01d51bf5323408e9Faulting application path: C:\WINDOWS\System32\usoclient.exeFaulting module path: C:\WINDOWS\System32\ucrtbase.dllReport ID: 4296926e-1612-4e6e-965c-4314a8d0c55aFaulting package full name: Faulting package-relative application ID:

Prior to this 1903 update when I had Windows 10 1809 I never had usocoreworker.exe running in the Task Manager background nor did I receive any such error like that.

Is there a way to fix this problem besides either going back to Windows 8.1/7 or Windows 10 1809?

I'm assuming this error occurs even if I cleanly installed 1903 as opposed to my upgrade from 1809 to 1903.

SFC /Scannow does not find any integrity violations.

:)

 

Crashing to event ID 1000

After I have installed new computer parts my games and most particularly Destiny 2 has been crashing to event ID number 1000

I am running a GTX 1080

I7-6700k avg cpu temp is 63

32g corsair 3000 Memory (4 x 8)

So far I have reinstalled most games and have changed the CPU priority in task manager. I have also done a memory test with no useful results. I don't know if this is enough but i cant find any thing more out on the internet. sorry if this seems lack a lack
of information. Thanks for any help. If you need anything more to help solve the issue just post a message.

This is what I was able to pull from event viewer

Log Name: Application Source: Application Error Date: 1/9/2019 9:44:13 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Rozen Description: Faulting application name: destiny2.exe, version:
4541.0.0.0, time stamp: 0x5c0f1df6 Faulting module name: destiny2.exe, version: 4541.0.0.0, time stamp: 0x5c0f1df6 Exception code: 0xc0000005 Fault offset: 0x0000000001285b01 Faulting process id: 0x308c Faulting application start time: 0x01d4a8a3eb77806f Faulting
application path: C:\Program Files (x86)\Destiny 2\destiny2.exe Faulting module path: C:\Program Files (x86)\Destiny 2\destiny2.exe Report Id: a012fb58-5443-405f-95b5-93fdacb56b0e Faulting package full name: Faulting package-relative application ID: Event
Xml: <Event xmlns="Error <System>
<Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-01-10T05:44:13.037149900Z" /> <EventRecordID>2003</EventRecordID> <Channel>Application</Channel>
<Computer>Rozen</Computer> <Security /> </System> <EventData> <Data>destiny2.exe</Data> <Data>4541.0.0.0</Data> <Data>5c0f1df6</Data> <Data>destiny2.exe</Data> <Data>4541.0.0.0</Data> <Data>5c0f1df6</Data> <Data>c0000005</Data> <Data>0000000001285b01</Data>
<Data>308c</Data> <Data>01d4a8a3eb77806f</Data> <Data>C:\Program Files (x86)\Destiny 2\destiny2.exe</Data> <Data>C:\Program Files (x86)\Destiny 2\destiny2.exe</Data> <Data>a012fb58-5443-405f-95b5-93fdacb56b0e</Data> <Data> </Data> <Data> </Data> </EventData>
</Event>

 

Event ID 10016

Solved Numerous event id 10016 errors win 8 pro 64 bit

Here is the basic outline ...

1. Search the registry for the CLSID
2. Make note of the Default Value, which is the name (ex. ShellExperienceHost, RuntimeBroker) you're going to look for in DCOM
3. Change the Owner to Administrators
4. Give Administrators Full Control
5. Repeat steps 1-4 for the APPID
6. WinKey + s > type in component services > click on Component Services in list
7. Component Services > Computers > My Computer > DCOM Config
8. Change the View to Details
9. Find the name from step 2 (ex. ShellExperienceHost, RuntimeBroker)
10. Right Click on the Name > Properties
11. Select the Security Tab
12. Launch & Activation Permissions > Click Edit
13. Look for the offending user from the 10016 (ex. System, Local Service) and make sure it has the activation requested (ex. Local Activation). If the offending user does NOT exist, you have to add it and give it Local Launch and Local Activation
14. Click Apply
15. Close DCOM and Regedit
16. Reboot PC

Note: Make sure you understand the steps before doing them

 

Event ID 10016

I changed it to Administrators and gave it full control in Reg. Then re-booted. When I go to DECOM config, It's all grayed out. I tried login as administrator and same thing. Any Ideas?