BleepingComputer reports Windows 10 KB5131096 ESU update released

What happened

According to BleepingComputer, Microsoft released the Windows 10 KB5131096 extended security update on November 10, 2026. BleepingComputer reports that it includes the November 2026 Patch Tuesday fixes plus a few bug fixes and changes. The outlet says Microsoft no longer releases new features for Windows 10, so the update mainly carries security updates and bug fixes.

BleepingComputer says the Patch Tuesday release addressed 1,235 vulnerabilities across Microsoft products, including one actively exploited Outlook zero-day flaw. The article does not name a CVE ID for that flaw, so the identifier is not confirmed here. This is a single-outlet report. No Microsoft advisory is among the sources, and BleepingComputer does not say which fixes are specific to KB5131096.

Other changes BleepingComputer lists for KB5131096:

• Build numbers: Windows 10 moves to build 19045.7846, and Windows 10 Enterprise LTSC 2021 moves to build 19044.7846.
• PowerShell: Stricter encoding validation for script signing and signature verification. Scripts with invalid UTF-8 encoding might fail signature validation even if they were accepted before.
• Printing: A fix for adding an Active Directory-published printer failing with error 87. BleepingComputer says the October 2026 update introduced the issue.
• Remote Desktop: A fix for a trusted .rdp publishers policy that could not be configured through Microsoft Intune. A second fix covers shadow connections that might fail with an “Unspecified error” on Windows Server 2016 and Windows Server 2012 R2 after the October 14, 2026 update.
• Date and time: Updated daylight saving time rules for Cuba.
• USB audio: BleepingComputer says Microsoft states it has resolved all known USB Audio Class 1.0 issues introduced by the September 2026 security updates.

Am I affected?

Per BleepingComputer, the update is for Windows 10 Enterprise LTSC or devices enrolled in the ESU program. You are in scope if you run Windows 10 in either of those ways and have not yet installed it.

Check your build number. According to BleepingComputer, a patched system shows 19045.7846 (Windows 10) or 19044.7846 (Enterprise LTSC 2021).

You should also check whether you rely on signed PowerShell scripts. BleepingComputer says scripts with invalid UTF-8 encoding might now fail signature validation.

Not confirmed from the sources: the CVE list for this update, which fix addresses the Outlook zero-day, and whether KB5131096 itself closes that flaw.

What to do now

1. Open Settings, click Windows Update, and manually run Check for Updates to install KB5131096, as BleepingComputer describes.
2. Confirm the build after installing: 19045.7846 for Windows 10, or 19044.7846 for Windows 10 Enterprise LTSC 2021.
3. If you use signed PowerShell scripts, test them. BleepingComputer says scripts that now fail should be saved with valid UTF-8 encoding with a byte order mark (BOM) and signed again.
4. For the Outlook zero-day, consult Microsoft’s own November 2026 Patch Tuesday documentation. The sources here do not give its CVE ID or the specific fix.

Sources

• BleepingComputer: Microsoft releases Windows 10 KB5131096 extended security update