Go to ...

RSS Feed

April 6, 2020

1809 Users: Get Ready for 1909 Updates!

OK, then: it’s official. MS announced yesterday — December 5, 2019 — that it will now automatically initiate updates to 1909 for users still running 1809. We’ve known this was coming, because EOL for was originally scheduled for May 11, 2020. Here’s the text verbatim from the Windows 10 1909 Status Page (see text outlined in red):

1809 Users: Get Ready for 1909 Updates.statusinfo

Plenty of time for a smooth (or not-so-smooth) update process, indeed. Ready or not, here it comes!
[Click image for full-sized view]

Prepping for Migration/Upgrade

Commercial or business users on 1809 should probably start working 1909 over in their test labs to look for potential issues or gotchas. LTSB (Long Term Service Branch) and LTSC (Long-Term Servicing Channel) do have longer time horizons, but the end of mainstream support is coming for older LTSC versions,too. For Windows 10 Enterprise and IoT Enterprise 2016 LTSB, that date is October 12, 2021; for Windows 10 Enterprise and IoT Enterprise 2015 LTSB, it’s October 13, 2020.

So even if you’ve opted into the long term service options that MS makes available, it’s definitely time for those on the 2015 release to start migration planning and analysis. Likewise, it’s smart for those on the 2016 release to follow suit, though perhaps without the same sense of immediacy or urgency. Here’s that info, from the Windows Lifecycle Fact Sheet:

1809 Users: Get Ready for 1909 Updates.long-term

Surprisingly, time is running out on the 2015 LTSB (and ultimately, also its 2016 successor).
[Click image for full-sized view.]

Ultimately, it looks like all Windows 10 roads will lead to an upgrade of some kind. The forthcoming 20H1 Feature Upgrade promises to be pretty significant, so it may also be worthwhile for admins to field some Fast or Slow ring Insider Previews in their test labs as well. I’ve been working with those Builds since they started showing up early this year and they are now incredibly stable. That’s because MS is reworking its release cycles to field a “mostly stable” release of 20H1 before this month ends (that is, before the end of 2019). It can then use that release as the basis for Enterprise, IoT, Azure VMs, and other Windows OS code bases.

Author: Ed Tittel

Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.

Leave a Reply

More Stories From 19H2