Forum Discussion
Official Download links for Microsoft Edge Stable Enterprise
HotCakeX <em>"You can read my comment here. [M]ost of your assumptions are wrong because I tested it myself on Windows 10 pro. [Y]ou don't need enterprise edition of Windows."</em>
If you are referring to the sentence ["[T]he Enterprise version is not intended for consumers, and installation of the Enterprise version of EgdeChromium might or might not update normally after the initial installation if you are running Windows 10 Home or Windows 10 Pro rather than Windows 10 Enterprise."] then I think you might have misunderstood the issue I tried to raise.
The issue I raised is not whether MicrosoftEdgeEnterpriseX64.msi will or will not initially install successfully on Win10 Home or Win10Pro (it will and does), but whether EdgeChomiumEnterprise installed through that msi will or will not "update normally after the initial installation if you are running Windows 10 Home or Windows 10 Pro rather than Windows 10 Enterprise".
There is a difference between the two issues. At this point, the former can be tested (we've both done so), but the later cannot be tested because there have been no updates to EdgeChromiumEnterprise Version 79.0.309.56. If I'm wrong about that (that is, if there have been updates to EdgeChromiumEnterprise Version 79.0.309.56 and you've tested post-installation upgrades on a Win10 Home or Win10 Pro consumer-side installation), I'd be interested in learning about your experience with post-installation upgrades.
The reason I flagged the issue is that Enterprise customers typically do not allow auto-update of software deployed in the Enterprise, but test internally before releasing an update, and, for that reason, Enterprise releases of software are sometimes designed to accommodate that practice by requiring manual intervention to install the update.
I don't know whether or not EdgeChromiumEnterprise will auto-update in normal course (which is the expected behavior for EdgeChromium installed on Win10 Home and Win10Pro) or require manual intervention (which is often the behavior of software deployed on Win10 Enterprise). That's why I said "might or might not update normally", and I stand by that observation, absent an advisory from Microsoft to Enterprise customers, and that's why I cautioned about the possibility.
Another caution to anyone running Win10 Home or Win10 Pro and planning to install MicrosoftEdgeEnterpriseX64.msi:
My experience with installation (hard metal, not VM or Sandbox) is that MicrosoftEdgeEnterpriseX64.msi installed correctly, but did not uninstall completely. Specifically, the installation removed EdgeClassic from Windows menus (as expected) but the uninstall did not completely reverse the process, probably because the uninstall did not completely reverse the changes made to Win10 during the installation process.
What I ended up with after uninstall was an instance of EdgeClassic that did not run normally. EdgeClassic was identified as LegacyEdge, and when the icon was clicked, nothing happened. Opening LegacyEdge required a right-click on the icon, followed by a click on a popup menu item "Open in New Window". When that routine was followed, EdgeClassic opened and seemed to run normally.
I don't know what your experience was after uninstall of MicrosoftEdgeEnterpriseX64.msi, but I'd be curious to know if yours was similar or different. My test computer is a Dell Inspiron 3583 running Windows 10 Home 2004 Build 19041.1 (vb_release) -- that's the current Windows Insider Slow Ring build, and (as I understand it) the pre-release build, or close thereto. You might get a different result with 1909.
My opinion (and it is an opinion and no more) is that it is usually a mistake to mix and match Consumer-track software with Enterprise-track software. The two tracks are different (Win10 Enterprise has numerous enhanced features, primarily security features, and Enterprise-track software is sometimes subtly different than Consumer-track software to accommodate those enhancements) so you might not have a satisfactory experience trying to install, run and uninstall software intended for one track in the other track.
My best wishes for the New Year.
Likewise 🙂