![\"Windows](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2025\/10\/1760883608_994_960x0.jpg\")
<\/p>\n<\/p>\n
This is a \u2018total disaster\u2019<\/p>\n
NurPhoto via Getty Images<\/p>\n
Republished on October 19 with a second confirmation from Microsoft that its new update breaks Windows and an emergency fix is now due.<\/p>\n
Just days after Microsoft killed security updates<\/a> for 500 million Windows 10 users, there\u2019s bad news for Windows 11 users as well. A new, mandatory security update is a \u201ctotal disaster\u201d and an emergency update has suddenly been confirmed.<\/p>\n The warning comes courtesy of Windows Latest<\/a>. Microsoft admits that Windows 11 KB5066835 breaks localhost connections, \u201cwhich means locally hosted apps can no longer connect to your network.\u201d But there are also multiple installation failures and bugs blocking peripherals and accessories from working properly.<\/p>\n Users going online to fix update issues are being warned to stop. \u201cDon\u2019t try your luck with internet solutions. They don\u2019t work.\u201d Instead, wait for the update. <\/p>\n Forbes\u2018Phased Out\u2019\u2014Google Confirms Bad News For All 3 Billion Chrome UsersBy Zak Doffman<\/a><\/p>\n \u201cMicrosoft says it\u2019s rolling out an emergency patch that should address localhost-related issues in Windows 11 24H2\/25H2, but remember, the hotfix could take longer than 48 hours to show on affected PCs.\u201d Meanwhile, Microsoft says \u201caffected users should check for updates and reboot their PC, even if they do not see any newer updates listed.\u201d<\/p>\n Windows Latest has found a \u201cregression in the kernel-mode HTTP server (HTTP.sys). When a browser or app tries to connect to HTTP\/2 to services hosted on 127.0.0.1, HTTP.sys mishandles the HTTP\/2 handshake\/frames and resets the connection.\u201d<\/p>\n The website warns that this is significant \u201cbecause the Windows update broke IIS, which affects anything behind HTTP.sys. Windows is designed to handle 127.0.0.1 requests by loading TTP\/2 session in the kernel, which then sends the request to the IIS worker, ASP.NET Core Module or your app.\u201d<\/p>\n Per The Register<\/a>, \u201cMicrosoft had yet to acknowledge the issue. Users report mixed results when trying to reinstall the patch or roll forward to newer builds. The problem appears to vanish on clean installs of Windows 11 24H2, suggesting that the error stems from a conflict in how the update interacts with existing system configurations, rather than being a universal bug.\u201d<\/p>\n Separately, accessory failures affect \u201csome Logitech peripherals\u201d and \u201cmouse and keyboard not working in WinRE (Windows Recovery Environment).\u201d<\/p>\n As ever, there are a number of green-fingered workarounds for these various issues, but for almost all Windows 11 users, the reality is you\u2019ll await the emergency update if you\u2019re affected. It\u2019s likely that will be here quickly, likely within a day or two.<\/p>\n After initially admitting the \u201clocalhost-related issues,\u201d Microsoft has now confirmed<\/a> the WinRE (Windows Recovery Environment) issues as well. <\/p>\n Per Windows Latest\u2019s<\/a> update, \u201cthis month\u2019s update renders WinRE (Windows Recovery Environment) useless because a bug blocks the mouse or keyboard from working. This means you cannot navigate WinRE. It\u2019s one of the issues that originates from Windows 11 KB5066835, which also breaks localhost.\u201d<\/p>\n In practice, \u201cthe issue makes it impossible to navigate between different options within WinRE. For example, if you\u2019re on WinRE and want to troubleshoot the OS or reset Windows, you can\u2019t do that because the cursor will not work, and keyboard buttons will not respond.\u201d Not great news for the millions of Windows 10 users with fresh upgrades.<\/p>\n Windows Latest does have a workaround, which you can find on the website. It comes with a major health warning though, and so is not reproduced here. The fix (before the real fix) means playing with system files, and if you get that wrong \u201cyou can make Windows unstable or stop it from booting. Do it carefully and at your own risk.\u201d<\/p>\n If you\u2019re still running Windows 10<\/a> and reading this with a sense of relief, just make sure you\u2019ve updated your PC with the last ever security fixes you will receive unless and until you enroll in the 12-month ESU program to keep Windows 10 until 2026.<\/p>\n ForbesMicrosoft Suddenly Offers Windows 10 Update In Store\u2014Buy NowBy Zak Doffman<\/a><\/p>\n