Hi Everyone,
I've finally got my Windows 10 Pro installation up and running fairly smoothly. I have run into one problem, however, that I hope you can help me with. I am a web developer so I've setup a virtual instance of CentOS 7 (using VirtualBox) as my local testing server for my projects. It isn't anything too glamorous, but I have things setup so that 192.168.56.101 goes to the VM's web server. I've also setup a record in the Windows 10 host file to forward the domain "local" to this IP address. I'm able to SSH to this domain or IP with Putty. I'm able to access the VM's web server using the domain or IP with FireFox, Chrome, and Internet Explorer. However, if I try to access either the domain or IP address with the Edge browser, I'm told "Hmm, we can't reach the page." It's obviously something to do with Edge, but I'm not entirely sure what that might be. Anyone know what's going on?

Hi IntegrityDC,

Thank you for your question.

if the Window Edge could not open this page, the issue could be caused by compatibility, we could see all intranet sites to automatically open with IE by the following link:

https://technet.microsoft.com/en-us/library/mt270205.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Thanks for your reply, Jim. But I don't think it's a compatibility problem. Edge isn't even bringing up any content at all. Even if I go to a simple "Hello world" script, it can't find the page. Anyway, using IE11 isn't really a solution as I need to use Edge for browser testing for my clients.

exactly the same... I think that I have troubles with my SQLSERVER instance and I  almost lost my head on this...

Them I try Internet Explorer and the content renders on it...

Same Chrome, Firefox, etc. But EDGE....

Any possible reason?

I have this site on my developer machine with HOST file edited to render my test web site on my local IP.

By the way I'm using local IIS10. So all the services are running at the same machine.

Thanks you and join to IntegrityDC in this looking forward...

Maybe this is related to the "Localhost-Loopback" restriction of "about:flags"?

Possibly the browser identifies the IP as a local one and prevents loading withouch checking the setting?

NEatMaxworx,
Thanks for your suggestion. I had checked about:flags and verified that loopback addresses were allowed. It doesn't look like Edge filters out 192.168.* IPs because I can access my router and modem (192.168.0.1; 192.168.100.1)

It was a suggestion where I think MS should take a look into.

Most of our software is initial created for IE6-7, so I cant use FF or something else. Because MS pages dont let me download IE11 for Win10 (they didnt detect the OS), I have to use a virtual machine to connect to my local websites until MS fixes edge :(

When I first installed Windows 10, everything was working fine. However, I must have pulled down an update that prevents Edge from connecting to the IP address of the local machine. I can connect to anything else on my local network. I can also connect to localhost. However, I have software that specifically invokes the default browser with the local IP address (i.e. 192.168.1.101), and this fails. No other browser in my system fails with this.

Same problem here. Thank you Microsoft for making testing locally on a development PC in Edge impossible: that really helps us out! :-p

Well, I found the source of my problem. Apparently, Edge had decided to blacklist my local IP address. I found my IP address in a list under [HKEY_CURRENT_USER\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig]. I deleted the entry matching my IP address and it started working again. Hope this might help somebody else with the same problem. I have no idea why it even added the entry.

codewright2000, that's bizarre! I wish that would work for me, but no dice. Hopefully, it will help other folks though.

IntegrityDC, I have confirmed that the about:flags setting "Allow localhost loopback (this might put your device at risk)" will cause the same behavior, if unchecked. An additional thing you might want to check is to see if the same entry I listed above is in HKEY_LOCAL_MACHINE. Just spit-balling, but worth a check.

Thanks, codewright2000, but no luck. I had checked the about:flags->Allow localhost loopback before, and it's checked like it is supposed to be. Also there was nothing for Microsoft Edge in the HKEY_LOCAL_MACHINE registry entry. Thanks for the effort!

It worked for me.

We could access sites hosted on our local domain using Edge as soon as I removed my local domain name from:

HKEY_CURRENT_USER\SOFTWARE\Classes\

Local Settings\Software\Microsoft\Windows\

CurrentVersion\AppContainer\Storage\

microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig

• Marked as answer by Kate LiMicrosoft contingent staff, Moderator Thursday, August 27, 2015 2:04 PM
• Unmarked as answer by IntegrityDC Thursday, August 27, 2015 3:52 PM

I see that this is marked as an answer, but this actually doesn't fix the problem mentioned in the original post. "TabProcConfig" doesn't exist in my registry nor does the IP address or local domains that I can't access. Thanks for your input anyway, Zooper.

• Proposed as answer by JohnRom.com Thursday, August 27, 2015 7:19 PM
• Unproposed as answer by JohnRom.com Thursday, August 27, 2015 7:19 PM

Hi IntegrityDC,

If that, we suggest you run SFC /ScanNow in CMD to check if there are some corrupted files. Then post the result for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

No luck with the SFC /ScanNow utility. Is it safe to post the resulting log here?

Hi IntegrityDC,

You could post it to Onedriver and then shared it. Please dont forget to give a link for us.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Here are the results of the scan:

CBS Log

Hi IntegrityDC,

We could try to the following solution:

Please run gpedit.msc to open Group Policy Editor, then switch to Computer Configuration---> Windows Settings---> Security Settings ---> Local Policies---> Security Options, then enable "User Account Control: Admin Approval Mode for the Built-in Administrator account", after all restart Windows to take effect. Figure as below:

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim,

I am not sure what the policy change is meant to do, but it does not make me able to browse to local virtual machines, nor does it make the aforementioned registry keys appear.

I have the exact same problem as IntegrityDC, same setup as well. Neither the domain nor the IP address exist anywhere in the registry. Localhost loopback is enabled. Works fine in any browser I try, except Edge. It responds so fast, it does not even seem to be trying.

Makes it incredibly difficult for me to fix an Edge-specific bug in one of my web applications. I was really looking forward to taking Edge for a spin but I've been stuck since day one.

I have the same problem.

Windows 10 Pro, running Wamp on local machine, having set up a virtual host-file in the Apache-config, and modified the hosts-file in Windows to match.

I can reach my local domains (I only use the name it self, not TLD-ending, or any ending at all) via Firefox, Opera, Chrome or any other browser (including IE 11).

Seems this is a problem with Edge being an App, instead of a desktop-program (for some reason).

The interesting bit is that I _can_ reach localhost - that's not a problem (but due to the setup, it won't really help me view my sites, because if I go via localhost/domain, it breaks the pages internal structure).

This needs to be fixed.

Just to follow up on these instructions provided by Jim, as expected, this change had no effect.

Hi IntegrityDC,

Did you mean the solution didnt work for you?

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Jim,

That is correct. Adjusting the setting in Group Policy had no effect. It did not work.

Hi IntegrityDC,

If not, we suggest you open a case to Microsoft to get help.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim