Windows keeps becoming more and more worse and bloated every month. This month's update bumped up the install.wim by 400MB! And last month's update added a similar amount of bulk. It's insane how much junk Microsoft keeps adding to the OS, whilst breaking core functionality.
I'm shocked there's not more traction on this post. Breaking localhost is almost unthinkable to me. Of all the things network unit testing should cover, that's pretty close to the top.
Link at bottom has some results about sudden, recent localhost failures
working for several years, today localhost not found
after GUI reboot attempt
localhost and 127.0.0.1 should be the same,
it seems strange they shows different results.
wusa /uninstall /kb:5066835 (restart)
wusa /uninstall /kb:5066131 (restart)
wusa /uninstall /kb:5065789 (restart)
Windows keeps becoming more and more worse and bloated every month. This month's update bumped up the install.wim by 400MB! And last month's update added a similar amount of bulk. It's insane how much junk Microsoft keeps adding to the OS, whilst breaking core functionality.
Agreed, yet I don't see people rushing out to buy GNU/Linux powered laptops at Media Markt, because there aren't any.
Every time they add new things to the OS, the old functionality is crushed under the weight of the new.
I'm shocked there's not more traction on this post. Breaking localhost is almost unthinkable to me. Of all the things network unit testing should cover, that's pretty close to the top.
Same. The incident calls I'm on this morning agree too
Link at bottom has some results about sudden, recent localhost failures
ref: https://kagi.com/search?q=windows+localhost+not+working&dr=2...It seems like it only concerns IIS (and/or SChannel), and only for HTTP/2 (and maybe 3?). I use apache and openssl and doesn't have any issue.
I'm more interested in how this update causes the issue. What is the mechanism?