[syklep]

This is frustrating. More than once, issues with Edge not opening or not working prevented me from browsing/installing another browser. Without IE, I would have been SOL. Just now realizing there are probably baked in powershell methods like winget.

[anenefan]

I take what I saw of Edge's behaviour in 2015 when Win 10 was being installed on retail laptops, as a good "clear" hint where M$ plans to eventually head.

I was asked as a favour to look at a laptop that was having "issues" (ultimately resolved by uninstalling Mc Afee which was preventing a network connection via a usb dongle - other normal paths familiar in earlier M$ OSes to investigate / resolve I noted had been locked down - which M$ I heard later, wound back.) This laptop was only two weeks from purchase, and relatively untouched and I arrived not planning to do anything drastic but resolve a connection issue.

I expected Edge to work with caveats, what I wasn't expecting, would be best described as a hidden "disallow" list where the action was simply printing a white page, no error, no nothing. Not even Abode's flash. Of course it remained a mystery to me for an hour or so, until Firefox was installed.

The problem was with installing a new browser was searching for it on the web if one hadn't brought a copy. Edge iirc wasn't doing that well either, as I'd had no luck trying to download a couple of good tools I resort to dig deeper into what setting Mc Afee had altered.

Eventually I realised M$ had not removed IE, it worked as expected, which allowed me to find the latest version of Firefox.

[ndegruchy]

Curl (like, the real deal curl.exe) is also available on Windows 10 since... a while.