Atti Abderrahim
Table of Contents
A recent Windows 11 update, build 26120.1542 (KB5041872), intended to bring changes to widget placement on the taskbar and fix various instabilities, is causing significant issues for some users. However, the good news is that this bug currently affects only a minority of users who are part of the Windows Insider Program.
A Buggy Release Right Out of the Gate
Shortly after its release, the windows 11 build 26120.1542 update has been reported to have severe issues. Many users in the dev channel of the Windows Insider Program are finding that the update is struggling to download on a large number of devices. In some cases, it even pushes CPU usage to its limits, causing the entire PC to crash. The update often gets stuck at 8% download progress, with the CPU locked at 100%, leading to frequent failures.
Indefinite Waiting Period
Frustrated users have taken to the Microsoft forum, voicing their concerns about the cumulative Windows 11 update that seems to be causing crashes before it even finishes installing. For now, the only viable solution appears to be restarting the affected computers to pause the problematic download. Users are strongly advised against attempting to reinstall the KB5041872 update, as this could lead to further complications.
Temporary Workarounds While Awaiting an Official Patch
In the midst of this experimental chaos, a potential workaround has been found. One user suggests that the high CPU usage is related to the TiWorker.exe service (Windows Update Trusted Installer Worker Process). By stopping this process and reinstalling the KB5041872 build offline (using the *.msu file from the Microsoft update catalog), the dual problem of downloading issues and excessive CPU usage was reportedly resolved after restarting the PC and manually checking for updates via Windows Update.
Other users have also managed to overcome these problems by uninstalling the KB5041872 (windows 11 security update) and KB5037898 (feature update) builds. After uninstalling, they then reinstalled them properly through windows 11 Update, eventually obtaining a stable version of the KB5041872 update.
Waiting for an Official Response
Microsoft was informed of these issues at the end of August but has yet to issue any official response. If you lack the time or patience to perform a rollback or attempt manual workarounds, it may be best to hold off on downloading this problematic update until further notice.
Sources : Communauté Microsoft, Neowin
