Windows 10 V1809: Auto Update to Version 2004 has begun?

[German]It appears that Microsoft has now begun preparations to force systems running Windows 10 version 1809 Home and Pro to update to the Windows 10 May 2020 Update (version 2004).


Advertising

End of Life for Windows 10 Version 1809

The Windows 10 Oktober 2018 Update (Version 1809) was released in the fall of 2018 and has actually reached the end of life in the consumer editions Home and Pro, that is, the end of support support with updates. I had reported in February 2020 within the blog post Windows 10 Version 1809 reaches End of Life soon about this.

At that time there was Microsoft support article 4541558 dated 12 February 2020, which referred to the end of support. According to the information sheet on the life cycle of Windows, Windows 10 version 1809 will reach the 18-month service end on 12 May 2020.

Windows 10 Life Cycle

This applies to the Windows 10 variants listed in the table above, which, by the way, were first released in October 2018, but then withdrawn again. In contrast, Windows 10 Enterprise and Windows 10 Enterprise Education, which are intended for enterprise use, will receive 30 months of support and will be supported until May 11, 2021. Once the end-of-life date is reached, versions no longer receive updates and are forced to be updated to the next Windows 10 build via Functional Update.

However, in view of the Corona Pandemic, Microsoft decided to extend the support periods for Windows 10 version 1809 – and Windows 10 version 1709 in the enterprise environment by six months. I had mentioned this in the blog posts Support extension for Windows 10 V1809 until Nov. 2020 and Windows 10 Version 1709: Support extended till October 2020.


Advertising

Forced Upgrade from version 1809 to 2004?

Normally, Microsoft offers feature upgrades to a new Windows version as optional in the settings under Windows Update. The upgrade has to be initiated manually via a hyperlink to download and install the software (see screenshot).

Funktionsupdates ab Windows 10 Mai 2019 Update
(Upgrade to Windows 10 Mai 2019 Update, Click to size)

Last November, I described the situation with Windows 10 version 1803 in the article Forced update from Windows 10 V1803 to V1903? – that’s where the above screenshot comes from.

Bleeping Computer reported here, that Microsoft plans to force rollout the Windows 10 May 2020 Update (2004 version) for devices that reach the end of support. The basis is a tweet from the Windows Update Social Media Team:

In the Windows 10 version 2004 status dashboard, Microsoft has added the following statement on June 16, 2020.  Windows 10 Version 2004-Statusbereich hat Microsoft zum 16. Juni 2020 dazu folgende Erklärung eingefügt.

Current status as of June 16, 2020

Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909, who manually seek to “Check for updates” via Windows Update. We are continuing our phased approach on initial availability, as we listen, learn, and adjust. Today we are slowly beginning the training of our machine learning (ML) based process used to intelligently select and automatically update devices approaching end of service. The recommended servicing status is Semi-Annual Channel.

On my test machine I receive the following notification, that it is not ready to be upgraded to version 2004.

Windows 10 Version 2004 nicht bereit

Regarding the forced upgrade, it should also be noted that in the Windows 10 version 2004 status dashboard, numerous bugs are still listed as ‘Investigating’. And here I’m blogging daily about fat bugs in Windows 10 Version 2004. Any of you who have been forced to update with Windows 10 version 1809? 

Similar articles:
Forced update from Windows 10 V1803 to V1903?
Support extension for Windows 10 V1809 until Nov. 2020
Windows 10 Version 1709: Support extended till October 2020

Windows 10 2004: Storage Spaces issues
Windows 10 Version 2004: Issues with Malwarebytes 4.1.0?
Windows 10 version 2004 annoys Chrome users
Windows 10 v2004 breaks Fresh Start
Windows 10 Version 2004/Windows Server 2004 released
Windows 10 Version 2004: Deprecated/removed features
Windows 10 version 2004: Graphics issues with multi monitor and f.lux
Windows 10 2004: ADMX templates available
Windows 10 Version 2004: External display turns black
Windows 10 Version 2004: Issues with DVBViewer drivers
Windows 10 2004: Upgrade fail due to drive letter on boot partition
Windows 10 Version 2004: Issue with Optane Systems
Windows 10 V2004: Office365 Sync issues with iCloud
Windows 10 V2004: Downloads removed from disk cleanup
Windows 10 Version 2004: Forced upgrade without user consent
Windows 10 Version 2004 Upgrade Issues with Surfaces
Upgrade Block to Windows 10 2004 for devices with Core isolation (HVCI)
Windows 10 2004: Bug defragments SSDs too often


Advertising


This entry was posted in Update, Windows and tagged , . Bookmark the permalink.

2 Responses to Windows 10 V1809: Auto Update to Version 2004 has begun?

  1. Chris Pugson says:

    Does Microsoft care about the huge damage to its reputation that it is inflicting on itself by forcing bug infested new feature updates on users? Feature Update 2004 was released in spite of including a known unfixed bug which can damage SSDs.

    Microsoft has a effective monopoly of PC operating systems and software. What incentive is there for it to improve its increasingly unacceptably poor standards?

  2. JohnIL says:

    Yes of course let’s force you to upgrade to 2004 because that version is so good and way better than that old 1809 or 1903. Microsoft had even more time to work on 2004 and its still bad. Not only that but you have users willing to downgrade back to Windows 7 and accept that its unsupported over running any version of Windows 10. That to me says volumes about how bad Windows 10 is for some users. I would not go to those extremes myself, I have not had the major issues some have had with Windows 10. But I acknowledge that its been a very rocky 5 plus years of it. Not a chance I would install 2004 version in any scenario right now.

Leave a Reply

Your email address will not be published. Required fields are marked *