[German]After releasing the Windows 10 May 2021 Update (21H1), in the middle of last month (see Windows 10 May 2021 Update (21H1) released (May 18, 2021)), Microsoft is opening the floodgates. The operating system is now to be distributed more widely, but also more intelligently to compatible machines. Microsoft has just announced this on the status page.
Advertising
Windows 10 May 2021 Update (21H1)
The Windows 10 May 2021 Update internally carries the version designation 21H1, and is the first feature update for 2021. The feature update is intentionally designed to deliver key features that improve security, remote access, and quality. Distributed, this update will only be available for select devices running Windows 10, version 2004 or later.
Windows 10 21H1, similar to Windows 10 version 1903/1909 and Windows 10 version 2004/20H2, will be rolled out only as a minor feature update for the old 2004 and 20H2 versions. For this purpose, the changes are already prepared in the existing Windows 10 versions 2004 and 20H2 via monthly updates. For the release, only the few KByte Enablement Update KB500073 is required via Windows Update or WSUS. However, this will only be offered on suitable machines and will not be available via the Microsoft Update Catalog.
Interested users could open the Windows Update settings page on Windows 10 2004 and 20H2 (Settings > Update & Security > Windows Update) and select the Check for Updates button there. If the update appears, select the "Download and Install" hyperlink to start the installation. This approach was intended for "early birds" who didn't want to wait. Generally, Microsoft distributes its feature updates in waves so that not too many users are affected by bugs.
Rollout with machine learning (ML) phase started
In the status area of Windows 10 version 21H1, Microsoft has announced the next stage of the rollout on June 2, 2021. Although it still states there:
Windows 10 version 21H1 is available to users with devices running Windows 10, version 20H2 and version 2004 who manually select "Check for Updates" via Windows Update (nothing has changed here). The recommended maintenance status is "Semi-Annual Channel".
Advertising
But it also says that Microsoft has now begun the first phase of the rollout for machine learning (ML) training. In this phase, the feature update will be offered to devices running Windows 10 version 2004 when searching on compatible devices. The machine learning (ML) model is then trained to detect problems and stop the rollout if necessary. The goal is to automatically update compatible machines to Windows 10 version 21H1 later. Microsoft continues to train machine learning algorithms throughout all phases of the staged rollout. This rollout in waves, after all, has been in use for many years, and machine learning is also used to detect deployment issues early and suspend delivery on incompatible machines.
Similar articles:
Windows 10 May 2021 Update (21H1) released (May 18, 2021)
Windows 10 Version 2004/20H2: Audio issue "high-pitched noise" after Update
Windows 10 21H1: StrangeTaskbar issues after update KB5003214
Windows 10 21H1 reports ReleaseID 2009
Advertising
If there is one thing I have learned with Windows 10 in the past few years, it is to open a command window with admin privileges and run 'sfc /scannow' BEFORE letting Microsoft updates run.
Doing that as a precaution would save much anguish for users. If only Microsoft would automate the system scan process by routinely checking if it is necessary (and then running sfc /scannow if it is necessary), many fewer Patch Tuesday disasters would occur.
Maybe if Windows 10 ran a repair process in the backgound, that could keep watch for disruptive system errors and fix them before serious damage results.
It is a no brainer to me but obviously not to Mr Nadella and his crew.
Carry on the good work Herr Born. Your website is the most valuable asset to people like me who month after month endeavour to keep the Windows systems of friends and relatives working safely and reliably.
These problems do not occur on the systems I use but I guess that such things as improper shutdowns, for example, likely cause the system files to be disrupted and so require repair with System File Checker.