Forum Discussion
Installing MicrosoftEdgeBetaEnterpriseX64.msi - Error 1722 when EdgeUpdate Policy is configured
Hello all,
When i see the answers here i am unsure if this "Bug" is related to EMEA (German, Switzerland and Austria) maybe?
We have lost a lot of time at an IT service company because there was a BUG in Microsoft Edge/Chrome, from version 126 to 127, which caused an update loop. To solve this many IT technicians who forced users to use Firefox or other browsers then disabled updates locally (as shown with the REG key you delete in your post) or directly with a GPO. (Like the Post JasonGallas​ from below)
After some months they still need MS EDGE Chromium but get stuck in an update failure.
No matter how you tried to update Edge to get it running again, it failed. (MSI, WSUS, Download from Windows Update Catalog, Deployment, Intunes, Ninjaone etc.)
I have seen this so many times in the past with different customers and people that we collected everything in a post on our blog.
For me, it once again shows how dangerous such quick workarounds can be. They may solve a problem immediately but can result in hundreds of hours of lost work for the same customers over the following months.
Greetings from Switzerland
https://www.butsch.ch/post/microsoft-edge-fails-to-update-from-wsus-from-msi-file-or-repair-apps-because-of-gpo-0x80070643-1722/
Error: Product: Microsoft Edge — Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action DoInstall, location: