usoclient.exe errors

Topic

New Reply

After the installation of the July update to 20H2 I’ve been getting daily application errors  involving usoclient.exe, as follows:

Log Name: Application
Source: Application Error
Date: 7/16/2021 10:48:50 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-SCFKLGJ
Description:
Faulting application name: usoclient.exe, version: 10.0.19041.906, time stamp: 0xdd46bcf0
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x1894
Faulting application start time: 0x01d77a51b00e5e3c
Faulting application path: C:\WINDOWS\System32\usoclient.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: fb0fd940-2d4c-4acc-b87c-538aabfcd72d
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Application Error” />
<EventID Qualifiers=”0″>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2021-07-16T14:48:50.9010754Z” />
<EventRecordID>18829</EventRecordID>
<Correlation />
<Execution ProcessID=”0″ ThreadID=”0″ />
<Channel>Application</Channel>
<Computer>DESKTOP-SCFKLGJ</Computer>
<Security />
</System>
<EventData>
<Data>usoclient.exe</Data>
<Data>10.0.19041.906</Data>
<Data>dd46bcf0</Data>
<Data>ucrtbase.dll</Data>
<Data>10.0.19041.789</Data>
<Data>2bd748bf</Data>
<Data>c0000409</Data>
<Data>000000000007286e</Data>
<Data>1894</Data>
<Data>01d77a51b00e5e3c</Data>
<Data>C:\WINDOWS\System32\usoclient.exe</Data>
<Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
<Data>fb0fd940-2d4c-4acc-b87c-538aabfcd72d</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

I’ve gone to several sites and found “fixes” relating to changes in my Group Policy Editor and my registry and I’ve made them. I’ve run an sfc scan and it shows no issues. I’ve also checked the health of my system image and it shows no component corruption as it relates to 10.0.19042.1110. And, yet, the application errors continue. Any suggestions?

Reply | Quote

Replies

Uninstall and reinstall the update does it still happen to your computer?

Also you could also just report it to Microsoft, they will have to fix these serious errors. After looking up these error codes it may involve memory corruption and USOCLIENT is doing the right behavior by ceasing operation. (It looks like the DLL is causing the problem.)

usoclient.exe
10.0.19041.906
dd46bcf0 (Oddly, looking this timestamp up points to a Windows Update troubleshooter.)
ucrtbase.dll
10.0.19041.789
2bd748bf
c0000409
000000000007286e
1894
01d77a51b00e5e3c

Reply | Quote

I ran the update troubleshooter and everything checked out. M$ says everything is okay. I also uninstalled and reinstalled the update; no change.

This is one of the sites I found in my search for a fix. (The same suggestions were found in additional searches.) I did everything suggested with no favorable results.  Any other suggestions?

Peace, CAS

Reply | Quote

Looked at the update release notes and Microsoft changed Windows Update again for this release, you may have an unusual case where it is now broken for you.

Please open Event Viewer and go to Application and then open a session of PowerShell and try usoclient StartInteractiveScan, and then refresh the Application Event log a few minutes to note if it crashed immediately.

Are you able to temporarily disable UsoClient with Group Policy?

Can you think of any other changes you may have made recently?

If there is no successful operation you should report it to Microsoft ask them if there any hotfixes for this or underlying runtime libraries.

1 user thanked author for this post.

CAS

Reply | Quote

Not many here like Microsoft’s KB4023057 (I installed it many times with no ill effects).

This update includes reliability improvements to Windows Update Service components in Windows 10, versions 1507, 1511, 1607, 1703, 1709, 1803, 1909, 2004, 20H2, and 21H1. It may take steps to free up disk space on your device if you do not have enough disk space to install Windows updates.

This update includes files and resources that address issues that affect the update processes in Windows 10 that may prevent important Windows updates from being installed. These improvements help make sure that updates are installed seamlessly on your device, and they help improve the reliability and security of devices that are running Windows 10. …

If you haven’t installed yet KB4023057 may fix usoclient.exe errors and other WU bugs.

Make a backup before installing the update.

1 user thanked author for this post.

CAS

Reply | Quote

Gentlemen, I’ve done as each of you suggested with no positive results. As a last resort, I restored the backup I did before the July update and I’m starting from scratch and hoping for the best.

Before the download and install of the update, I ran an sfc scan and took ownership of the two usoclient exe. files dated 6-10-2021. To my amazement, after restarting my PC to finish installing the update, the event log showed no errors. Thanks again for your suggestions and concern.

Peace, CAS

 

1 user thanked author for this post.

Alex5723

Reply | Quote

…I ran an sfc scan and took ownership of the two usoclient exe. files dated 6-10-2021…

Where were these two usoclient.exe files located?

I haven’t installed the July update yet, but in looking at my usoclient.exe file, it’s dated April of this year, and has the same version number as shown in your error logs, not June 21st. Also, the file’s owner is shown as the TrustedInstaller. It’s the only person or group that has full control of the file, all anyone else has is read and read and execute permissions. This includes the System…it only has read and read and execute permissions.

Questions aside, it’s great to hear you got the file to stop generating the errors that were filling up the Event Log! Taking ownership is quite a simple thing to do, but can cause problems if done incorrectly on certain files, I suppose.

BTW, in your post, you make it sound as if running sfc.exe allowed you to take ownership, rather than taking it through the file’s Properties sheet and the subsequent Security tab. Is that indeed true?

Reply | Quote

Bob, I use a tool called winaero tweaker. I have found it to be invaluable. Among the many “tweaks” is one that allows you to take ownership of a file and adds it to your content menu. There are many other helpful things that I have added to my content menu including running an sfc scan, checking/repairing the health of windows image all done by right clicking your mouse. If you click on the link in the first sentence it will take you to the site.

I use a search tool called Everything to search my computer and locate these files. (I do not use Cortana or any applications from M$.) I found the April versions of usoclient.exe and, yesterday, I recalled after I created this post that I had the same issue previously and resolved it by taking ownership of the files. (My memory isn’t what it used to be as I approach 80.)

I’m aware of the risks involved in allowing the “user” to take ownership. (Trusted Installer was not the previous owner of this file. I live alone and am the only one using this PC, I’m not worried. I guess you can make changes in the security settings but what I did was much easier for me. The sfc scan was run just to make certain I hadn’t screwed anything up.

I hope that my reply helps you out, Bob. I’m generally looking for help on this site rather than giving it.

Peace, CAS

Win 10 Pro. Version 20H2 (OS Build 19042.1110)

Reply | Quote