Replies

The update has been detected for awhile (on my devices, UpdateOrchestrator would sbow 2 updates but download only 1 for the last few months). So the only thing that appeared to change yesterday is that the update was now acknowledged/downloaded/installed. The intel updates from 2018/19 would be detected but not downloaded for awhile.

I suspect the timing is a 2004 thing where they want the little update (just barely larger than the maximum file size for an attachment on here) to be installed before people start moving to the new version.

while this quote doesn’t directly say “upgraded to 1903”.. it seems more logical to see it as saying “1803ers/etc are going directly to 1903”:

The Windows 10 April 2018 Update (Windows 10, version 1803) will reach end of service on November 12, 2019 for Home and Pro editions. Starting this June, we will begin updating devices running the April 2018 Update, and earlier versions of Windows 10

I think the pace of 1803->1903 upgrades will pickup by the June patch day (June 11th) when people on 1803 will get the “Download and Install Now” option on the update, since a good portion of them who won’t be downloading KB4499183 to get D&IN before then.

So there’ll be a nice reasonable 3 weeks for everything to roll out before they crank up the upgrades. Remember that measurements seem to suggest that more people are on 1803 than 1809.

It seems more complicated then necessary to move 1803 people onto 1809 before moving them to 1903. They had months to move 1803 users to 1809 without 1903 and didn’t.

raises hand

from what I can tell from having it installed for most of the last 2 1/2 months.. it doesn’t do anything, as intended. It’s a dumb little thing that I guess everybody with AMD on 1809 is getting to experience since these updates are baked into 1809.

The weird thing from my experience is that the updates would automatically queue and do nothing, but the last two times they emerged for download involved my internet connection dropping beforehand. Which also means it gets to drop entries in Event Viewer about failing to move towards being staged because it’s trying to stage the update too quickly.

1 user thanked author for this post.

CADesertRat

it arrived automatically for me and it’s listed in the catalog as a Security Update instead of just an “Update” (like other non-patch day updates)

If you’re at risk of being tricked into using IE, you should probably let this download and install.

As someone on 1803, when I saw a folder with files show up in SoftwareDistribution on a Wednesday, I was expecting “automatic 1809 update”, not “security update for 1803”. (Yeah yeah, the 1809 update files probably land somewhere else when they arrive, right?)

It downloaded along with some other updates but didn’t install at first due to the logjam. Then I went to updates, clicked retry, and it installed in 15 seconds and that’s that.

I guess this is today’s indicator that they’re not expanding their web of pushing 1809 today.

My best guess on 4058258 is that the classification for it in the catalog (just “Updates”) means that some won’t have it offered to them automatically, but that the stuff in it will be in the February update next week, which will be a “Security Update” and offered up automatically.

The other updates for 1709 x64 listed as just “updates” have never arrived for me (4051963/4073290), but the cumulatives have always arrived.

Everything is going smoothly here (knockonwood) on 16299.192. We’ll see the 16299.214 devices next week when we all get back on the same number again hopefully.

As somebody with an AMD (A4-5000) and Intel (i5-3337 Ivy Bridge) that hasn’t been hit by the problems that impacted AMD or Intel and have been living peacefully on 16299.192 for a few weeks, I’m not really expecting to get anything. I’ll see soon enough if that’s an accurate prediction.

As someone who had to deal with that update popping up on a W10 recently… I dislike that ‘update’ immensely. The people on 7/8.1 probably have an easier time dealing with that than people on 10.

I probably made a mistake or two in the process, but I eventually just fresh started the computer and haven’t had it pop up in the weeks since then. I’m still sorta left to wonder why that update arrived for me a year after it really got attention on here and other places.

It’s not like getting error 0x80070643 on KB4054517 causes it to start fetching that computer-wrecking junk out of confusion? It was something else in the process, I’m sure.