3175x175(CURRENT).thumb.jpg.b05acc060982b36f5891ba728e6d953c.jpg)
It's the second Tuesday of the month which means it's Patch Tuesday time again. As such, today Microsoft is rolling out the monthly security update for February 2022 (also called "B release") on Windows 10 for the latest versions, 20H2, 21H1, and 21H2. The new updates are being distributed under KB5012599, bumping up the builds to 19042.1645, 19043.1645, and 19044.1645.
You can find standalone links to download the new update on Microsoft Update Catalog at this link here.
The major highlight of the release is security updates for Windows 10 and as is generally the case, the Redmond company has also listed the known issues in the update, which is always handy. Here are the symptoms and their respective workarounds:
| Symptom | Workaround |
|---|---|
|
Devices with Windows installations
Note Devices that connect directly to
|
To avoid this issue, be sure to first slipstream
If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
|
|
After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".
|
For more information and a workaround, see KB5005322.
|
|
After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red.
|
This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to non-managed personal devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy linked below.
Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.
Group Policy installation files:
Important Verify that you are using the correct Group Policy for your version of Windows.
|
Some of the older Windows 10 versions have also received updates today which have been listed below with their respective release notes (KB) linked as well as links to download them at Microsoft's Update Catalog.
| Version | KB | Build | Download | Support |
|---|---|---|---|---|
| 1909 |
|
18363.2212
|
Update Catalog | Enterprise, Enterprise and Education, IoT Enterprise |
| 1809 |
|
17763.2803
|
Update Catalog |
Long Term Servicing Channel (LTSC)
|
| 1607 |
|
14393.5066
|
Update Catalog | |
| 1507 |
|
10240.19265
|
Update Catalog |
While not Windows 10, Microsoft has also released updates for Windows Server 2022 under KB5012604.
Windows 10 Patch Tuesday (KB5012599) is out — here's what's new and what's broken
Recommended Comments
There are no comments to display.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.