Friday, October 17th 2025
Microsoft Breaks Localhost with Windows 11 October Update, Users Forced to Revert
Just two days after Windows 10 reached its end of life, issues with Microsoft's latest Windows 11 October update have begun to surface. Users on Microsoft Support Forums, Stack Overflow, and Server Fault have reported that the localhost functionality in Windows 11 is now broken. This problem is affecting millions of web developers who are unable to run their applications on their own PCs. The update, KB5066835, focuses on security and enhances the September-issued KB5065789 package with additional quality improvements. However, it disrupts the localhost function, a virtual hostname that allows a PC to serve as its own server. This feature is commonly used by local developers to test websites or fully developed web apps. The disruption has significantly impacted developers, including those using Windows 11 on their local servers or workstations for production purposes.
The community has managed to solve the issue by simply deleting the October KB5066835 package, alongside its September KB5065789 sibling, if the first package uninstall doesn't work. Software engineers have reported connection failures and HTTP/2 protocol issues impacting various development tools, including ASP.NET compilation processes and Visual Studio debugging functionality. Investigation has revealed that the problem originated in build version 26100.6899, with the root cause identified in HTTP.sys—a kernel-level Windows component responsible for managing HTTP traffic on local systems.
Update October 17, 15:30 UTC: Microsoft confirmed the issue and stated: "We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available."This issue stack for Microsoft's latest Windows 11 keeps piling up. On Monday, Microsoft accidentally broke the Windows Media Creation Tool (MCT) just a day ahead of Windows 10's end-of-life. Last week, the company started mandating Online Accounts for Windows 11 installations, which are getting increasingly impossible to bypass. We need to see if this changes, and the constant influx of broken functionality drives users away from the Windows OS, or they are stuck with it for good.
Source:
via The Register
The community has managed to solve the issue by simply deleting the October KB5066835 package, alongside its September KB5065789 sibling, if the first package uninstall doesn't work. Software engineers have reported connection failures and HTTP/2 protocol issues impacting various development tools, including ASP.NET compilation processes and Visual Studio debugging functionality. Investigation has revealed that the problem originated in build version 26100.6899, with the root cause identified in HTTP.sys—a kernel-level Windows component responsible for managing HTTP traffic on local systems.
Update October 17, 15:30 UTC: Microsoft confirmed the issue and stated: "We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available."This issue stack for Microsoft's latest Windows 11 keeps piling up. On Monday, Microsoft accidentally broke the Windows Media Creation Tool (MCT) just a day ahead of Windows 10's end-of-life. Last week, the company started mandating Online Accounts for Windows 11 installations, which are getting increasingly impossible to bypass. We need to see if this changes, and the constant influx of broken functionality drives users away from the Windows OS, or they are stuck with it for good.

105 Comments on Microsoft Breaks Localhost with Windows 11 October Update, Users Forced to Revert
If the latter, a hosts file edit could serve as a temp workaround. Still a pretty wtf thing to do.
EDIT: Reading more, sounds like a HTTP protocol issue more. Confusing to say the least.
Let me know when a FOSS OS drives the development of graphics technology. Or has a unified integration of office software, device management, cloud services, user management, etc.
With a friendly smile,
Fred.
They are breaking more and more, more critical and so obviously easy to spot features that it feels like they truly are using chatgpt to run and analyze their build tests.
Which isn't a good idea if you ignore their feedback for months anyway
No idea why anyone who has the option / able to use LTSC wouldn't go that way, or at least demand payment for testing MS code for them all the time ?
Some end users had problems, but who cares, money is pouring in like rain.
As an example Firefox uses it to connect to itself.