Windows 11 update blocking some users from logging in

Windows 11 update blocking some users from logging in

Some users with new Microsoft accounts are having trouble logging onto their computers as a result of a Windows update that was released last month. Microsoft claims the problem can be fixed using either a workaround or a feature that was added to the operating system last year.

According to Microsoft, a number of problems with USB printing, trusting programs from the Microsoft Store, Bluetooth headsets, and Microsoft Edge in IE mode were addressed with the update to Windows 11 version 21H2, which was released on August 25.

The KB5016691 upgrade, however, also brought about a new problem. Microsoft stated in an advisory released this week that certain users who installed the update and added a new Microsoft account user to Windows were temporarily unable to sign in after the initial restart or after signing out.

The company stated that "the problem only impacts the newly added Microsoft account user and only for the first sign-in." "Devices only experience this problem after adding a Microsoft account. Accounts for Azure Active Directory users or Active Directory domain users are unaffected."

The world's largest software company provided two solutions. One is a workaround that effectively instructs the OS to resolve the issue on its own.

According to Microsoft, the problem will eventually fix itself if a user with a fresh account is unable to sign in.

In this case, the user will have to wait for the lock screen to reappear before they can log in as normal.

Users can also fix the issue by utilizing the Known Issue Rollback (KIR) feature, which was released in March 2021. Microsoft said that KIR would speedily put a device afflicted by a Windows upgrade back to use in a blog post at the time.

"The Known Issue Rollback infrastructure in the OS provides developers with a method that evaluates a policy to determine the execution path," said Microsoft. "This policy tells the OS whether a fix should remain enabled or not. If the policy states that the fix is enabled, then the new code runs; and if the policy says that the fix is disabled, then the OS falls back to the old code-path."

The old code is disabled by default, and the new code is enabled for monthly Windows updates. If the fix results in a significant issue, Azure hosted services and Windows collaborate to update the device's policy settings and disable the offending remedy.

Microsoft claims that enterprises are in charge of the KIR policy.

KIR may need up to 24 hours to automatically fix the login problem on non-managed corporate devices and consumer systems. According to the provider, restarting the Windows device might speed up the procedure.

"For enterprise-managed devices that have installed an affected update and encountered this issue [admins] can resolve it by installing and configuring a special Group Policy," the company wrote. "The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5016691 220722_051525 Known Issue Rollback -> Windows 11 (original release)."

The Group Policy must be installed and set up by an IT administrator according to the Windows versions being used. Deployments of Windows Server are not impacted by this problem.

Source: TheRegister