I'm glad I found this thread as I too thought IE 11 was not going to be in Windows 10 release version. I use a local proxy that I will never give up. My other browsers have zero problems with connecting through my local proxy. Spartan cannot do so even though it has the settings to set up a local proxy connection. It lets me set up my local proxy connection but then says it can't connect and suggests the problem is likely my firewall. Why are those settings there if it can't use them?
Based on this craziness, I probably will simply stay with Windows 8.0 Pro. I am doing Win 10 Preview on Hyper-V virtual machine to see if I will want to upgrade to it but evidently it would be a downgrade if Spartan is so badly crippled that it can't connect to a local proxy. My browsers of choice are all Gecko based so I seldom use IE and wouldn't use Spartan much at all but I would not want Windows 10 if IE is hidden and its future is uncertain as IE has to be used at first setup to download Fx or Pale Moon and occasionally IE has to be used on Microsoft sites and my airlines site and some others that are setup only for IE. My airlines has a new site in beta and it works only with IE as does its current website. Microsoft is cutting its nose off making the future of IE 11 on Windows 10 uncertain since it wants everyone on Windows 10 and that won't happen if only Spartan and no local proxy is available.
This is the first I have heard that browsers like Fx, Sea Monkey, Pale Moon, etc are not standards compliant. They have been always standards compliant yet they have no problems with a local proxy connection. Spartan should have no problems either.
Firefox, Chrome, etc.. are standards compliant, but they are also backwards compatible. Edge is not.
IE11 is not "uncertain" It will be in WIndows 10 for the foreseeable future. It just won't be the default browser, by default.
And i'm sorry, but any company making new sites that require IE today are the ones cutting their own throat...
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 !!!.
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 !!!