Microsoft is now blocking the Windows 11 22H2 update from being offered on some systems because signing in using Windows Hello might not work after upgrading.
As the company explains, customers will experience problems signing in via Windows Hello after installing the Windows 11 2022 Update only on devices that also use Enhanced Sign-in Security.
On impacted systems, the known issue affects both PIN and biometric (face and fingerprint) sign-ins.
“This issue might be encountered on devices which already have Windows Hello when upgrading but should not happen on devices which enable Windows Hello after upgrading or installing Windows 11, version 22H2,” Microsoft said.
Redmond has added a compatibility hold (safeguard ID 40667045) that will prevent the update from being offered and users from upgrading affected systems.
Customers are advised not to manually install the Windows 11 2022 Update on affected systems using the Media Creation Tool or the ‘Update now’ button until this known issue is addressed and the safeguard is removed.
Issue addressed in last month’s preview release
Microsoft has already addressed the issue in the KB5017389 preview cumulative update, and the safeguard hold will likely be removed in mid-October.
A workaround is also available until the fix rolls out to all users, and it requires signing in using the account’s password.
“If you upgraded to Windows 11, version 22H2 and are unable to sign-in using Windows Hello, you can sign-in using the password for your user,” Microsoft added.
Since the Windows 11 2022 Update was released, Microsoft has added two other compatibility holds to block the upgrade from being offered on some systems due to blue screens and printer issues.
The company also confirmed that the upgrade is also breaking provisioning, leaving Windows 11 endpoints partially configured and failing to finish installing, and comes with a significant performance hit when copying large files over SMB.
Windows 11 22H2 is now available to all seekers on eligible devices since entering a new deployment phase on Tuesday, October 4.
Source: www.bleepingcomputer.com