New Update Windows 10 September 2026 Patch Tuesday (KB5122878)

Gandalf_The_Grey

Level 85
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
Apr 24, 2016
7,842
6
83,901
8,389
55
The Netherlands
It's the second Tuesday of the month, which means we're getting a new set of Patch Tuesday updates for Windows 10. Microsoft is rolling out the monthly security update (also called "B release") for Windows 10 users in the the Extended Security Updates (ESU) program.

The new updates are being distributed under KB5122878 for Windows 10 22H2, 22H1 and bumps the build numbers to 19045.7725 and 19044.7725. You can download the new update directly from the Microsoft Update Catalog at this link.

Here's the complete changelog of the KB5122878 update for Windows 10:
  • [Secure Boot] This update includes additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Certificate deployment via Windows updates continues across supported PCs and non-managed business devices in the coming months.
  • [Date and Time] This update adjusts Morocco Standard Time to reflect Morocco's transition to permanent UTC+00:00 effective September 20, 2026. This change ensures that the correct local time is displayed after the transition.
  • [OMA DM protocol] This update improves the logging features of the OMA DM Client (omadmclient.exe) component. More debug information is now saved when connecting to a server.
  • [Windows Code Integrity policies] Improves application compatibility during Windows certificate-authority rotation by recognizing Microsoft Windows Production PCA 2026 RSA2048-SHA256 as equivalent to PCA 2011.
  • [Remote Desktop] This update addresses an issue that affects Remote Desktop audio redirection. Audio from the remote session might not play on the local computer in certain configurations.
  • [BitLocker Group Policy] This update addresses the "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key" known issue.
 

You may also like...