Patch tracker / KB5099540
KB5099540: Windows Server 2022 Security Update (July 2026)
KB5099540 is a Critical security update for Windows Server 2022, released 2026-07-14. It closes 327 CVEs with a maximum CVSS of 9.9. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. It is the fourth largest of the 61 updates Microsoft shipped that month, by CVEs closed.
Update summary
Fixes 327 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.9 (Critical). EPSS exploit probability up to 4.9%. Among the top half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows Server 2022 has shipped since this one: KB5126655 (2026-10-13). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 2 known issues with this update.
- Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
- Windows Server Update Services (WSUS) does not display error details
KB5099540 is a large July 2026 rollup for Windows 10 version 1809 and Windows Server 2019 that fixes 325 CVEs, with the worst rated Critical at CVSS 9.9 and at least one CVE already listed in the CISA Known Exploited Vulnerabilities catalog. The confirmed exploitation matters more than the modest 11% top EPSS here, since KEV listing means attacks are observed in the wild rather than merely predicted. Server 2019 domain controllers and any remaining 1809 endpoints are the exposed population.
Do this: Deploy KB5099540 to your Windows Server 2019 and 1809 systems now, prioritizing internet-facing and domain controller hosts because of the CISA KEV listed CVE.
AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5099540
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5099540
- Released
- 2026-07-14
- Last changed
- 2026-10-13
- Changes tracked
- 8
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Microsoft revised KB5099540 on 2026-10-13: CVEs fixed 326 to 327.
- 2026-07-29 CVEs fixed 325 to 326
- 2026-10-13 CVEs fixed 326 to 327
Recorded by Senserva on the dates shown, from the MSRC release feed. This is what moved and when, which neither the vendor advisory nor NVD publishes.
Check if KB5099540 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5099540 (checked 2026-10-13). Verify against the article before acting.
Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
Symptom
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 of 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 as "Not Possible".
The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.
The device is not already running the 2023-signed Windows Boot Manager.
In this scenario, the BitLocker recovery key only needs to be entered once -- subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged. For help finding your BitLocker recovery key, see the article, Find your BitLocker recovery key.
Enterprises are recommended to audit their BitLocker group policies for explicit PCR7 inclusion and check msinfo32.exe for their PCR7 binding status before installing this update. (See the Workaround below.)
Workaround
Remove the Group Policy configuration before installing the update (Recommended)
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 (where BitLocker is enabled on the C: drive): manage-bde -protectors -disable C:
Run the following command to resume BitLocker (where BitLocker is enabled on the C: drive): manage-bde -protectors -enable C:
This updates the BitLocker bindings to use the Windows-selected default PCR profile.
A permanent resolution for this issue is planned in a future Windows update. More information will be provided when it is ...
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
Scope and sources
- Affected products
- Also released in July 2026
KB5099444
186 CVEs · Critical · exploitedKB5099445
175 CVEs · Critical · exploitedKB5099535
262 CVEs · Critical · exploitedKB5099536
390 CVEs · Critical · exploitedKB5099538
313 CVEs · Critical · exploitedKB5099539
315 CVEs · Critical · exploitedKB5101649
384 CVEs · Critical · exploitedKB5101650
381 CVEs · Critical · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.