An important update is being applied to Windows 10 to fix a bug that caused Windows Explorer to hang when looking for files from the search box According to Windows Latest, this very annoying bug first appeared in November 2019 and Since then, there has been a significant delay in getting it fixed.

The issue was quite large and managed to bring Windows Explorer to a halt, preventing users from doing simple things like clicking. And Microsoft admits that the filter tool stopped working, leaving either a blank page or a "calculating filter" message displayed indefinitely.

This bug has also been fixed in Windows 10 21H1, which will be distributed in the coming months. However, this patch brings this component slightly forward, which will please those who do not want to wait to be able to launch Explorer again.

The update also removes the creaky old original version of Microsoft Edge. The browser received an update in January 2020, moving to a Chromium-based platform. However, Microsoft allowed the original Edge, which ran on its own rendering engine, to remain in case someone was using it.

The update, KB5000842, provides a patch that removes Explorer bugs and old Edge code. Additional fixes include an update to stop HDR screens from appearing darker than expected. The patch also addresses a video playback bug that causes synchronization problems when a computer is duplicating a display on multiple monitors. It also fixes several 7.1 sound issues.

Microsoft warns that if a custom offline ISO is built for a Windows installation, the legacy Edge may not be replaced by the new version when it is removed. While this could be a problem for a theoretical person who had only legacy Edge installed, it is highly unlikely to be a problem in the real world. It may be an issue for some companies using machines that do not use Windows Update for patching.

The patch is available through Windows Update and can be installed by selecting the appropriate cumulative update from the Windows Update menu. If you do not do this manually, you will have to wait for the 21H2 update, which is scheduled for a few months later.

Update: This bug was reported in 2019, not 2020 as originally reported.