New
#1
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.
- - - Updated - - -
Finally identified the cause of the error! As you can see usoclient.exe Error in my Event Viewer occurred at 11:37PM and this coincides with the Universal Orchestrator Start service that was also scheduled to run at 11:37PM.
Sadly I have no permission to disable this Task. I get "The user account you are operating under does not have permission to disable this task."
I guess this is the cause of it. However, it is difficult to find a solution to this issue. The cause has been identified but the solution hasn't. It is something broken related to 1903 because I've had 1809 installed for 1 month since 12th of May and I never had any such errors.
Now none of you guys have responded to let me know if you also get this error in your event log. So it is difficult for me to know if a clean install of 1903 will fix this issue or whether it is a corruption caused since upgrading from 1809 to 1903...