To correct a patch, Microsoft releases a Windows update.
In order to address a few vulnerabilities it unintentionally introduced through a routine Windows update, Microsoft has produced an emergency upgrade.
The organisation published KB5014697 on June 14; it is a cumulative update that fixes several well-known Windows problems. However, the patch also created fresh vulnerabilities, specifically problems with Azure Active Directory sign-in and Microsoft 365 on Arm-powered devices.
In addition, the patch prevented some devices from using the Wi-Fi hotspot feature and caused some.NET apps to not launch.
The problem is now fixed for Windows 10 and Windows 11 devices by the out-of-band (OOB) update. It was stated that customers could manually download and install it via the Update Catalog in addition to having it automatically downloaded and installed by Windows Update.
Remedies and protections
Microsoft stated in its advisory that the fix “addresses a known issue that only affects Windows Arm-based systems and can prevent you from signing in using Azure Active Directory (AAD)” (opens in new tab). VPN connections, Microsoft Teams, and Microsoft Outlook are just a few examples of the apps and services that could be impacted.
Three versions of Windows 10 (21H2, 21H1, and 20H2) and one version of Windows 11 (21H2) both have fixes.
“This cumulative OOB upgrade. We advise installing this OOB update rather than the June 14, 2022 security update if you are using updates that were released before that date “The business goes on to clarify. Only the new updates contained in this package will be downloaded to and installed on your device if you have already installed earlier updates.
System administrators who are unable to patch that quickly might, as usual, use a workaround by switching to some of the programmes’ web versions.
Microsoft advised using the web versions of the affected apps, including OneDrive, Microsoft Teams, and Outlook.com, to reduce the problem.
Microsoft recommended disabling the Wi-Fi hotspot capability for Wi-Fi troubles while re-enabling the.NET Framework tool for problems with the latter.