Windows 10: Edge browser can't access LOCALHOST type of IP addresses (build 10122

Hi there

For the foreseeable future people will want web interfaces on some local applications. Presumably Edge *Might* (I say might because I don't know and am guessing) have a problem too with LOCAL INTRANET sites. This if it were to be true would be a big no-no for a lot of companies who have local intranet applications.

I'm 100% in favour of Ms or anybody else making / developing robust secure applications but a lot of businesses tend to react for all sorts of reasons - a lot of them totally valid - much more slowly and re-writing a lot of their standard applications isn't usually worth it. Over time new applications will get rolled out but this will take years -- I know a quite large Oil company that's still using some Windows NT servers !!!.

Cheer
jimbo

 

The problem is localhost only, not local intranet sites. Yes, local intranet sites might have backwards compatibility issues that require IE for backwards compatibility, but it won't be that they can't access them.

 

Note: You can fix this via executing the following command-line:

~C:\WINDOWS\system32>checknetisolation LoopbackExempt -a -n=Microsoft.Windows.Spartan_cw5n1h2txyew

Microsoft will also allow this to be set via an about:flags setting in a future build.

 

Make sure you run the command prompt as administrator first.

 

Heya,

For anyone not able to access localhost now that it is Edge, here is the fix that worked for me:

CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe

I hope they come up with a plan soon so localhost can be utilized with Edge.

Hope this helps

Dragon

 

Confirming: Edge browser is now able to browse to localhost and my local IP when directly-typed into address field after:
Run the command prompt as administrator, then execute:
CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe

Thank you TonyPreston, Mystere and Dragon !!!