(It may be just as unclear a year from now, for even though Edge now boasts a share of nearly 7%, much of that growth stemmed from Windows 10's gains, not the browser's. Although there was little downside to the radical shift to Chromium - Internet Explorer had long been on legacy life support and Edge was at a near-death 4% user share - it's vastly unclear whether the switch to Chromium will save Microsoft's browser bacon.
With that said, here's a Registry file that should get rid of the problematic policies in the HKLM hive (it's easily modified to work with any HKCU-set policies): Windows Registry Editor Version 5.More than a year after Microsoft waved the white flag, saying it would scrap Edge's rendering engine and replace it with Blink, the engine that powers Google's Chrome, the company has now delivered its reborn browser to the public.īut the result? That's still up for grabs. Some other policies don't seem to exist anymore at all (like the ones about Cloud Print). It turns out that a bunch of policy entries that I had applied via the Registry, mostly copied over from a Chrome setup, do not work in Edge anymore, and at least one of these things was making it fail to launch first of all, the list of force-installed extensions is now 1-indexed rather than 0-indexed, and second, some policies were re-named to have more Microsoft-relevant names (like using "Favorites" instead of "Bookmarks", "InPrivate" instead of "IncognitoMode", "SmartScreen" instead of "SafeBrowsing", and "SurfGame" instead of the old "DinosaurEasterEgg"). I'm worried about restarting the copy of Edge I'm running on at home because of this issue I have not seen any mention of this issue in this subreddit, in recent Google search results, or on WinAero. I had actually uninstalled Chrome and Brave and am now posting this from Firefox. Whenever I click the icon in the taskbar, Windows seems a bit busy but then the browser does not launch, and there is no "msedge.exe" in the Task Manager I re-ran the Microsoft Edge installer and the same thing happens. I'm at the latest version of Edge, and the three computers at my office that I installed it on have this same issue all of them are running Windows 10 version 1909 fully patched (I realize that 2004 is out now and I will update soon). EDIT: I fixed the problem, and a partial solution is below.
0 kommentar(er)
