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.
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.
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)
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.
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.
Every time they add new things to the OS, the old functionality is crushed under the weight of the new.
Link at bottom has some results about sudden, recent localhost failures
ref: https://kagi.com/search?q=windows+localhost+not+working&dr=2...