Installing MicrosoftEdgeBetaEnterpriseX64.msi - Error 1722 when EdgeUpdate Policy is configured

[Gunnar Haslinger]

When installing MicrosoftEdgeBetaEnterpriseX64.msi (current Version 77.0.235.20) I get following MSI Error 1722:

Product: Microsoft Edge Beta -- 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.

After some investigation I found out, that the configured EdgeUpdate Policy results in this Error.

Update-Policy as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate]
"UpdateDefault"=dword:00000000
"InstallDefault"=dword:00000000
"AutoUpdateCheckPeriodMinutes"=dword:00000000

To solve the MSI Installation Problem I had to delete the EdgeUpdate Policy prior to start the MSI-Installation:

reg DELETE HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate /f

This seems to be a bug which should be fixed. The UpdatePolicy configures the Automatic Online-Update behavior - but should not result in MSI-Errors when deploying the Package by on-premise software-distribution Solutions.

[#2]

@Gunnar Haslinger How do you plan to distribute updates/patches? Do you think every single update/fix well be available as MSI package? How do you organize test deployment rings for new releases?

[#3]

@Thilo Langbein Microsoft didn't publish information how the Lifecycle of the final product is planned. But as there are the EdgeUpdate Policies I guess this is part of the final product too (wouldn't make sense to create EdgeUpdate Policies only for beta-phase).

Sure, offline MSI-Package-Deployment is the preferred way. Planning to deploy Edge based on Chromium as every other software package by our internal fully-managed enterprise deployment. Seems there is no need for separate "Updates/Fixes" because the full MSI-Package of Edge itself is not very large and can be used to update to the most current version.

[#4]

@Gunnar Haslinger 

Based on the reg keys that were set it looks like "install default" is the culprit and this experience would be by design (though we should look into having a more descriptive error message in this scenario).

Essentially with InstallDefault set that way the machine is being told "don't allow the next version of Edge to be installed" so when you try to install the next version of Edge it recognizes that there is policy set saying "don't allow installation" and it is respecting that.

Presetting the Update policies (UpdateDefault) should work as you expect and not block installation. Doing this would be the intended way to prevent Auto-update from running after you install using the MSI.

Hope that helps!

-Steve

[#5]

@Gunnar Haslinger In my test Environment I was still affected by this bug with the stable version of Edge ( 79.0.309.71) 

The workaround fixed the issue.

Should this be fixed? 

[#6]

@Stefan Röll I'm still using my workaround (deleting the EdgeUpdate Policies before applying the MSI-Package). I haven't tested if newer MSI Packages behave different or at least give more intuitive Error-Messages. 

See the message @Steve Rugh posted which basically tells us to just set the UpdateDefault and not the InstallDefault Policy as an other solution.

My solution is still, to delete the EdgeUpdate Policies before Installation the MSI-Package and ReApply the Policy after Installation.

[#7]

Thank you so much for discovering this! We had implemented group policy to lock down the new Edge browser and it was applied to our test machines. I couldn't figure out why it wouldn't install on ANY of them and this was why. I simply put in a delete command before the installation and it works flawlessly now.