On Sun, 16 Sep 2018 20:19:01 -0400, in alt.comp.os.windows-10, Paul
wrote:

Zaghadka wrote:
On Sun, 16 Sep 2018 19:55:02 -0000 (UTC), in alt.comp.os.windows-10, lew
wrote:

On 2018-09-16, Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill
Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul
I checked my update history & see something "funny".

1) 09/12 - cumulative update 1803 = KB4457128) ==========
2) 09/12 - update for flash player 1803 = KB4457146
3) 09/12 - update for 1803 = KB445665
4) 09/13 - cumulative update 1803 = KB4457128 ===========

Guess ms did not think that the cumulative worked??
Or was it a measure twice thinggy?

I had KB4457128 go off twice, too. The first time it installed, it was
very brief and didn't require a restart. It didn't upgrade the version
number, which remained at 17134.254.

The second time it took a lot longer, like a cumulative update normally
should, required a restart, and I ended up with 17134.285.

So maybe something is wonky with that update.

On my laptop, the update went off without a hitch, but it didn't have
KB4346783 already installed. It went straight from 228 to 285.

A KB can be issued more than once, and they have
revision control on them. I would hope the large
one would come first, and the revision 2 would
be a small one correcting the install status of
the first one. If one of them is intended to be
a Servicing Stack update, it should have its own
number.

These two updates were in the space of 10 minutes, and the small one was
the first one.

Something wasn't right with the first install. It didn't install at all.
My build number stayed the same, and didn't increment to from 254 to 285.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten