NewsWindows 11

Windows 11: New update KB5016691 will block you from logging in, but there’s a fix

A Windows update issued last month is blocking some users with new Microsoft accounts from being able to log into their systems, a glitch Microsoft says can be remedied either through a workaround or a feature introduced to the operating system last year.


Windows 11 users have been put on alert about a recent update that’s been released by Microsoft. At the end of August, the KB5016691 patch was pushed out to millions of PCs and was meant to address a number of niggling issues such as problems with USB printing, Bluetooth headsets and the Microsoft Store. However, while this patch fixed some gremlins it also introduced another one, as it could cause Windows 11 users to be locked out of their laptops.


The recent Windows 11 update sparked a bug which meant anyone logging in to the OS via a new Microsoft account could have had trouble signing in

Speaking about the problem in a recent advisory, the Redmond-based tech giant said: “After installing KB5016691 and adding a new Microsoft account user in Windows, you might be unable to sign in for a brief time after the first restart or sign out. The issue only affects the newly added Microsoft account user and only for the first sign in.

“This issue only affects devices after adding a Microsoft account.”

The Ultimate Guide to Installing Windows 11 from a USB drive

The Windows 10 and 11 makers said the problem has now been resolved, with the issue addressed via Known Issue Rollback (KIR).

This is a Windows servicing tool which makes sure a non-security bug can be quickly fixed.

Windows 11 users looking to get these fixes don’t even need to download any patches, as the fix can be deployed when you reboot your PC.

Explaining how this feature works, Microsoft in a blog post said: “When Microsoft decides to rollback a bug fix in an update because of a known issue, we make a configuration change in the cloud. Devices connected to Windows Update or Windows Update for Business are notified of this change and it takes effect with the next reboot.

“Once this happens, the Know Issue Rollback infrastructure will start reporting that the fix – the new code that has a problem – is no longer enabled. From this point on, the OS will fall back to the previous code that had a bug albeit a much more benign issue than the new code that has a problem.

“While these devices would still require a reboot, in most cases we have identified and published a rollback before most end user devices would have had the chance to even install the update containing the issue. In other words, most end users will never see the regression!”

Microsoft has been using KIR since the end of 2019, with the majority of non-security fixes rolled out via this feature.

Notify of

Inline Feedbacks
View all comments