Windows 11 update that broke Safe Mode is now fixed

Windows 11 ran into some serious issues with Safe Mode due to a nasty bug in a recently rolled out preview update, but the good news is that this problem has now been fixed – and you should already have the fix.

This bug was caused by the recent preview update for Windows 11, patch KB5012643, which was an optional update for those who wanted early access to all of the fixes planned for the May patch series.

As Windows Latest reports, after installing the update, some Windows 11 users took to Microsoft’s Feedback Hub (and elsewhere online) to report issues with Safe Mode, namely that the screen flickers.

In fact, the flickering effect was so bad for those affected by the bug that it rendered safe mode more or less unusable, so it’s no surprise that this is a priority fix. for Microsoft.

As Microsoft informed us in a support document, the problem occurred when users chose to enter “safe mode without networking”, and the company has already rolled out the fix which, fortunately, is automatically applied – there is no need to reinstall the update or go to other lengths.


Analysis: preview updates are optional for a reason

If you’re fetching preview updates, you can expect to encounter gremlins from time to time – that’s just the nature of beta software. The idea is to identify issues and fix them before the full release, although it’s true that the issues that crop up are usually more minor.

Keep this in mind whenever you grab an optional update for Windows 11 (or Windows 10), and that’s why most people will give it a thumbs up and wait for the fully completed release next month – unless the patch fixes a particularly annoying bug. they are already suffering at the hands of (which changes the risk-reward balance, of course).

In the case of KB5012643, not only did we see this issue, but there was also a major issue that was causing extremely long boot times for some systems.

The good news with this safe mode bug is that it was quickly fixed by Microsoft using a “known restore issue”, although it will take some time to filter its way to Windows 11 machines. .

Note that you should already have the fix, but Microsoft advises those still benefiting from the restore that “restarting your device may help the fix apply to your device faster” (plus other tips for users professionals are given in the aforementioned supporting document).

Leave a Comment