Windows 10 22H2 build 19045.7663 (KB5120249) — release notes, downloads, known issues

• 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 ›

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

• Coverage KB5120249 Updates Windows 10 ESU to Build 19045.7663 Aug 11, 2026 · names this build

No member thread names 19045.7663 yet.

Search the forum for 19045.7663 Ask about this build