Makes sense. Thank you. As usual Bree is the voice of wisdom, courtesy, and thoughtfulness. I had always "assumed" that the automatic WU check for updates would snag any that were available for my system, I guess that's incorrect. I will continue to back up the system image when a CU is announced just in case WU decides to install it behind my back.
As had I, not having seen any definitive guidance from MS. Seems not to be the case though. That MS blog is the first time I've seen anything official that describes how Microsoft handle these updates.
The test is well into day 8 now and is still running 17134.228. Defender updates have been downloaded, but not KB4346783. I expect the test to end with the automatic download and install of tomorrow's 'Patch Tuesday' update. If and when it does, that would be good supporting evidence that my explanation is correct.Bree said:
WU did an automatic check for updates at 6:56PM today and installed KB4456655, KB4457146, KB4457128, and the September version of KB890830. Each was done one time only. It did the restart automatically as I was out mowing the lawn. I'm going to accept Bree's explanation that WU knows what is going on and I will just keep backups current. Interesting enough the system bld. is still at 17134.254. I thought KB4457128 would take it to 17134.285.
One of my machines did that. I manually checked for updates again and it found and installed one.
Just checked history and last one listed (top of list) was KB4457128 but it had a (2) after the KB number. Can't say I seen a bracketed number after KB before.
I have seen the bracketed number following a KB update in W10. IIRC, it was prior to V.1803. I experienced a pair of back to back updates (one supposedly correcting the other) that resulted in one of them having up to 5 installs with none of them being done successfully. I finally discovered that they had corrupted the WU control files and fortunately, I had a system image save prior to the corruption. I highly doubt this instance is anything like my previous experience, and I still have only one instance of KB4457128 being installed so far.
I got KB4457128 offered about 10 minutes ago (I didn't check - I was waiting for weeks to see what happened).
Looks like the theory of @Bree was correct - it wasn't an important update so was pushed out later in the month.
It would be interesting to know what constitutes a 'B', 'C', or 'D' release though.
The "B" release is another name for the second Tuesday ('Patch Tuesday') release. This has the latest security fixes along with non-security patches. I think we all understand this one quite well by now.
Microsoft say:Of course, being cumulative B C & D contain all previous updates, but the B release is the only one to have any new security fixes.The “C” and “D” releases occur the third and fourth weeks of the month, respectively. These preview releases contain only non-security updates, and are intended to provide visibility and testing of the planned non-security fixes targeted for the next month’s Update Tuesday release.
Windows 10 update servicing cadence - Windows 10 ForumsAt times referred to as our “B” release, Update Tuesday (most often referred to as Patch Tuesday) updates are published the second Tuesday of each month. These updates are the primary and most important of all the monthly update events and are the only regular releases that include new security fixes.
Quote