I installed Fiddler (V4.6.0.2 - August 17 2015) on Windows 10 RTM (build 10240) x64 en-US.
Since then, Edge is no longer working (error "Hmm, we can't reach this page.") unless Fiddler is running.
Note that Firefox , Chrome and IE11 do not have this issue, they are OK when fiddler is NOT running.
I restarted the PC several times,the problem is still present.
I checked the ProxyServer key in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings : the key is only there when fiddler is running.
Also I cannot sign in Windows Store or Groove Music unless Fiddler is running AND I've enabled the apps in "App Container Loopback Exemption Utility" (WinConfig button).
Note #1: I have a warning "Orphaned Exemption Record Found" when launching WinConfig, see attached screenshot.
Note #2: In HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings, I have this key : _FiddlerDirectWrite = "BuggyWinShutdown at 01:07:59 2015-09-17". I don't know if this is normal.
Note #3 : I searched every location in registry with value "8888" ( fiddler proxy port) when Fiddler was running then I closed Fiddler and looked at the registry locations again.
I found 8888 in those 2 keys below, so I deleted the keys, restarted the computer but the issue is still there.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iphlpsvc\Parameters\ProxyMgr\{E6EFF353-402B-45F2-8D72-E8B7FA394DB5}]
"StaticProxy"="http=127.0.0.1:8888;https=127.0.0.1:8888"
"ProxyBypass"="<-loopback>"
"LastUseTime"=hex(b):8a,ce,43,c6,ba,f0,d0,01
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iphlpsvc\Parameters\ProxyMgr\{F9D45E1B-22AA-4CAA-BDA0-DA414B44C2A5}]
"StaticProxy"="http=127.0.0.1:8888;https=127.0.0.1:8888"
"ProxyBypass"="<-loopback>"
"LastUseTime"=hex(b):8a,ce,43,c6,ba,f0,d0,01
From HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles, I can see that:
{E6EFF353-402B-45F2-8D72-E8B7FA394DB5} is "fortissl" : Fortinet SSL VPN that I use to connect to my company network.
{F9D45E1B-22AA-4CAA-BDA0-DA414B44C2A5} is "Network" : Ethernet connection
After I ran fiddler, the key {F9D45E1B-22AA-4CAA-BDA0-DA414B44C2A5} was re-created.
The other key {E6EFF353-402B-45F2-8D72-E8B7FA394DB5} would probably have been re-created as well if VPN connection was established when I ran fiddler again.
Fortinet SSL VPN is working fine, I installed it right after Windows 10.
I had no issue with Edge or Windows Store until I installed Fiddler 4.
21 Answers, 1 is accepted
The only change Fiddler itself makes is to change the proxy settings to point to itself while it runs; those settings are reverted when it exits.
The "BuggyWinShutdown" registry key tracks whether or not Fiddler ever had to directly overwrite the system proxy settings because the Windows proxy API failed due to a Windows bug (see https://connect.microsoft.com/IE/feedback/details/838086/internet-explorer-10-11-wininet-api-drops-proxy-change-events-during-system-shutdown). The presence of this key simply indicates that Fiddler took this action and doesn't indicate a real problem.
The best way to examine your proxy settings is to use IE's Tools > Internet Options > Connections > LAN Settings; this uses the proper API that is used by the browser.
If Edge is the only browser with problems and IE works fine and Edge works when Fiddler is running, this is a strong indication that the problem is the system's firewall configuration. You might try disabling the Windows Firewall service (using services.msc) temporarily and confirm that this is related.
Regards,
Eric Lawrence
Telerik

The issue was not related to firewall, it happened because the DNS client service (Dnscache) was disabled.
This is caused by FortiClient VPN SSL, Dnscache is set to disabled state when VPN is connected and it should be set to Automatic when VPN is disconnected (after 1 minute it seems).
So it look like that VPN did not shut down properly and did not restore Dnscache service (maybe I shutdown the computer while VPN was connected).
I found something on Fortinet KB, I may try this: http://kb.fortinet.com/kb/documentLink.do?externalID=FD36228
But at least, I know how to repair this issue now, check that DNS client service is not disabled.
It is strange that only Edge is affected, others browsers (IE, Firefox, Chrome) are OK when Dnscache is disabled.

Hello
I just have the same problem...
After using fiddler, all my UWP applications can't connect to any network.
Such as Edge, OneNote, Store, Weather, etc..
And I'm pretty sure my DNS Client service is running, my proxy settings are all disabled.Both windows settings and IE settings.
Can anyone tell me what happened and how to fix it ? Thanks a lot.
I've googled a lot but only got this thread.
Ps.English is not my native language, so sorry for my bad English...
Hello
I've disabled all proxy settings and tried disable windows firewall, doesn't work...
Edge and other UWP apps still can't connent to Internet.
IE Firefox works fine.

I'm sorry to hear that but as I wrote, in my case Fiddler was not the problem, it was some kind of solution as Edge was working when Fiddler was running.
So Fiddler did not break anything, I was wrong, I would have edited the thread title if I could.

In my case I only installed Fiddler, and as you said, when Fiddler is running Edge and other apps works fine.
Seems I disabled proxy, but actually they are still affecting my apps? Don't know.
It's weird...
My platform: Windows 10 build 10240 x64 zh-CN @ Surface Pro 3 i5/128G
Screenshots are in Chinese..If someone needs translate I'll do that later tomorrow

I'm pretty sure that Eric Lawrence is right, if Proxy Server (in IE's Tools > Internet Options > Connections > LAN Settings) is disabled as it should be when you leave Fiddler then the problem is not Fiddler, you have an issue with Windows or third party software.
You can also check "ProxyServer" in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
The value exist when Fiddler is running, it is deleted when you close Fiddler.

