![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I think I know the cause of this:
If you're connected to a wireless network that has a web-based login portal (whether you type a login/password, or just click agree to the terms and conditions, they're both the same) while you're also connected to a wired, then that is probably the cause, and your workaround is to disconnect to that wireless network (or alternatively, just log in.)
Edit: or do this: https://stackoverflow.com/questions/43491861/how-to-disable-automatically-browser-opening-on-wi-fi-hotspot-connection-for-win
Explanation: Windows 10 has a new behavior to correct Windows 7's worse behavior of frequently prioritizing wireless connections over wired connections, while you're connected to both, and getting the interface metrics all wrong. Windows 10 prioritizes wired always, meanwhile it also has a feature so that if it detects a wireless network with a web landing, then it directs your browser to a Microsoft owned URL (I forgot the exact URL,) which is then supposed to be redirected by your wireless controller to its internal IP, therefore showing you the landing page. If you're on a wired network, then this will send the URL request over the wired network instead, which WILL be able to reach the outside internet without having to log in to your wifi. It will periodically do this to "help" you log in to a network opening your browser to that URL, which can then reach Microsoft's actual website, which subsequently redirects you to MSN.
This is a bug that Microsoft should fix, rather than send a representative who doesn't read your question enough to understand what qualifiers apply, has less knowledge than the asker, and can't read your post fully, and/or lacks the analytical capability to troubleshoot in order to answer the question, only to instead throw you off on random tangents based on some script he goes off of without any actual knowledge of the underlying causes so he could make a better suggestion.
Hope this helps, it did for me. After initially coming here and noticed nobody already had a fix, this occurred to me based on what I know about networking (I hold a CCNP and work on Cisco enterprise wireless) as well as Windows behavior, and how I was troubleshooting such a webauth page minutes earlier and was probably still connected to it. (See that, Microsoft? Not so hard.)
My opinion for fixing this is that Microsoft should by default put the wireless NIC to a sleep state if a path to the open internet is found on a wired connection (using the method Microsoft already uses to show that yellow triangle on the network icon if it determines no connectivity to its servers,) thus saving power and reducing the use of spectrum when you aren't actually using it, all while eliminating the chance of packets intended to go over wired instead end up going wireless. That, and this is a very commonly requested feature by enterprise IT teams for the reasons I mentioned. And of course, when you disconnect from wired, it wakes up the wireless NIC.
(normally I hate it when google points to either answers.microsoft.com or social.microsoft.com because the solutions Microsoft offers in these places are totally irrelevant to the issue at hand. (Seriously, a browser hijack? WTF? Why would anybody besides Microsoft create a browser hijack to msn? Is bing really that terrible that they now resort browser hijacks to get people to go there? Common sense should tell you that if Microsoft wanted to do that, then they'd force edge as the default browser, and prevent changes to the default search engine, just like they do with windows phone. Seriously, Microsoft shouldn't be giving scripts and canned responses to their representatives.)