The next-next version of Windows 10, code named 20H1, known colloquially as 2003, may arrive in December 2019

Topic

New Reply

Just when you thought the pace of unnecessary changes in Windows was receding…. Now comes word from Zac Bowden at Windows Central that the version o
[See the full post at: The next-next version of Windows 10, code named 20H1, known colloquially as 2003, may arrive in December 2019]

1 user thanked author for this post.

Reply | Quote

Replies

This madness has got to STOP !! I’m constantly fixing things that MS breaks each and every time we have a new buggy feature update.

1 user thanked author for this post.

Zaphyrus

Reply | Quote

Yet people and some here likes to claim that “Nothing is wrong with windows” with their only proof being “everything is okay in my computer/computers/systems”

Just someone who don't want Windows to mess with its computer.

Reply | Quote

What other proof could they have?

Reply | Quote

Does finalize or RTM mean the same as arrive or GA?

Reply | Quote

Excellent question.

Based on Zac’s Twitter responses and the update you posted below, he’s betting that 20H1 will hit “RTM” (not clear what that means any more) in late December, and be available to anyone who wants it then, likely through the Insider Release Preview ring.

When will it hit full distribution? Who knows.

What seems clear at this point is that 20H1 contains very, very few improvements that most people will want.

1 user thanked author for this post.

WildBill

Reply | Quote

Update October 29, 2019: I’m hearing that Microsoft intends to get the RTM build out to Insiders in the Slow ring before the end of December, likely the week after the RTM build is compiled. It’ll then go to the Release Preview ring in January, before being released officially to the public in March/April. So Microsoft still intends to ship these updates in the spring and fall, it’s just that they are finished much earlier.
https://www.windowscentral.com/windows-10-os-development-schedule-changes

1 user thanked author for this post.

warrenrumak

Reply | Quote

b wrote:

Update October 29, 2019: I’m hearing that Microsoft intends to get the RTM build out to Insiders in the Slow ring before the end of December, likely the week after the RTM build is compiled. It’ll then go to the Release Preview ring in January, before being released officially to the public in March/April. So Microsoft still intends to ship these updates in the spring and fall, it’s just that they are finished much earlier.
https://www.windowscentral.com/windows-10-os-development-schedule-changes

That actually means MORE beta testing before more advanced users get their hands on it. Which is not a bad thing (for me).

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 hope Bowden’s wrong… but if he isn’t, Win10 20H1 AKA 1912 AKA Vibranium is being rushed to fit with Azure. Rushing usually means killer bugs… & I sooo wanted 1909 to be just a bump in the road that I could wait 3-4 months for. Well, 1909 hits on 11/12/19 AKA November Patch Tuesday. As I replied on Woody’s tweet about this, I think “Bowden’s hedging his bets; RTM is supposedly 1912, but he hints users won’t see it until 1st Quarter 2020.”

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

I really don’t see how it’s “rushing” if they finalize new feature development in December, but don’t release it until March or April.

The first 20H1 build was back in early February, so we’re talking 10 months of new feature development time, followed by 3+ months of testing.  That’s longer than normal.

 

 

 

2 users thanked author for this post.

WildBill, b

Reply | Quote

Sure. Why not to implement another half-baked version, if old ones are still not debugged. 1903 is ready for bussiness and two other are on their way. I feel sorry for MS programmers.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

2 users thanked author for this post.

Carl D, woody

Reply | Quote

I also feel sorry for the admins who have to live through this ridiculous pace over and over again.

1 user thanked author for this post.

Carl D

Reply | Quote

Yes, I think the MS programmers are the ones we should feel the least sorry for.

In fact, we shouldn’t feel sorry for them at all. While they’re busy churning out the constant ‘cosmetic’ changes and mostly useless additions (i.e. stuff that most people wouldn’t want and would probably never use) to Windows 10 at least they’re “gainfully employed”.

The MS programmers might be out of a job otherwise.

 

Reply | Quote

Raise your hand if you’re sick of all these code names. For me it goes back to all those processor code names which I could never get straight. And to add to the confusion, who the heck came up with “2003”? 

Red Ruffnsore

2 users thanked author for this post.

Microfix, Carl D

Reply | Quote

‘Windows server 2003’..oh blast, it’s already been used.

Windows - commercial by definition and now function...

Reply | Quote

Woody came up with “2003” himself, kind of as a joke.

 

2 users thanked author for this post.

WildBill, woody

Reply | Quote

Given this unrelenting release schedule, we will likely never, ever have a stable version of Windows 10!  I’m still on 1809, waiting for 1903 to stabilize (not happening!!), and now 1909 is about to drop…with yet another “feature” update waiting in the wings.  The logic of this is truly beyond my comprehension.

Reply | Quote

At least thay can now mark it as version 2001 or 2002, to avoid server 2003

Reply | Quote

[_Reassigned Account]

Just wonder if Microsoft is trying to bake in Edge Chromium into 20H1? Is this why they are trying to push out the upgrade early? I mean Edge original is floundering and with Windows 7 going away or going into enterprise extended support. Businesses may want new Edge to be in final release by January.

• This reply was modified 5 years, 6 months ago by _Reassigned Account.

1 user thanked author for this post.

WildBill

Reply | Quote

Microsoft’s Chromium-based Edge browser to be generally available January 15, 2020

Reply | Quote

Edge will be the default browser for Windows 10 but will be on its own release schedule. The release schedule pace will be similar to Chrom, Firefox, Opera, etc.

--Joe

Reply | Quote