There’s a reason why your Win10 1803 machine hasn’t been pushed onto 1809

Topic

New Reply

Microsoft gave up. The 1803-to-1809 push pace has gone from slow to glacial. Gregg Keizer has the details on Computerworld: According to AdDuplex, …
[See the full post at: There’s a reason why your Win10 1803 machine hasn’t been pushed onto 1809]

6 users thanked author for this post.

HiFlyer, abbodi86, GreatAndPowerfulTech, Elly, Fred, PhotM

Reply | Quote

Replies

Am I mistaken, or isn’t 1809 the base for LTSC?

If so, how is this going to affect LTSC and server base?

Reply | Quote

Well, yeah, they are going to have to continue fixing the bugs on this branch, given that it has 10 years of support as far as Server 2019 and LTSC go.  We might want to think of 1809 as a “throw away” version, but they have to maintain the source for a long, long time, regardless.

In reality, the problems with 1809 are just a symptom of the far, FAR too rapid pace they have been on with modifying Windows code – with not enough (any?) testing.  1809 has just sort of become a symbol of enough is enough.

Reply | Quote

it won’t affect the LTSB/LTSC folks that much since they can only upgrade to LTSC 2019 (v1809) thru installation media and will not be “forced” into upgrading, meaning they can upgrade anytime they want (yes, even postpone upgrading indefinitely since feature updates are never offered to LTSB/LTSC users)

Reply | Quote

A few users are reporting that 1903 became available for non-Insiders today, presumably for seekers.

Reply | Quote

Where are you seeing this?

Reply | Quote

Yep, I’m dubious too. It turns out that others had installed 1903 from an ISO. And I don’t think I trust the report of a single user who made this claim (as he had earlier failed Insider updates):

Non insider 1809 machine offered 1903 during a WU check along with the other monthly updates

1 user thanked author for this post.

woody

Reply | Quote

Pics or didn’t happen :). That would be quite surprising to say the least.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

I think it didn’t happen. I originally thought there was more than one claimant.

2 users thanked author for this post.

woody, radosuaf

Reply | Quote

He now claims it was offered but failed to install. (I think because he switched off Insider.)

(Apologies for distraction; the range of rings/situations became confusing.)

Reply | Quote

We’ve had one claimant here.

1 user thanked author for this post.

radosuaf

Reply | Quote

Was that definitely via a non-Insider Windows Update check? (Doesn’t appear to say so.)

Reply | Quote

My question is, what does this do for us using deferrals? What flavor of medicine are they going to attempt to serve us? I’d rather go from 1803 to 1809, but if they’re pulling 1809… now what? I don’t want 1903, it’s not ready and it won’t be for probably another 4+ months which is what my deferrals are set as.

Reply | Quote

I don’t think they are pulling it.
I think they are just not PUSHING it.

2 users thanked author for this post.

abbodi86, zero2dash

Reply | Quote

I really, REALLY hope so. (Maybe I’m giving them too much rope.)

Reply | Quote

Putting Win 10 v1903 on VM seems a prudent way to get to know it before “taking the plunge” with important hardware. I can report that it works reasonably well and an in-place upgrade from v1809 went surprisingly smoothly. I can’t say anything about how or where to get the data, except that I got it legally and properly, so please don’t ask.

Win 10 v1809 seems to have somehow gotten a bad name – people are actively avoiding it without strong reason, IMO. From someone who has been using it every day, I can say that it’s actually not been bad at all for professional use (suitably tweaked).

I have a hunch an in-place upgrade from an older version of Win 10 might not be as easy or as tidy as when starting with the immediate predecessor version in good working order. But perhaps those who choose to skip versions are anticipating a full, clean installation in the future. That’s also not a bad way to go.

-Noel

Reply | Quote

Noel, you’d be surprised what upgrading from an older version to newer version can do.  We did two different types of upgrades.  One group from v1511 LTSB to v1709 and another group from v1607 to v1709.  I was surprised at how well it went.  The big thing was that on some of the PCs they had stopped taking patches and after the upgrade they started working like a new machine.
Our next upgrade will most likely be all the boxes upgraded to v1809, but that won’t be for several more months.  We have to make sure everything is stable on our reference machines first.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

Reply | Quote

um Mark, there was no LTSB for v1511 – only v1507 had LTSB before v1607 came out in LTSB form

Reply | Quote

Do not push a 30-month servicing version, in a favor of 18-month servicing version without SAC-T

technicalities 🙂

2 users thanked author for this post.

NetDef, woody

Reply | Quote