Microsoft posts, then yanks, then re-posts this month’s second cumulative update for Win10 1903, KB4505903

Topic

New Reply

We have a blow-by-blow account from @EP. Microsoft released a (truly gigantic) second monthly cumulative update for Win10 version 1903 on Thursday aft
[See the full post at: Microsoft posts, then yanks, then re-posts this month’s second cumulative update for Win10 1903, KB4505903]

Reply | Quote

Replies

Why it’s gigantic? you mean the size or how much it fixes?

by the way, there were 4 versions of this update released for Insiders

Reply | Quote

The number of fixes.

Glad they finally got it right!

Reply | Quote

Got it.  Also got this, as usual:

I have never, not once, had a reboot because of a Windows Update that I did not initiate myself.  I’m not saying that others haven’t, just sayin’ it hasn’t happened to me.  When I clicked “Restart”, the update went through it’s usual routine, rebooted and continued, then presented my sign-in screen.

After I signed in, the two programs I had had running, Firefox and Outlook, re-launched as usual.  The update didn’t take very long.  I also got an update to the Windows Defender engine earlier today when I checked for updates.

It’s my personal policy to keep Windows completely updated with any and all updates pertinent to my installations.  The canary is still singing.  I’ll update the other side of my dual boot shortly.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Sure, its ready!

2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4505903) – Error 0x80070490

Reply | Quote

Found “Ready for Download and Install” and Clk’d. Macrium Images last night.

No issues …. 18362.267

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

MikeMc wrote:

Sure, its ready!

Many Windows Updates require code that was installed in previous updates.  If that code is not available …

The image you posted indicates that it’s your Windows installation that isn’t ready; “Your device is missing important security and quality fixes.”

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren wrote:

The image you posted indicates that it’s your Windows installation that isn’t ready; “Your device is missing important security and quality fixes.”

If important security updates are missing why present/install KB4505903 ? Where are Microsoft’s telemetry and AI ?

Reply | Quote

Alex5723 wrote:

If important security updates are missing why present/install KB4505903 ? Where are Microsoft’s telemetry and AI ?

Disabled, perhaps?

bbearren wrote:

It’s my personal policy to keep Windows completely updated with any and all updates pertinent to my installations.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Installed with no apparent problems.

Also installed a new SSU KB4508433

 

Barry
Windows 11 v23H2

Reply | Quote

Having just seen this update I decided to install on the one machine I have moved to 1903 just to see what, if anything would go wrong. I was greeted with the garbage in the screenshot attached. A second restart cleared things up, the system returned to normal. I’m going through the system events to hopefully find a root cause. Thus far, I cannot find anything that suggests this is happening to other Windows 1o users and may therefore be just an isolated event.

Cheers

Reply | Quote

Updated the B side of my dual boot, no problems.  RDP’d into my laptop, and the update was ready to download and install.  No problems.  RDP’d into my NAS, the update was ready to download and install.  No problems.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

I installed this update on Sunday afternoon (7/28); and there was a suspicious long pause of at least a minute or two during the install (before the reboot) at the 74% point. The update finished installing and the laptop rebooted successfully, so I assumed that the install just paused to wait for something else that was happening at the same time to finish and get out of the way.

When checking everything out after the reboot, the activity monitor showed that the update was successfully installed; and the update list showed that it, as well as a definition update were both successfully installed. However I found five WER messages elsewhere in Windows Error Reporting indicating that TiWorker.exe encountered a problem while trying to install some aspect of the update.

That’s an application within the Trusted Installer platform. It appeared to begin with what’s called a radar_pre-leak_64, which I’m guessing has something to do with accessing the registry (I’ve never touched or even looked at the registry on this laptop); so I am assuming that some minor aspect of this rather large windows update didn’t get installed properly. But whatever it was, it wasn’t enough to prevent the rest of the update from successfully installing and being reported as having done so.

There was one error in the event log saying that an application was prevented from accessing a part of the windows registry because that part of the registry was already being used by another application. But I don’t know if it waited, then tried again, and was successful on the second or subsequent attempt. In any event, everything seems to be working as normal with no problems, yet.

Reply | Quote