Windows 10 · 21H2 · Release · Security update (Patch Tuesday)

Feature update to Windows 10, version 21H2 (19044.7663)

Windows 10 21H2: Servicing ended

Download amd64 — build 19044.7663 from UUP Dump, opens in a new tab Download arm64 — build 19044.7663 from UUP Dump, opens in a new tab Download x86 — build 19044.7663 from UUP Dump, opens in a new tab All 21H2 builds JSON — this build from the builds API

AI summary

This Windows 10 21H2 feature update delivers performance and reliability improvements, strengthened security protections, and fixes for known system issues. (learn.microsoft.com)

Generated from the package's release notes and forum coverage. Verify against Microsoft's release-health page before acting on it.

Microsoft's known issues — KB5120249

  • Issue Known issue Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update. This issue only affects a limited number of systems in which ALL the following conditions are true. These conditions are unlikely to be found on personal devices not managed by IT departments. BitLocker is enabled on the OS drive. The Group Policy " Configure TPM platform validation profile for native UEFI firmware configurations " is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually). System Information ( msinfo32.exe ) reports Secure Boot State PCR7 Binding Workaround: A resolution for this issue is planned in a future Windows update. To work around this issue, remove the Group Policy configuration before installing the update. To do this, follow these steps: Open Group Policy Editor (gpedit.msc) or your Group Policy Management Console. Navigate to Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives . Set "Configure TPM platform validation profile for native UEFI firmware configurations" to Not Configured . Run the following command on affected devices to propagate the policy change: `gpupdate /force` Run the following command to suspend BitLocker (if BitLocker is enabled on the C: d

Microsoft's release notes for KB5120249 ›

Known issues — reported on the forum

No problems reported on the forum for this build yet. Threads that name 19044.7663 or KB5120249 and describe a fault appear here automatically.

In the news

Discussed on the forum

No member thread names 19044.7663 yet.

Search the forum for 19044.7663 Ask about this build