How To Install Microsoft Edge For Mac
Malka Crickenberger
I was trying to use google meet and it said that i need to update my Microsoft Edge browser. I downloaded the new update and installed it but it showed the error: "Failed to cache the downloaded installer 0x8007......" i don't remember the rest.
I searched up the microsoft support page only to get more confused so i tried clearing my temporary files and tried installing it again and it is still showing error but a different one "There was a problem downloading the required files. Error: 0x80070070"
Check your VPN. If you received a 403 error and are using VPN, the VPN might be blocking Microsoft Edge from downloading correctly. Try disconnecting from the VPN temporarily while you download and install Microsoft Edge.
If you or your organization block certain web sites, make sure to allow , from which Microsoft Edge checks for updates, as well as *.dl.delivery.mp.microsoft.com, from which Microsoft Edge can be downloaded during an initial install or when an update is available. For more details, see Allow list for Microsoft Edge endpoints.
Select Open Microsoft AutoUpdate on the About Microsoft Edge page, or open Microsoft AutoUpdate manually. If the system detects a problem, follow the on-screen instructions to resolve it. Also, see Update Office for Mac automatically.
On the About Microsoft Edge page, select Open Microsoft Update or open Microsoft AutoUpdate manually. If the system detects a problem, follow the on-screen instructions to resolve it. Also see Update Office for Mac automatically for help with Microsoft AutoUpdate.
Do I create an App Layer and follow the Google Chrome recipe, using the enterprise offline MSI-installer and GPOs? Or do I need to install it into the OS Layer since it possibly is connected to some operating system funcionality?
However, we had a couple of auto-updates slip into the UPL and this caused side-by-side issues for Edge/Chrome because to the system there were 2 different versions installed (1 in UPL, 1 in OS/Platform). Since these didn't have their own App Layer there was no way to purge the UPL data regarding these applications. We ended up separating out Edge/Chrome into their own App Layers in order for the ELM to actually generate a repair script in case this happened again.
It should be worth noting that current and future builds of Windows 10 include Edge (20H2) so may be simpler to retain in the OS Layer, the downside is that it does not update via windows update. It uses the same update mechanism as Chrome (launch Edge and check version via about)
I currently have it as an App Layer (Elastic) along with seperate App Layers for Chrome and Firefox. Problems can arise with User Layers if the users are able to update and then a subsequent layer update is made, the msedge exe references the wrong version folder. User Layer repair does not resolve the issue when this occurs.
At this point, the only recourse I can come up with is to remove it from the OS layer, and all subsequent layers that were created with the problematic OS Layer as a base. I'll leave the Chrome layer untouched and let it be used as my AL for Chrome and Edge.
We ran into the exact same issues as well, which is why it prompted us to separate it out as I described earlier. I then ran the repair json on all users after the Edge layer was created. This fixed all of our side-by-side issues. However, I now do a quarterly update and my only frustration is that the first time someone opens Edge after the update, it is in a broken state until the user closes Edge and re-opens it. I've also tried running the repair json and its the same behavior. The broken state also doesn't come back after a reboot, its only when I do the next update.
I had a ticket in with Citrix and if you use User Layers, you cannot App Layer browsers whatsoever. I told them that their CTX article didn't make mention to that but they said the internal team confirmed that browsers cannot go in App Layers if you're planning to use User Layers. I've started migrating my users and so far no issues with the browsers being installed in the User Layer with updates enabled.
We use Microsoft Configuration Manager and via Software Center Self-Service users install it themselves if they require it. You could also remotely install it but make sure however you're pushing the installation that it can detect a user session or else it wont install in their User Layer.
Microsoft decided to complicate things this month with the April patching and actually forced you to install Edge Chromium in the OS Layer. I ended up renaming both folders (Edge/EdgeUpdate) in C:\Program Files (x86)\Microsoft to Edge.OS_Layer and EdgeUpdate.OS_Layer as well as disabling all Edge Update services/removing the Task Schedule auto-update tasks in the OS Layer. This has worked well and users are still able to install Edge Chromium into their User Layers and update it without issue.
This is actually getting pretty ugly now, with the latest Windows 10 updates now add Edge into the OS Layer and uninstall is not supported (only presented option is repair presumably as legacy edge is also removed) this means everytime it gets reinstalled you need to rip it out via command line.
Yes, agreed it is ugly but as mentioned above the folder rename and disabling of services, etc in the OS Layer has worked for me without causing any issues to my new installs of Edge Chromium as well as users continuing to auto-update the version they have installed in their User Layer.
As per my experience, never install an application that update itself (auto update) in OS layer or you will waste a lot of time repairing other application layers. Tipicaly, those applications are antivirus software, Edge chromium, Chrome, every software you cannot block from self updating.
Now I'm stuck with Edge Chromium working partially, even if I disable Edge App Layer I used to work with (example : Outlook links won't open anymore, it tries to open with an old Edge browser, before Chromium).
Then run from terminal in the folder you saved .deb file:
ar xf file.deb name file here is just for the example.
Then extract the data.tar.xz archive. Inside the data.tar.xz is the program.
There should be a script microsoft-edge-stable that is needed to launch the program.
Inside the bin folder should be the executable file and in usr/share/application should be the desktop file.
Please note that the Flatpak instructions in that tutorial install the BETA** version of Edge, not the newly released stable version, and tie to the beta channel of Flathub, not the stable channel of Flathub.
The developers of the Edge Flatpak have not yet released a wrapper for the stable version of Edge. I've been in contact with the developers in the last few days, and there is going to be a delay in releasing a Flatpak for the stable version because of a delay in development of an upstream element relating to Chrome. I don't have any information on when a Flatpak for Edge will be released into the Flathub stable channel.
Because Edge (like Chrome) updates every few weeks, manually updating is likely to become tedious, sooner rather than later. I would consider waiting until a stable version of the Flatpak is released into the stable channel of Flathub instead of trying to do a roll-your-own installation.
(1) Edge-Linux Stable was released by Microsoft this week. Microsoft offers Edge-Linux in .deb and .rpm, which align with the package formats used by Microsoft's enterprise/business partners (Canonical, SUSE, RedHat and so on), but which leave Arch-based and independent distributions (e.g. Solus) out in the cold. Microsoft has declined (based on the best information available to me at this time) to wrap Edge-Linux as a Flatpak. Microsoft's attitude toward eventual release of a Snap is unknown, although more likely a Snap than a Flatpak because Snaps are pushed by Canonical, a Linux partner of Microsoft.
(2) A community-based project is in the process of wrapping Edge-Linux as a Flatpak, with the goal of including Edge-Linux Stable in the Flathub stable channel going forward. The project is stalled at this point because of an upstream issue involving both Edge-Linx and Chrome. I don't know when that issue will be resolved, so I don't know when Edge-Linux Stable is likely to be released into the Flathub stable channel. A Github discussion of the issue is ongoing. The project developer will post developments in that discucssion.
(3) Edge-Linux is available in BETA on Flathub's beta channel through the community-based project at this point, and will continue to be available until Edge-Linux Stable is released into the Flathub stable channel. Anyone who wants to install Edge-Linux Beta can do so following the steps in this tutorial. My experience with the Beta version over the last six months is that Edge-Linux Beta is very stable, running without issues internally, although some Solus functionality (e.g. the ability to pin the app) is not available using the Flathub beta channel.
(4) It is possible to install Edge-Linux Stable locally using algent's technique described above, or by packaging Edge-Linux Stable as a private .eopkg in a local repository for your personal, private use only. If you elect to develop a private .eopkg, please do not publish or distribute the package on this forum because doing so may embroil Solus in licensing issues. Both "roll-your-own" solutions will require a level of expertise to set up an maintain, and both will entail frequent manual updating as Edge-Linux Stable releases become available every few weeks.
I think those are the only alternatives at this time. For what it is worth, I intend to continue to use Edge-Linux Beta via the Flathub beta channel on Solus until the Stable version is released to the Flathub stable channel.
7fc3f7cf58