I've been having a similar issue too. Edge says "can't reach this page." Windows search says "We can't connect to the web right now." But Edge can't see Bing, Google, Yahoo, or any other website I try to hit.
And yet, I launch Chrome. I can surf like there's no tomorrow.
Outlook? Connects, sends, and receives just fine.
Dropbox? Sure. No problem.
Adobe Creative Cloud? Just updated two apps.
Save files to my NAS? Or print to my network printer? Yep. Sure can.
And yet, here I sit with Chrome open on one monitor typing this entry, and on my other monitor sits Edge "Hmmm"ing to itself like an idiot.
This is TRULY a remarkable achievement by Microsoft. They've managed to kill their own browser and search system, but everything else just keeps going. Bravo!!
Seriously though, anybody have any luck taking care of this issue? I'm poking fun at Edge by talking about Chrome, but the truth is, I don't like Chrome. Or FireFox, or Safari or any of the others. I'm a Microsoft boy. And honestly, I I don't care for the Apple-fication that I see going on. If I want a dumb toy with pretty colors and nice soft edges, I'll by a Mac. But I can't understand for the life of me how Microsoft has lobotomized Edge and Cortana, yet everything else still sees the internet just fine. Can even do a old fashioned (and not very hip) ping (see below for the proof)... But no Edge love!
Interestingly enough, when I go into the Control Panel (was it really necessary to bury it?) and check out my Network and Sharing Center, I'm informed that "You are not connected to any networks."
Funny that, really. All those pages I sent to my network printer must be in my imagination. As, obviously, this post because since I clearly don't have a network connection, I can't possibly be typing this right now into Chrome.
No issues found by the troubleshooting system. Just can't connect through Edge or Windows Search.
C:\Program Files\IIS\Microsoft Web Deploy V2>ping
Google
Pinging
Google [74.125.225.18] with 32 bytes of data:
Reply from 74.125.225.18: bytes=32 time=44ms TTL=54
Reply from 74.125.225.18: bytes=32 time=48ms TTL=54
Reply from 74.125.225.18: bytes=32 time=41ms TTL=54
Reply from 74.125.225.18: bytes=32 time=43ms TTL=54
Ping statistics for 74.125.225.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 48ms, Average = 44ms
C:\Program Files\IIS\Microsoft Web Deploy V2>