Liquidation cleaning can damage Windows 10 2004 systems on some devices.

To avoid a concentrated outbreak of bugs during large-scale pushes, Microsoft has adopted a phased push policy for the Windows 10 2020 May Update (Version 2004). Once some serious issues are identified, software giants can promptly block update deployments to some similarly configured devices and then resume push when patches are ready. In some cases, Microsoft can also fix problems with the system’s own troubleshooting tools to avoid frequent involvement in update blocking.

Liquidation cleaning can damage Windows 10 2004 systems on some devices.

A recent example is related to the disk cleanup tool for Windows 10 2004. Serious problems can even cause equipment to be damaged to the point where it does not start.

Unfortunately, Microsoft did not share more details, saying only that “running disk cleanup may result in some devices not being started after the Windows 10 Build 19041.21 update is installed.”

Technically, after installing the Windows 10 2020 May update and the 19041.21 internal compilation version for Insider testers, disk cleanup usually starts automatically, resulting in some devices not being able to start again.

There has been speculation that the bug may have mistakenly deleted or broken some important Windows 10 system files, but this has not yet been officially confirmed.

Instead of upgrading to solve this problem, however, Microsoft has provided a troubleshooter specifically for disk cleanup tools that are now enabled and automatically launched on Windows 10 devices.

Essentially, the troubleshooter does simply disable the automatic start of the disk cleanup tool to prevent accidental file deletion seisluded above. The device will not be released again until the 19041.84 update is installed.

Interestingly, the troubleshooter cannot be started manually. Microsoft only provides users with a dedicated screen interface to determine whether the troubleshooter has started and will only run automatically when the above-mentioned issues affect the device.

The troubleshooter will run automatically twice, first on all devices with the 19041.21 compilation version, and then again after upgrading to the 19041.84 compiled version.

If you are not sure if it has been performed, check the troubleshooting history in the system by in “Start – – – – Update and Security – – . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Currently, Windows 10 2004 is still deployed on a limited number of devices, and more comprehensive pushes are expected later this summer. Can’t wait for friends to get a new version of the installation image through the media creation tool.