All posts

Update known issues: what changed on October 29, 2026

Senserva Watch

Join Senserva Watch and get Three Free Unlimited Audits with our full Claude MCP, a fresh audit credit every quarter, alerts when a CVE or KB you follow changes, critical security updates when they land, the Patch Tuesday wire on release day, and 20% off when you buy.

Join Senserva Watch

One email address. No tenant connection, no agent, no call.

What Microsoft changed in update known issues, October 29, 2026

Each day we read the Known issues section of Microsoft's support article for every recent Windows and Office update and record what changed. Since our last post, Microsoft changed that section on 2 updates. Every quote below is Microsoft's own text, from the article linked beside it.

Known issues Microsoft updated

"Remote Desktop connections might fail for non-admin users with error 0xC000000D"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

This issue is addressed for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 27, 2026 ( KB5127936 ). 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 ( KB5127936 ) or later, you do not need to use a workaround for this issue. If you are using Windows 11, version 24H2, or an update released before October 27, 2026, and have this issue, you have the option to apply the following workaround.

"Remote Desktop connections might fail for non-admin users with error 0xC000000D"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

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.

"You might be unable to turn on Smart App Control"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 27, 2026 ( KB5127936 ) . 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 ( KB5127936 ) or later, you do not need to use a workaround for this issue. If you are using Windows 11, version 24H2, or an update released before October 27, 2026, and have this issue, you have the option to apply one of the following workarounds.

Every recent update and its known issues are on our Microsoft patch tracker.

Compiled automatically by the Senserva Patch Tracker from Microsoft's support articles. No AI writes this post: every quote is copied from the article it links, and an issue counts as changed only when Microsoft's text changed. Sources and their terms are on our Data sources & thanks page. Facts as of 2026-10-29.

All posts

Patching across Intune, Windows Autopatch, Defender, Azure, and your endpoint managers: see Senserva patching in action.