Windows bugs and fixes October 31 2026: status

Has Microsoft fixed the Remote Desktop failure?

Yes. KB5127936 fixes the non-admin Remote Desktop connection failure on affected Windows 11 systems. BleepingComputer says KB5127936 resolved the Remote Desktop failure.

The failure followed KB5124010, the September 2026 non-security preview update, and Windows updates released after it. Affected systems run Windows 11 24H2 or later with the Administrator protection security feature enabled. Standard users could receive error 0xC000000D when trying to connect through Remote Desktop.

The shipped repair is the better answer for an affected computer. Check Windows Update for KB5127936. If an organization is not ready to install the preview update, Microsoft also provides a temporary workaround. An administrator can reset the User Account Control Type Of Admin Approval Mode policy through Microsoft Intune or Group Policy.

That workaround disables Administrator protection. Its cost is the loss of that security feature while the policy remains disabled. I would install KB5127936 where practical instead of trading away the protection.

Is the Always On VPN problem fixed?

No. A permanent fix for the Always On VPN problem has not shipped. Techrepublic says a permanent Always On VPN repair remains pending.

Microsoft had listed a repair in the October updates, including KB5127648, but removed that repair from the release notes. The issue status changed from Resolved to Mitigated. The Windows 11 bug affects configurations using automatic protocol selection or fallback between IKEv2 and SSTP.

Affected managed devices can fail to reconnect to corporate networks even when their internet connections work. Microsoft’s workaround is to configure the affected VPN profile to use one tunneling protocol instead of automatic selection or fallback.

The workaround costs flexibility. A profile fixed to IKEv2 cannot fall back to SSTP, and a profile fixed to SSTP cannot select IKEv2 automatically. Ask the person who manages the VPN profile which protocol the connection should use. Do not treat KB5127648 as the permanent repair.

What shipped, and what is still pending?

KB5127936 shipped with the Remote Desktop repair, while the permanent Always On VPN repair remains pending. BleepingComputer identifies KB5127936 as the shipped Remote Desktop fix.

That distinction matters. The Remote Desktop failure now has a named Windows update fix. The VPN failure has a mitigation, not a repair. Installing the latest available update does not remove the need to check an affected VPN profile.

I would record the two statuses separately. Mark Remote Desktop as fixed by KB5127936. Mark Always On VPN as mitigated through a single-protocol configuration. Do not close the VPN case merely because an October update is installed.

My previous Windows status report provides the immediate earlier context. Today’s useful change is that the Remote Desktop repair is clearly attributable to KB5127936. The VPN position remains unchanged: Microsoft plans a future repair, but no named permanent fix is available in the cited report.

Are these Windows known issues documented?

Yes. The affected features, update names, workaround and shipped repair are publicly attributable. BleepingComputer documents the affected Windows versions, error code, workaround and KB5127936 repair.

I do not regard either failure as an unexplained Windows KB update problem. Microsoft publishes known issues, workarounds and fix builds through release health and KB articles. The useful work is matching the symptom on the computer to the documented condition.

For Remote Desktop, check whether the user lacks administrator rights, whether Administrator protection is enabled and whether KB5127936 is installed. For Always On VPN, check whether the profile uses automatic selection or fallback between IKEv2 and SSTP.

Ordinary users can read the status and identify the relevant update. An IT department may still need to change managed policy or a managed VPN profile. Waiting for scheduled work can be reasonable, but the person at the keyboard should know whether a fix has shipped and what access is being lost meanwhile.

What can you do today?

Install KB5127936 for the documented Remote Desktop failure, or ask the administrator responsible for the computer to install it. Microsoft recommends one tunneling protocol for affected Always On VPN profiles.

If Remote Desktop still fails, confirm that the computer runs Windows 11 24H2 or later and that Administrator protection is enabled. Check whether the connecting account is a standard user. Record error 0xC000000D if it appears. Those details identify the documented condition.

If KB5127936 cannot be installed yet, ask an administrator whether temporarily disabling Administrator protection is acceptable. State the trade-off plainly: the workaround restores access by turning off the named security feature.

For an affected VPN, ask the VPN administrator to choose IKEv2 or SSTP instead of automatic selection or fallback. The cost is losing automatic protocol choice. Keep the case open after applying the workaround because the permanent repair has not shipped.

Do not uninstall unrelated updates merely because Remote Desktop or VPN access failed. Match the symptom, configuration and update status before changing the computer.