Win10 Update breaks Internet connection.

[Diggs]

FYI - Be aware of another Win10 Update bug that breaks an Internet connection. No current fix from Microsoft but a quick registry hack may fix the problem. It's being reported in several places but here's a link -

https://www.techradar.com/news/wind...rnet-connectivity-for-some-and-causes-deja-vu

 

[GTP]

Many of my clients have updated to the latest 2004 build. I've had zero problems and clients have reported no issues either.
This will be handy if they do, thanks.

 

[Sky-Knight]

I've still got a bucket of gear that "isn't ready" for 2004, so most of my junk is on 1909 still.

 

[SAFCasper]

We decided to keep internal systems and managed clients on 1909 until a direct upgrade to 2009 (or 20H2 with the new naming scheme).

Microsoft are going with the Major-Minor update cycle again this year. 2004 was the major update with new features while 2009 will be a minor update of mostly bug fixes and optimizations. The same way 1909 was a minor upgrade from 1903.

I have upgraded 3 personal devices to 2004 without any issues.

 

[britechguy]

We decided to keep internal systems and managed clients on 1909 until a direct upgrade to 2009 (or 20H2 with the new naming scheme).

There is no new naming scheme. What is 2004 was 20H1 while under development. All of the development versions, pre-release, are and have been YYH1 and YYH2, respectively, at least for a while now.

All of the computers in my household have been deemed "not quite ready" and I know of a couple of people who had been offered the Download and install link that had the machines later change to "not quite ready." This is not at all surprising, as issues can be identified with specific hardware via telemetry during the rollout process that had not, as yet, been identified earlier, so the readiness status of a piece of hardware can change if anything on it is determined to be potentially problematic during the phased rollout.

 

[SAFCasper]

There is no new naming scheme. What is 2004 was 20H1 while under development. All of the development versions, pre-release, are and have been YYH1 and YYH2, respectively, at least for a while now.

It was changed last month.

"With this release, we will also simplify our approach to numerical versions for Windows and move to a format that represents the half of the calendar year in which the release becomes available in retail and commercial channels. Windows 10, version 20H2 is, therefore, “20H2” because it will be released in the second half of the 2020 calendar year. This is a familiar approach for our Windows Insiders and is designed to provide consistency in our version names across releases for our commercial customers and partners. (Note: We will continue to use a friendly name, such as the May 2020 Update, in consumer communications.)"

https://blogs.windows.com/windowsexperience/2020/06/16/whats-next-for-windows-10-updates/

 

[Sky-Knight]

HAHA it also gives them a bit of a pass when they call something say 2004, but release it in MAY!

 

[SAFCasper]

HAHA it also gives them a bit of a pass when they call something say 2004, but release it in MAY!

Double points when it should have been named 2003 under normal conventions but they wanted to avoid confusion with Server 2003. Gave themselves and extra month and still missed the deadline!

 

[britechguy]

@SAFCasper,

Thanks very much, as I'd somehow missed that announcement. I am very glad that they are finally dropping the MM part of the releases for the very reason @Sky-Knight mentions. I can't remember the last time the actual MM of release matches the MM designation in the release number!