Windows Updates Issue after fresh MDT Deploy or In-Place Upgrade

Good morning, everyone.
Our business, within the last few months, has decided to push through with a company-wide upgrade to Win 10 Pro (not Enterprise). And while the initiative to upgrade is recent, we in IT had spent the previous 8 months before that to hammer out a solid image. Things are going smoothly for the most part, we have nice image deployed, except we have an on again/off again problem with Windows Update. After the deploy or inplace upgrade I'm finding that close to half the time, Windows updates don't work. What happens is, after the machines hit the WSUS server, report in, and they download their updates, if i'm not riding the machine when it finished downloading its updates, the 'Install Now' button disappears. In the example below, I deployed this computer's new image yesterday afternoon, got everything set, and left it on to let it tag up with WSUS and download its updates. It's a Lenovo Thinkpad T580, if that matters. I come in this morning, and this is what I see:

Another symptom that goes along with this is that the C:\ProgramData\USOShared\Logs folder fills up with files. When I first experienced this (and not knowing about it), this folder literally filled up the remainder of the 70GB of free space post-deploy after about 4 days. This morning, there were ~50,000 files in this folder. I rebooted to try and start updates again, and in the time i've taken to write this, 1,000 files have generated in here, approximately 1-2 files every second.


So far, the only solution i've come across has been to run Tweaking.com's Windows Update Fix, immediately followed by the Windows Update Troubleshooter Stand-alone, downloaded from Microsoft (not the built-in troubleshooter in Win 10). Sometimes I have to do this process twice, and even rarer yet, I have to re-image because I can't get it to update. After this, as near as I can tell, updates are working fine.

Some things we do as part of the deploy is hide most of the store apps, I don't know if that makes a difference or not. I tried some of the troubleshooting steps I've seen around here, with no success. I did try to update with WUAUCLT /updatenow with no success.

Any thoughts on this? I'd love to prevent this if I can.

Hi, Which Windows build are you using?
Windows key + R, winver

You may know build 1809 has been paused after a brief initial release last month.

It may be that you're experiencing problems because MS is having difficulty with their servers.

MSFT acknowledges some Win10 Pro licenses being mistakenly deactivated - Windows 10 Forums

- may be somehow related.. + the difficulty with not distributing 1809...which is on hold..

I've noted 1 user had a possibly rather similar problem- 1803, two PCs, same build, one with updates pending that would not install but the other ok.

Note that 1803 has a problem, widely reported, with setting default file type associations. Some attribute this to one update, some to having certain 3rd party programs installed.