Cumulative Update KB4515384 Windows 10 v1903 build 18362.356 Sept. 10 Win Update

Decided to give it a go earlier today after a week or so without powering my home PC, despite seeing yet more carnage introduced by MS... The upside is that none of these so-called side-effects should impact me.

And: all is well so far, and although deployment took some time - as opposed to the swift installation witnessed by others - CU installed & system updated without issues.

I do not experience any increased load @ CPU either and everything seems to be fine.
I'm creating fresh system image as the latest one I have is a faulty one, created post 26/07, so after non-security CU installation that (assumingly) broke update processes.

What I'm still reluctant to do is to perform any component store clean up - and I suspect that this has broken my updates in Jul/Aug (as reported in another thread earlier).

What I'm still really eager to know though is what exactly broke it. I trust Microsoft will advise on this one at some stage - updates failure issue is still under investigation.

Windows 10, version 1903 and Windows Server, version 1903 - Windows Release Information

krzemien said:

What I'm still reluctant to do is to perform any component store clean up - and I suspect that this has broken my updates in Jul/Aug (as reported in another thread earlier).

I doubt that cleaning the component store was responsible. For years my 'Patch Tuesday' routine for all my machines is to follow up the install of the cumulative update with a component store clean up. None of my machines have had any problems with 'broken updates'.

Bree said:

I doubt that cleaning the component store was responsible. For years my 'Patch Tuesday' routine for all my machines is to follow up the install of the cumulative update with a component store clean up. None of my machines have had any problems with 'broken updates'.

Bree said:

I doubt that cleaning the component store was responsible. For years my 'Patch Tuesday' routine for all my machines is to follow up the install of the cumulative update with a component store clean up. None of my machines have had any problems with 'broken updates'.

Well, it might have been both 26/07 CU and subsequent component store clean up - or something along these lines. Something broke it around then, for sure (and it wasn't me), literally few weeks from upgrading to 1903.

Please note that quite a few posters had to resort to in-place upgrade around then unexpectedly - which is quite telling either.

In either case and getting back to the original subject: this thread is yet another proof that 1903 is just not ready for business deployment.

WEKJR said:

The system wont uninstall KB4515384 I also have a high CPU Usage running around 30% when doing nothing. How did you uninstall KB4515384?

WEK

Control Panel.>Programs and Features>View Installed Updates>Right click on update to uninstall

If you have a Macrium image from before the update you can always restore it too.

Uninstall a KB file

In Powershell ISE admin:
List of KB files

Code:

wmic qfe list

Uninstall latest one:

Code:

wusa /uninstall /kb:4515384

I believe this update has borked any machine on my network on 1903 in regards to our county print server. Printer GPOs that have been in place for years for Canon Copiers in my schools are not functioning properly. Started off with just a few machines/people but now it is spreading to different buildings. People can't print to copiers now or are being asked to install them or they aren't showing up for new students logging into machines with domain accounts that get copiers installed by user GPO, or the printers look like they are installing and quit halfway. I heard about this update having sound issues but now reading its having other effects.

I recreated GPOs, uninstalled/installed "problem" copiers, tried different drivers, nothing. Found a old laptop running Win7 32bit lying in a closet in a school I was in yesterday, hooked it up, put on domain, it installed the copiers. I just rolled back updates on a 1903 laptop in my office that I had been testing with to a few weeks ago, signed on as a student from a group that is suppose to get two printers installed to it via GPO, installed right away.

krzemien said:

In either case and getting back to the original subject: this thread is yet another proof that 1903 is just not ready for business deployment.

I work for a major association in Canada. Was curious to see what we're on at work so I checked my machine last week. 1709.