Microsoft has released the Windows 10 KB5131096 extended security update, bundling the November 2026 Patch Tuesday fixes with a small set of bug fixes and changes. The update is available to organizations running Windows 10 Enterprise LTSC or enrolled in the ESU program, which can install it through Settings by opening Windows Update and manually checking for updates. After installation, Windows 10 moves to build 19045.7846, while Windows 10 Enterprise LTSC 2021 moves to build 19044.7846. Microsoft is no longer adding new features to Windows 10, so the release is limited to security updates and bug fixes.
The security content comes from this month's November 2026 Patch Tuesday, which addressed 1,235 vulnerabilities across Microsoft's products. Among them was one actively exploited zero-day flaw in Outlook. Microsoft has also closed out all known issues affecting USB Audio Class 1.0 devices that were introduced by the September 2026 Windows security updates. Those problems had caused some devices to stop producing audio, fail to start with Code 10 errors, or show unresponsive volume controls and sound settings. Microsoft had previously shipped an emergency out-of-band update on September 14 to address issues with 8-channel and 3D audio modes, and the remaining audio problems are fixed in this release.
The update adjusts daylight saving time rules for Cuba for the extended 2026-2027 DST period. Cuba remains on UTC-04:00 and does not observe the November 2026 and March 2027 transitions. It returns to UTC-05:00 in November 2027 and resumes its regular seasonal schedule in 2028.
A printing fix is included as well. Adding a printer published in Active Directory through Settings, Bluetooth & devices, Printers & scanners, Add device could fail with error 87, "The parameter is incorrect." That issue was introduced by the October 2026 update and generally does not affect existing printers or printing.
The release also tightens security for PowerShell script signing and signature verification by introducing stricter encoding validation. As a result, scripts containing invalid UTF-8 encoding might fail signature validation even if they were previously accepted. To resolve the issue, administrators should review the affected scripts, save them using valid UTF-8 encoding with a byte order mark, and sign them again. Microsoft points to its Encoding Guidance for Signed PowerShell Scripts for further instructions.
More software news from TechManNews.
