On Fri, 15 Mar 2019 02:31:15 -0400, Paul
wrote:

Eric Stevens wrote:
On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.
That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379

I've got one machine still on 1803. MS does not seem to want to offer
it 1809.

In the Settings Wheel : Update and Security, what does
the Windows Update History tab show ? Does it show an update
which is failed, and blocks other updates ? You can have
a "log jam", where WU is trying to get some older update
to install, and this prevents 1809 from being considered.

!803 is all it knows about. There is no evidence of problems with
updates. It hasn't been used much for several weeks and when I started
it up to read its history it gave me a list of three updates for 1803
which it is right now downloading and going to install. There was no
mention of 1809. I'll wait to see what the future holds.

If you get the failed update (which is not followed by any
success entry with the same number), then you can go to
catalog.update.microsoft.com and get the MSU for that KB
via manual download. Double click it and install it.

There is usually sufficient logic (and wsusscn content) for
an MSU to figure out whether it's relevant or not. I've never
seen a case where trying to use an MSU caused a problem.

I found the "need to install 1809" was pretty aggressive
a couple days ago, and an install I didn't particularly want
updated, started to update on this machine. The cleanup
behavior is there, to "move on to the next thing".

If you've been messing around with "streams" and using the
Long Term business stream (whatever that's called today",
maybe you could break it that way. Also, in the past,
if you manually reverted the OS version (made the OS
loot C:\Windows.old and put things back), that also
functions as a "manual barrier" to upgrading. And running
a Repair Install by executing Setup.exe might be the simplest
way to move forward again.

By knowing things you've done to the OS along the way,
there may be some hint as to why.

I've also noticed, that a number of items referenced by
people on the web, concerning the Registry, and ways to
control this behavior, don't actually work. And a ton of
stuff that worked at one time, is just left there as
a "grave yard" of registry entries. Even if you did find
some registry entries that didn't match what it told
you to do on the web, it could be the OS isn't even paying
attention to those now. I used to look at those, when the
Insider Edition threw a wobbly, and fiddling that stuff as
instructed, didn't do a thing. The Insider is constantly doing
Upgrades, and is an excellent test vehicle for such.

Paul
--

Regards,

Eric Stevens