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...

I seemed to have solved this problem, well sort of!
Found the answer here. https://answers.microsoft.com/en-us/...f-c9b1687ae797

First go here to download PsTools. Extract it to a folder on your desktop.
Open Start and type cmd. Right-click the program and choose to run as administrator.
Navigate to the folder where you extracted the tools by typing "cd C:\Users\Username\Desktop\Pstools", replace Username with your username and Pstools with the folder where you extracted the tools.
When you have navigated to the correct folder, copy the following command without the quotes: "psexec.exe -i -s %windir%\system32\mmc.exe /s taskschd.msc".
Open the command window and right click, choose paste. Press enter.
Navigate to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator.
Right click the task called Reboot and click on Disable.
The task should now be disabled.

Now disable also the Windows Update and WaaSMedic task scheduler. Set them all to Disabled as well! These stupid task schedulers are simply there to keep scanning for Windows Updates at a pathological mental level.

Now download Windows Update Blocker tool from here Windows Update Blocker v1.2
Set all of these services to Disabled as well! This will ensure that the Windows Update Task Scheduler does not auto reconfigure itself back to enabled.

Now ever since I've done that, I stopped receiving the error message related to usoclient.exe. I also haven't seen the usocoreworker.exe run in the background randomly in the Task Manager last 2 days since doing that (fingers crossed)!

Obviously it is not a permanent solution, I do believe something must be corrupted with my usoclient.exe during the 1903 upgrade. However, I can't be 100% certain of that since no one here on these forums has responded to say that they also receive this error.

One thing is certain, the usocoreworker.exe in 1903 is simply relentless by default. I don't know what's up with that but it is absolutely crazy and unnecessary programming from Microsoft. I'm glad to see it stop happening now with the blocker tool. Hopefully a Windows update in future should fix this issue and the errors relating to usoclient. If I ever need to update windows I will do so manually, but I don't need Windows to have to do all their silent background schedules against my will!
I believe my PC performance has improved since having those Windows update services disabled. I was really about to give up and go back to Windows 8.1... If in future I see things like that happen again and I don't find a solution I will dump this operating system. Microsoft will lose Windows 10 customers if they continue.

It is ridiculous that I have to do it the tricky way to get those task schedulers disabled since MS has programmed Windows 10 to not let you disable those Task Schedulers the normal way. But so far no errors in Event Viewer!