Anyway, thanks a lot ~
I've checked almost everything...and still don't know what caused my problem.
I'll reinstall my whole system and try to figure out what is affecting.


Chrome doesn't use AppContainer, and IE only uses it if you turn on Enhanced Protected Mode. What you're describing does sound like a bug in the firewall configuration-- either the third-party one or the one that comes with Windows itself. If you can share the exact text of the error page you see in Chrome, it may shed some light.
Beyond disabling McAfee's firewall, you may want to verify that the Windows Firewall configuration isn't interfering.
Regards,
Eric Lawrence
Telerik

Unfortunately, you'll probably want to talk to Microsoft Support about this, assuming the suggestion of examining your Windows (or third-party) Firewall settings doesn't bear any fruit.
Regards,
Eric Lawrence
Telerik

If you are on Win 10 (Edge, Store, One Note, etc makes it sound like you are) I discovered that Fiddler will set the SYSTEM PROXY SETTINGS.
Goto Start > Settings > Network & Internet > Proxy and turn it off.
NOTE: The next time you start fiddler it will turn it back on! Exiting Fiddler does not seem to turn the SYSTEM PROXY back off. :(

Exiting Fiddler normally does, of course, change the system proxy settings back. The one exception to that is if the exit of Fiddler occurs during the system shutdown. With IE10, Microsoft shipped a bug (which they have yet to fix) whereby system proxy changes at shutdown are ignored.
Restarting Fiddler will detect that the proxy settings were already pointed at Fiddler such that exiting normally (not during shutdown) will clear them.





It seems like Windows 10 firewall is hard-coded to block access from managed apps to the localhost.
No matter what firewall exception I add, as soon as I enable the proxy to any localhost port (Fiddler or any other app running locally), none of Windows managed apps can access the Internet. Store, Maps, Mail, Edge, etc. - all get a "connection timeout" error.
The ONLY solution is to (1) turn off the Windows Firewall and (2) then stop the MpsSvc service.
WTF Microsoft!

Looks like a case of RTFM. A loopback exemption is needed for metro apps:
https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureFiddlerForWin8