Known issues in Microsoft Patches:
Microsoft often releases patches to address security and reliability issues. Sometimes, patches itself will introduce unprecedented issues after installing them. Here's the updated list of all the known issues in Microsoft patches and possible workaround for them.

Oops! No results for your search.

workaround
Nov 18, 2026
KB5136490
2026-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5136490)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5136489
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5136489) (26100.33828)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5136487
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5136487)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5136483
2026-11 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5136483)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134140
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5134140)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134137
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5134137) (26100.33674)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134134
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5134134) (28000.3237)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134133
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5134133) (26100.9725)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134130
2026-10 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5134130)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134124
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5134124)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5134123
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5134123) (ESU)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5132059
2026-11 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5132059) (28000.3501)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5131291
2026-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5131291) (ESU)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5131090
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5131090)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5131087
2026-11 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5131087)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5131085
2026-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5131085)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5131080
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5131080)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5127936
2026-10 Cumulative Update Preview for Windows 11, version 25H2 for arm64-based Systems (KB5127936) (26200.9818)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5127653
2026-10 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5127653) (28000.3365)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5127648
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5127648) (26100.9711) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5127646
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5127646) (28000.3231) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5126868
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5126868) (CVE-2026-108398) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5126655
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5126655) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5126653
2026-10 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5126653) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 18, 2026
KB5126651
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5126651) (CVE-2026-96951)
"SQL Server linked server connections might remain open After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time. This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running. If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time"
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business. We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
workaround
Nov 16, 2026
KB5136489
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5136489) (26100.33828)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Nov 16, 2026
KB5136487
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5136487)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Nov 12, 2026
KB5131096
2026-11 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5131096)
"Windows activation and licensing commands might fail with error 0x80041008 After installing the November 2026 Windows security update, certain Windows activation and licensing operations performed using the Software Licensing Management Tool might fail. Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys. The failure has been observed while executing the following commands: slmgr.vbs /skms-domain slmgr.vbs /ipk This issue primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing. Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected. Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation. Customers who have the KMS client key already installed in their image and do not use slmgr for further configurations are unaffected"
This issue is resolved in Windows updates released on and after November 13, 2026 such as KB5136493. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 12, 2026
KB5132061
2026-11 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5132061) (26100.9974)
"November security update might fail to install on some devices When attempting to install the November 2026 Windows security update KB5127936, some devices might be unable to complete the installation. Affected devices might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993"
The resolution for this issue is automatically running in affected devices connected to the internet and using Windows Update in Settings to install updates. No manual action from end-users is required to receive the repair. All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT. Once your device receives the repair, it will automatically download and install the November 2026 security update via Windows Update. You can also install the update by following these instructions. We will update this documentation once the resolution rollout is completed. If you still face installation issues after 48 hours, please use Windows help and learning or contact Microsoft Support.
workaround
Nov 12, 2026
KB5131090
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5131090)
"Windows activation and licensing commands might fail with error 0x80041008 After installing the November 2026 Windows security update, certain Windows activation and licensing operations performed using the Software Licensing Management Tool might fail. Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys. The failure has been observed while executing the following commands: slmgr.vbs /skms-domain slmgr.vbs /ipk This issue primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing. Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected. Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation. Customers who have the KMS client key already installed in their image and do not use slmgr for further configurations are unaffected"
This issue is resolved in Windows updates released on and after November 13, 2026 such as KB5136487. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 12, 2026
KB5131087
2026-11 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5131087)
"Windows activation and licensing commands might fail with error 0x80041008 After installing the November 2026 Windows security update, certain Windows activation and licensing operations performed using the Software Licensing Management Tool might fail. Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys. The failure has been observed while executing the following commands: slmgr.vbs /skms-domain slmgr.vbs /ipk This issue primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing. Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected. Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation. Customers who have the KMS client key already installed in their image and do not use slmgr for further configurations are unaffected"
This issue is resolved in Windows updates released on and after November 13, 2026 such as KB5136483. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 12, 2026
KB5131085
2026-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5131085)
"Windows activation and licensing commands might fail with error 0x80041008 After installing the November 2026 Windows security update, certain Windows activation and licensing operations performed using the Software Licensing Management Tool might fail. Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys. The failure has been observed while executing the following commands: slmgr.vbs /skms-domain slmgr.vbs /ipk This issue primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing. Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected. Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation. Customers who have the KMS client key already installed in their image and do not use slmgr for further configurations are unaffected"
This issue is resolved in Windows updates released on and after November 13, 2026 such as KB5136490. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 12, 2026
KB5131080
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5131080)
"Windows activation and licensing commands might fail with error 0x80041008 After installing the November 2026 Windows security update, certain Windows activation and licensing operations performed using the Software Licensing Management Tool might fail. Affected devices might encounter error 0x80041008, Invalid parameter (SWbemObjectEx), when running commands to activate Windows, configure Key Management Service (KMS), or manage product keys. The failure has been observed while executing the following commands: slmgr.vbs /skms-domain slmgr.vbs /ipk This issue primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing. Devices that are already activated remain activated. Customers whose devices already have the appropriate KMS client key and KMS configuration, and who do not need to run the affected Slmgr.vbs commands, are not expected to be affected. Devices that are being configured to use KMS activation might encounter errors when attempting to initiate their activation. KMS-activated devices typically remain activated for up to 180 days following successful activation. Customers who have the KMS client key already installed in their image and do not use slmgr for further configurations are unaffected"
This issue is resolved in Windows updates released on and after November 13, 2026 such as KB5136489. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5131291
2026-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5131291) (ESU)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129239). The remaining symptoms are addressed in (KB5131291).
workaround
Nov 11, 2026
KB5131291
2026-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5131291) (ESU)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131291). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5131096
2026-11 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5131096)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129236). The remaining symptoms are addressed in (KB5131096).
workaround
Nov 11, 2026
KB5131090
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5131090)
"Windows Server Update Services (WSUS) does not display error details "
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Nov 11, 2026
KB5131090
2026-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5131090)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131090). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5131085
2026-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5131085)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129238). The remaining symptoms are addressed in (KB5131085).
workaround
Nov 11, 2026
KB5131085
2026-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5131085)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131085). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5131080
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5131080)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Nov 11, 2026
KB5131080
2026-11 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5131080)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131080). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5134137
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5134137) (26100.33674)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
workaround
Nov 11, 2026
KB5127648
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5127648) (26100.9711) (CVE-2026-96951)
"You might be unable to turn on Smart App Control After installing this update, some devices might be unable to turn on Smart App Control in the Windows Security app if it has been turned off. On affected devices, the option to turn on Smart App Control might be grayed out. Devices where Smart App Control is already turned on are not affected and remain protected"
This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936). This issue was resolved for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026 (KB5132061). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Nov 11, 2026
KB5126646
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5126646) (CVE-2026-96951)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
workaround
Nov 11, 2026
KB5126868
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5126868) (CVE-2026-108398) (CVE-2026-96951)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129239). The remaining symptoms are addressed in (KB5131291).
workaround
Nov 11, 2026
KB5122871
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5122871) (26100.33438) (CVE-2026-81963)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
workaround
Nov 7, 2026
KB5129244
2026-09 Update for Windows Server 2012 for x64-based Systems (KB5129244) (ESU)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue was partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129244). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135580).
workaround
Nov 7, 2026
KB5129243
2026-09 Update for Windows Server 2012 R2 for x64-based Systems (KB5129243) (ESU)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129243). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135582).
workaround
Nov 7, 2026
KB5126836
2026-10 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5126836) (ESU) (CVE-2026-96951)
"Multipath I/O (MPIO)-managed iSCSI disks go offline Multipath I/O (MPIO)-managed disks may unexpectedly go offline or display error C0000010 in the details tab of device manager. MPIO is a storage multipathing technology used to manage paths between a server and its storage. Although the storage location becomes unavailable, this issue does not result in data loss or change. MPIO-managed storage and all underlying data is immediately visible after disabling MPIO"
This issue is resolved in an out-of-band (OOB) update released on November 6, 2016, (KB5135582).
workaround
Nov 7, 2026
KB5126835
2026-10 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5126835) (ESU)
"Multipath I/O (MPIO)-managed iSCSI disks go offline Multipath I/O (MPIO)-managed disks may unexpectedly go offline or display error C0000010 in the details tab of device manager. MPIO is a storage multipathing technology used to manage paths between a server and its storage. Although the storage location becomes unavailable, this issue does not result in data loss or change. MPIO-managed storage and all underlying data is immediately visible after disabling MPIO"
This issue is resolved in an out-of-band (OOB) update released on November 6, 2016, (KB5135580).
workaround
Nov 7, 2026
KB5123065
2026-09 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5123065) (ESU) (CVE-2026-85880)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue was partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129244). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135580).
workaround
Oct 30, 2026
KB5127936
2026-10 Cumulative Update Preview for Windows 11, version 25H2 for arm64-based Systems (KB5127936) (26200.9818)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Oct 30, 2026
KB5127653
2026-10 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5127653) (28000.3365)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Oct 28, 2026
KB5134140
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5134140)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Oct 28, 2026
KB5134140
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5134140)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131090). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134137
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5134137) (26100.33674)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Oct 28, 2026
KB5134137
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5134137) (26100.33674)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131080). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134134
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5134134) (28000.3237)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129194). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
workaround
Oct 28, 2026
KB5134134
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5134134) (28000.3237)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue is addressed by Windows updates released on and after October 28, 2026 (KB5127653). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134133
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5134133) (26100.9725)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129195). The remaining symptoms are addressed in (KB5132061).
workaround
Oct 28, 2026
KB5134133
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5134133) (26100.9725)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936). This issue was resolved for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026 (KB5132061). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134133
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5134133) (26100.9725)
"You might be unable to turn on Smart App Control After installing this update, some devices might be unable to turn on Smart App Control in the Windows Security app if it has been turned off. On affected devices, the option to turn on Smart App Control might be grayed out. Devices where Smart App Control is already turned on are not affected and remain protected. You can modify the registry to restore the ability to turn on Smart App Control by following these steps: Open a Command Prompt window by typing cmd in the Search box. Select Run as administrator. At the command prompt, enter the following commands. Then restart the device. reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2883193997 /t REG_DWORD /d 1 /f reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2850574478 /t REG_DWORD /d 1 /f IT administrators can instead choose to mitigate this issue for enterprise-managed devices managed by IT departments by installing and configuring the special Group Policies listed below. Download #1 for Windows 11, versions 24H2, 25H2, and 26H2 - KB5074105 261015_19222 Feature Preview Download #2 for Windows 11, versions 24H2, 25H2, and 26H2 - KB5074105 261015_19221 Feature Preview Important: You should install and configure both Group Policies to resolve this issue. The first Group Policy is needed to turn on Smart App Control. The second Group Policy ensures that logging is available to assist with troubleshooting in case any problems arise. The special Group Policies can be found in Computer Configuration > Administrative Templates > {Group Policy name} > Windows 11, version 24H2, 25H2. After installing the Group Policies, configure the value for both settings to Enabled and restart your device(s) to apply the Group Policy settings. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release"
This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936). This issue was resolved for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026 (KB5132061). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134125
2026-10 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5134125)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129236). The remaining symptoms are addressed in (KB5131096).
workaround
Oct 28, 2026
KB5134124
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5134124)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129238). The remaining symptoms are addressed in (KB5131085).
workaround
Oct 28, 2026
KB5134124
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5134124)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131085). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 28, 2026
KB5134123
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5134123)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129239). The remaining symptoms are addressed in (KB5131291).
workaround
Oct 28, 2026
KB5134123
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5134123)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131291). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 24, 2026
KB5127646
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5127646) (28000.3231) (CVE-2026-96951)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124006, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue is addressed by Windows updates released on and after October 27, 2026 (KB5127653). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released October 27, 2026 (KB5127653) or later, you do not need to use a workaround for this issue. If you are using an update released before October 27, 2026, and have this issue, you have the option to apply the following workaround. IT administrators can mitigate this issue on devices affected by the Remote Desktop connection failure by using their existing policy management method to temporarily turn off Administrator protection. Reset the User Account Control Type Of Admin Approval Mode policy in Microsoft Intune or Group Policy. For more information, see Administrator protection on Windows 11.
workaround
Oct 17, 2026
KB5126868
2026-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5126868) (CVE-2026-108398) (CVE-2026-96951)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131291). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 17, 2026
KB5126655
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5126655) (CVE-2026-96951)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131090). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 17, 2026
KB5126651
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5126651) (CVE-2026-96951)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131085). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 17, 2026
KB5126646
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5126646) (CVE-2026-96951)
"Users might be unable to sign in to OWA or send emails on Exchange Server After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication. In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn't required for these issues to occur"
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131080). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 15, 2026
KB5127648
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5127648) (26100.9711) (CVE-2026-96951)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129195). The remaining symptoms are addressed in (KB5132061).
workaround
Oct 15, 2026
KB5127648
2026-10 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5127648) (26100.9711) (CVE-2026-96951)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936). This issue was resolved for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026 (KB5132061). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 15, 2026
KB5127646
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5127646) (28000.3231) (CVE-2026-96951)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is addressed by Windows updates released on and after October 27, 2026 (KB5127653). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released October 27, 2026 (KB5127653) or later, you do not need to use a workaround for this issue. If you are using an update released before October 27, 2026, and have this issue, you have the option to apply the following workaround. IT administrators can mitigate this issue on devices affected by the Remote Desktop connection failure by using their existing policy management method to temporarily turn off Administrator protection. Reset the User Account Control Type Of Admin Approval Mode policy in Microsoft Intune or Group Policy. For more information, see Administrator protection on Windows 11.
workaround
Oct 15, 2026
KB5127646
2026-10 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5127646) (28000.3231) (CVE-2026-96951)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue is addressed by Windows updates released on and after October 28, 2026 (KB5127653). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 15, 2026
KB5126836
2026-10 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5126836) (ESU) (CVE-2026-96951)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129243). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135582).
workaround
Oct 15, 2026
KB5126835
2026-10 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5126835) (ESU)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue was partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129244). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135580).
workaround
Oct 15, 2026
KB5126657
2026-10 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5126657)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129236). The remaining symptoms are addressed in (KB5131096).
workaround
Oct 15, 2026
KB5126655
2026-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5126655) (CVE-2026-96951)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287.
workaround
Oct 15, 2026
KB5126651
2026-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5126651) (CVE-2026-96951)
"USB Audio Class 1.0 devices with error Code 10 or no output After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129238). The remaining symptoms are addressed in (KB5131085).
workaround
Oct 15, 2026
KB5126646
2026-10 Cumulative Update for Microsoft server operating system version 24H2 for ARM64-based Systems (KB5126646) (CVE-2026-96951)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287.
workaround
Oct 14, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127646. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127646. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124010
2026-09 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5124010) (26100.9550)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936). This issue was resolved for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026 (KB5132061). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26100.9445) (CVE-2026-81963)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124006
2026-09 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5124006) (28000.3086)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127646. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124006
2026-09 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5124006) (28000.3086)
"Remote Desktop connections might fail for non-admin users with error 0xC000000D After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, "The token that was passed to the function is invalid." This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled. Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently"
This issue is addressed by Windows updates released on and after October 28, 2026 (KB5127653). We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5120998
2026-08 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5120998) (26100.9278)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5120996
2026-08 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5120996) (28000.2804)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127646. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 14, 2026
KB5124010
2026-09 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5124010) (26100.9550)
"Applications which require AC-3 audio decoding might close unexpectedly After installing this update, some applications that use AC-3 (Dolby Digital) audio decoding might fail to launch or close unexpectedly when certain audio features are used. This issue primarily affects legacy applications that rely on Windows built-in audio decoding. Most modern applications are not affected"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 11, 2026
KB5123066
2026-09 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5123066) (ESU) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129243). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135582).
workaround
Oct 11, 2026
KB5123065
2026-09 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5123065) (ESU) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue was partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129244). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. The remainder of the issue, that caused some USB Audio Class 1.0 devices to fail to start or produce audio, is resolved with an OOB update released on November 6, 2016, (KB5135580).
workaround
Oct 11, 2026
KB5122882
2026-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5122882) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, KB5129237. The remaining symptoms are addressed in KB5126655.
workaround
Oct 11, 2026
KB5122878
2026-09 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5122878) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129236). The remaining symptoms are addressed in (KB5131096).
workaround
Oct 11, 2026
KB5122871
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5122871) (26100.33438) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
workaround
Oct 10, 2026
KB5129244
2026-09 Update for Windows Server 2012 for x64-based Systems (KB5129244) (ESU)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026. This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
workaround
Oct 10, 2026
KB5129243
2026-09 Update for Windows Server 2012 R2 for x64-based Systems (KB5129243) (ESU)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026. This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
workaround
Oct 10, 2026
KB5129242
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5129242)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129236). The remaining symptoms are addressed in (KB5131096).
workaround
Oct 10, 2026
KB5129235
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5129235) (26100.33451)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
workaround
Oct 10, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129195). The remaining symptoms are addressed in (KB5132061).
workaround
Oct 10, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129194). The remaining symptoms are addressed in (KB5132059).
workaround
Oct 10, 2026
KB5123099
2026-09 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5123099) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129239). The remaining symptoms are addressed in (KB5131291).
workaround
Oct 10, 2026
KB5122880
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5122880) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129242). The remaining symptoms are addressed in (KB5131087).
workaround
Oct 10, 2026
KB5122876
2026-09 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5122876) (CVE-2026-85880)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129238). The remaining symptoms are addressed in (KB5131085).
workaround
Oct 9, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"After installing the September 8, 2026, Windows security update (KB5124008), or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124008 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature"
This issue is addressed by KB5124010. This update prevents Machine Identity Isolation (MII) enforcement by disabling it completely while improvements are made to the feature. MII enforcement will be prevented regardless of the MII configuration.
workaround
Oct 9, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature"
This issue is addressed by KB5124010. This update prevents Machine Identity Isolation (MII) enforcement by disabling it completely while improvements are made to the feature. MII enforcement will be prevented regardless of the MII configuration.
workaround
Oct 9, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature"
This issue is addressed by KB5124010. This update prevents Machine Identity Isolation (MII) enforcement by disabling it completely while improvements are made to the feature. MII enforcement will be prevented regardless of the MII configuration.
workaround
Oct 9, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26100.9445) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update (KB5124008), or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124008 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature"
This issue is addressed by KB5124010. This update prevents Machine Identity Isolation (MII) enforcement by disabling it completely while improvements are made to the feature. MII enforcement will be prevented regardless of the MII configuration.
workaround
Oct 1, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 25H2 and Windows 11, version 24H2: KB5124010 260924_20021 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 26H1: KB5124006 260924_20071 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 26H1: KB5124006 260924_20071 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5124010
2026-09 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5124010) (26100.9550)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 25H2 and Windows 11, version 24H2: KB5124010 260924_20021 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Oct 1, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26100.9445) (CVE-2026-81963)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 25H2 and Windows 11, version 24H2: KB5124010 260924_20021 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5124006
2026-09 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5124006) (28000.3086)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 26H1: KB5124006 260924_20071 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5120998
2026-08 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5120998) (26100.9278)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 25H2 and Windows 11, version 24H2: KB5124010 260924_20021 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Oct 1, 2026
KB5120996
2026-08 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5120996) (28000.2804)
"Devices might experience a black screen or desktop loading issues after sign-in After installing the August 2026 Windows non-security preview update KB5120996 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles. Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes. Download for Windows 11, version 26H1: KB5124006 260924_20071 Known Issue Rollback For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback"
Affected customers can apply one of the following workarounds to mitigate the issue: Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR). For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below We are working on a resolution for this issue, and it will be released in a future Windows update.
workaround
Sept 24, 2026
KB5129242
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5129242)
"After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll."
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5126653. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 24, 2026
KB5124010
2026-09 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5124010) (26100.9550)
"After installing the September 8, 2026, Windows security update (KB5124008), or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124008 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature."
Important: This section contains information about modifying the registry. Before you modify the registry, back it up and make sure that you know how to restore it if a problem occurs. For more information, see How to back up and restore the registry in Windows. To work around this issue, disable Machine Identity Isolation using the same management method that was used to enable it. Choose the applicable option below: If Machine Identity Isolation was enabled by Intune policy, disable Machine Identity Isolation with Intune. If Machine Identity Isolation was enabled by Group Policy, disable Machine Identity Isolation with Group Policy. If Machine Identity Isolation was enabled directly in the registry, use these steps to disable it: On the Windows 11, version 24H2 or 25H2 device, locate the following registry paths: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MachineIdentityIsolation HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\MachineIdentityIsolation For either of these registry keys, if the value of MachineIdentityIsolation is set to 2, change it to: MachineIdentityIsolation = 0 After you disable Machine Identity Isolation, restart the device. Then reset the secure channel using the following command: Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 24, 2026
KB5124006
2026-09 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5124006) (28000.3086)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices."
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 24, 2026
KB5124006
2026-09 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5124006) (28000.3086)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected."
Important: This section contains information about modifying the registry. Before you modify the registry, back it up and make sure that you know how to restore it if a problem occurs. For more information, see How to back up and restore the registry in Windows. To work around this issue, disable Machine Identity Isolation using the same management method that was used to enable it. Choose the applicable option below: If Machine Identity Isolation was enabled by Intune policy, disable Machine Identity Isolation with Intune. If Machine Identity Isolation was enabled by Group Policy, disable Machine Identity Isolation with Group Policy. If Machine Identity Isolation was enabled directly in the registry, use these steps to disable it: On the Windows 11, version 24H2 or 25H2 device, locate the following registry paths: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MachineIdentityIsolation HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\MachineIdentityIsolation For either of these registry keys, if the value of MachineIdentityIsolation is set to 2, change it to: MachineIdentityIsolation = 0 After you disable Machine Identity Isolation, restart the device. Then reset the secure channel using the following command: Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 23, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"File History might stop working after installing September 2026 Windows update After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 23, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"File History might stop working after installing September 2026 Windows update After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124006. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 23, 2026
KB5002910
Security Update for Microsoft Office Online Server (KB5002910) farm-deployment
"In Excel Online, the paste operation might fail silently. Although users try to paste content, the source remains selected and the destination is unmodified. When this issue occurs, users receive no indication of the failure, such as a beep or error message."
This issue is fixed in the September 22, 2026, update for Office Online Server (KB4461632)
workaround
Sept 22, 2026
KB5002665
Update for Microsoft Excel 2016 (KB5002665) 32-Bit Edition
"If the workbook contains conditional formatting, paste operations might continue to fail."
If the paste operation fails, users can try the following Paste Special options: On the Home tab, select the Paste dropdown list, and then select Paste Special. In the Paste Special window, select one of the following options: Formulas Formulas & Number Formatting Values Values & Number Formatting Link
workaround
Sept 22, 2026
KB5122880
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5122880) (CVE-2026-81963)
"Host folder shares might be unavailable in Hyper-V-based Linux VMs After installing the September 2026 security update KB5122880, applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 21, 2026
KB5122878
2026-09 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5122878) (CVE-2026-85880)
"After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5126657. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 20, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124006. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 20, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26100.9445) (CVE-2026-81963)
"After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 20, 2026
KB5122880
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5122880) (CVE-2026-81963)
"After installing the September 2026 Windows security update KB5124008, some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History, is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll"
This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5126653. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 18, 2026
KB5129195
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5129195) (26100.9457)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature."
Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 18, 2026
KB5129194
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5129194) (28000.2956)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature."
Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 18, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature."
Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 18, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26100.9445) (CVE-2026-81963)
"After installing the September 8, 2026, Windows security update KB5124012, or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected. This issue occurs because KB5124012 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature."
Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.
workaround
Sept 17, 2026
KB5002914
Security Update for Microsoft Excel 2016 (KB5002914) 32-Bit Edition
"In Microsoft Excel 2024, 2021, 2019, and 2016, the paste operation might fail silently. Although users try to paste content, the source remains selected and the destination is unmodified. When this issue occurs, users receive no indication of the failure, such as a beep or error message."
To work around this issue, see the following Knowledge Base article: September 16, 2026, update for Excel 2016 (KB5002665) Users who experience this issue can try the following paste special options: Formulas Formulas & Number Formatting Values Values & Number Formatting Link
workaround
Sept 16, 2026
KB5129244
2026-09 Update for Windows Server 2012 for x64-based Systems (KB5129244) (ESU)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 16, 2026
KB5129243
2026-09 Update for Windows Server 2012 R2 for x64-based Systems (KB5129243) (ESU)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 16, 2026
KB5129237
2026-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5129237)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, KB5129237. The remaining symptoms are addressed in KB5126655.
workaround
Sept 16, 2026
KB5129237
2026-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5129237)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Sept 16, 2026
KB5129235
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5129235) (26100.33451)
"After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. This issue is limited to USB Audio Class 1.0 devices"
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 16, 2026
KB5129235
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5129235) (26100.33451)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Sept 14, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129194. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"Host folder shares might be unavailable in Hyper-V-based Linux VMs After installing the September 2026 security update (KB5124012), applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129194.
workaround
Sept 14, 2026
KB5124012
2026-09 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5124012) (28000.2954) (CVE-2026-81963)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129194). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
workaround
Sept 14, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26300.9445) (CVE-2026-81963)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129195. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26300.9445) (CVE-2026-81963)
"Host folder shares might be unavailable in Hyper-V-based Linux VMs After installing the September 2026 security update (KB5124008), applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129195.
workaround
Sept 14, 2026
KB5124008
2026-09 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5124008) (26300.9445) (CVE-2026-81963)
"USB audio devices might fail to start or produce no sound After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: The device displays an error in Device Manager: "This device cannot start (Code 10)." No audio output. Volume controls are unresponsive or remain at zero. Sound settings are unresponsive or unavailable. Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices"
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129195). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
workaround
Sept 14, 2026
KB5123099
2026-09 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5123099) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129239. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5123066
2026-09 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5123066) (ESU) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129243. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5123065
2026-09 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5123065) (ESU) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129244. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122882
2026-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5122882) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129237. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122880
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5122880) (CVE-2026-81963)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129242. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122880
2026-09 Cumulative Update for Windows 11, version 23H2 for arm64-based Systems (KB5122880) (CVE-2026-81963)
"After installing the September 2026 security update (KB5122880), applications that use [HCS-managed](https://learn.microsoft.com/virtualization/api/hcs/overview) virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue."
Microsoft is working on a resolution and will update this documentation when more information is available.
workaround
Sept 14, 2026
KB5122878
2026-09 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5122878) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129236. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122876
2026-09 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5122876) (CVE-2026-85880)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129238. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122871
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5122871) (26100.33438) (CVE-2026-81963)
"Remote Desktop Services might stop responding after September 2026 security update After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Microsoft Support: IT administrators who need an immediate workaround should contact Microsoft Support for Business for assistance"
This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129235. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 14, 2026
KB5122871
2026-09 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5122871) (26100.33438) (CVE-2026-81963)
"Windows Server Update Services (WSUS) does not display error details "
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Sept 10, 2026
KB5122882
2026-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5122882) (CVE-2026-85880)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287
workaround
Sep 9, 2026
KB5120249
2026-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5120249) (CVE-2026-62832) (CVE-2026-68820)
"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.)"
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 available.
workaround
Sept 9, 2026
KB5120998
2026-08 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5120998) (26100.9278)
"Desktop background settings are lost or reset on some devices Following installation of Windows updates released August 27, 2026 KB5120998 and later, some Windows Desktop settings fail to load, resulting in desktop backgrounds displaying as a solid black color. It is possible other desktop settings may be affected, such as slideshow settings or contrast themes. On affected devices, attempting to manually restore customized settings does not work. This is because the issue prevents the correct loading of settings, regardless of their value. In this case, a default black background is used instead"
This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124008. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 9, 2026
KB5121003
2026-08 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5121003) (26100.9168) (CVE-2026-62832) (CVE-2026-68820)
"Microsoft Teams and Outlook might fail to launch on ARM-based devices After installing Windows security updates released on or after August 11, 2026, (KB5121003), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates"
To work around this issue: Open Microsoft Store. Select Downloads > Check for updates. Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later). This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124008. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 9, 2026
KB5121000
2026-08 Cumulative Update for Windows 11, version 26H1 for arm64-based Systems (KB5121000) (28000.2704) (CVE-2026-62832) (CVE-2026-72971) (CVE-2026-68820)
"Microsoft Teams and Outlook might fail to launch on ARM-based devices After installing Windows security updates released on or after August 11, 2026, (KB5121000), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates"
To work around this issue: Open Microsoft Store. Select Downloads > Check for updates. Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later). This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124012. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 9, 2026
KB5120998
2026-08 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5120998) (26100.9278)
"Microsoft Teams and Outlook might fail to launch on ARM-based devices After installing Windows security updates released on or after August 11, 2026, (KB5121003), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates"
To work around this issue: Open Microsoft Store. Select Downloads > Check for updates. Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later). This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124008. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 4, 2026
KB5120996
2026-08 Cumulative Update Preview for Windows 11, version 26H1 for arm64-based Systems (KB5120996) (28000.2804)
"Microsoft Teams and Outlook might fail to launch on ARM-based devices After installing Windows security updates released on or after August 11, 2026, (KB5121000), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates"
To work around this issue: Open Microsoft Store. Select Downloads > Check for updates. Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later). This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124012. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Sept 9, 2026
KB5120998
2026-08 Cumulative Update Preview for Windows 11, version 24H2 for arm64-based Systems (KB5120998) (26100.9278)
"Mouse customization is reset on non-English Windows devices Following installation of Windows updates released August 27 2026 (KB5120998) and later, mouse personalization settings are being reverted to certain standard settings. This includes cursor and cursor animations that are selected in the Mouse Properties options under Windows. Our investigation indicates that this issue is caused by code components used in non-English Windows installations. In impacted locales, these settings will fail to load, causing a default to be used instead. Attempting to manually restore the settings values is not successful, as the issue prevents loading these settings regardless of their value"
This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124008. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
workaround
Aug 28, 2026
KB5121003
2026-08 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5121003) (26100.9168) (CVE-2026-62832) (CVE-2026-68820)
"Reports of certain games becoming unresponsive Microsoft received reports of issues involving inability to run certain games as expected after installing this update. Ongoing investigation indicates that this issue is associated with certain peripherals or internal device components that support RGB lighting features. These devices might install drivers or software components with file names similar to inpoutx64. On systems where these drivers are found, launching certain games can trigger this issue. Games identified in reports of this issue include ARC Raiders, MARVEL Tkon: Fighting Souls, and THE FINALS. Reported symptoms include: the game application becomes unresponsive the game application closes without notice the error "EXCEPTION_ACCESS_VIOLATION" is displayed the device restarts without warning If you are experiencing this issue or a similar issue, please use Feedback Hub to submit a report. You can open Feedback Hub by pressing the Windows logo key + F. For additional information, see Send feedback to Microsoft with the Feedback Hub app. Your reports are helpful to our investigation"
This issue is resolved by a block that prevents the inpoutx64 driver from loading on affected devices. When the block is applied, a message is displayed that states the driver has been disabled, after which the game will launch normally. This resolution is available automatically to consumer and business devices that are not managed by IT departments. For enterprise-managed devices, the mitigation will not propagate automatically. IT administrators can follow the steps in the workaround section on the Windows release health site.
workaround
Aug 12, 2026
KB5120233
2026-08 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5120233) (26100.33296) (CVE-2026-62832) (CVE-2026-68820)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287.
workaround
Aug 12, 2026
KB5120242
2026-08 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5120242) (CVE-2026-62832) (CVE-2026-68820)
"Windows Server Update Services (WSUS) does not display error details"
After installing KB5070884 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287.

Disclaimer:This webpage is intended to provide you information about patch announcement for certain specific software products. The information is provided "As Is" without warranty of any kind. The links provided point to pages on the vendors websites. You can get more information by clicking the links to visit the relevant pages on the vendors website.