
- #MS EDGE CHROMIUM DOWNLOAD MSI INSTALL#
- #MS EDGE CHROMIUM DOWNLOAD MSI UPDATE#
- #MS EDGE CHROMIUM DOWNLOAD MSI WINDOWS 10#
- #MS EDGE CHROMIUM DOWNLOAD MSI SOFTWARE#
I’ve attached the transform itself to the bottom of this article. You can translate that into what’s needed for Intune (as a Win32 app), ConfigMgr, or MDT yourself.

Msiexec.exe /i MicrosoftEdgeEnterpriseX64.msi TRANSFORMS=”MicrosoftEdgeEnterpriseX64.mst” /L*v %temp%\msedgeenterprise_installer.log Now you can deploy Edge with that transform, using a command line like so: On the Transform menu, click Generate Transform… and save the new MST file, e.g.Press Enter to finish editing the cell.It should look like this: installerdata=" Be sure to retain the closing quotation mark. Near the end of the text, delete the existing encoded JSON following installerdata= and replace it with the new property name in brackets.Double-click the Target cell for the BuildInstallCommand action to make it editable.Select the CustomAction table, and locate the BuildInstallCommand action.

This code will be applied during deployment and saved as the installation’s master_preferences file by the installer. Set the Property to MASTER_PREFERENCES, and set the Value to your URL-encoded JSON.

#MS EDGE CHROMIUM DOWNLOAD MSI INSTALL#
(Both Chrome and Edge use Active Setup to do their per-user stuff.) OK, how do I provide these at install time? I could prove that the Edge installer never tried to read the master_preferences file (regardless of where I put it), so there had to be another way. Through additional reading, I discovered that there are two different types of settings in master_preferences: Those that are processed once at install time, and those that are processed for each user when they log on for the first time. OK, but does Edge support the same master_preferences mechanism? According to the Edge docs, it does. And that documents a “do_not_create_desktop_shortcut” shortcut that sounded promising. The official Chrome docs pointed to a master_preferences file that links to a Chromium page that talks about the options. Since the new Chromium-based Microsoft Edge is based on the same engine as Chrome, the first task was to figure out how Chrome does this.
#MS EDGE CHROMIUM DOWNLOAD MSI WINDOWS 10#
But since I was getting tired of cleaning these off as I deployed Windows 10 devices using Windows Autopilot (it gets really messy after a while as you end up with several copies of the same app), I decided I would try to see what it would take to prevent that from happening.
#MS EDGE CHROMIUM DOWNLOAD MSI SOFTWARE#
I really don’t understand why software installers still create desktop shortcuts, especially when that desktop is being synced to the cloud using OneDrive. Or more accurately, “a crash course into the inner workings of modern browser installers (which really aren’t that modern).”
#MS EDGE CHROMIUM DOWNLOAD MSI UPDATE#
UPDATE 6: See my updated post for an easier way.
