Forum Discussion
Installing MicrosoftEdgeEnterpriseX64.msi - Error 1722
When installing MicrosoftEdgeBetaEnterpriseX64.msi (current Version 80.0.361.48) I get following MSI Error 1722:
Product: Microsoft Edge for Business- 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.
At first, I thought it was being caused by the update-restriction being applied via GPO (ADMX), but even without this GPO settings applied or by reverting the corresponding setting in the registry, the installation fails as well.
The issue occurs on 57 from 240 workplaces (Windows 10 build 1709), but also on one Windows 10 build 1903. Remaining 1709 builds successfully installed the application.
Logfile: MSIc3130.LOG
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: C:\WINDOWS\Installer\MSI4045.tmp, command: /silent /install "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft Edge&needsAdmin=True&usagestats=0&ap=stable-arch_x64" /installsource enterprisemsi /appargs "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atrue%2C%22verbose_logging%22%3Atrue%2C%22msi_product_id%22%3A%22DCF62978-E764-38B6-8D70-FD4BFF0EDEE5%22%2C%22allow_downgrade%22%3Afalse%7D%7D"
Could someone help us out finding a solution to the install failure?
Today I retried the MSI install on a computer where it failed last week, and this time the installation went through without any hazzle. The only thing I *know* had changed was that the 2020-03 windows patches had been installed.
We have the same issue in our enterprise. Ever since version 80.0.361.109, clients that previously had the Edge Beta enterprise installed will fail to install the enterprise MSI anything from 80.0.361.109
Our last successful deployment that was largely successful to devices was 80.0.361.69. Ever since version .109, the MSI fails on the same step as yours. (See at the end of this post for the log).
My additional troubleshooting steps I took that didn't work:
- Manual uninstalling and gutting out Edge and EdgeUpdate files, registry entries, and services (sc delete servicename) didn't help.
- Installing the enterprise MSI of version 80.0.361.69 fails as well now, even after everything was manually removed
- Installing the newer MSIs also fail, same MSI errors as below.
- Disable group policy that blocks automatic updates from EdgeUpdate (and also deleted the registry items for the respective policies to EdgeUpdate)
This is the only thing that has worked for me so far:
- Install the latest Edge Beta Enterprise MSI
- Take the EdgeUpdate command that is from the MSI log that failed, and run the command manually to install Edge 81.0.416.53 (yes that entire block is one command... and running it manually works where the MSI fails to work).
C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe /silent /install "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft Edge&needsAdmin=True&usagestats=0&ap=stable-arch_x64" /installsource enterprisemsi /appargs "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atrue%2C%22verbose_logging%22%3Atrue%2C%22msi_product_id%22%3A%2249DCD999-3A4A-30D9-8B5B-F1312CEFAB12%22%2C%22allow_downgrade%22%3Afalse%2C%22do_not_create_desktop_shortcut%22%3Afalse%7D%7D"Here is the snippet from the MSI log that are failing.
CustomAction DoInstall returned actual error code -2147219674 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (A8:D8) [08:58:53:562]: Note: 1: 1722 2: DoInstall 3: C:\WINDOWS\Installer\MSI502B.tmp 4: /silent /install "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft Edge&needsAdmin=True&usagestats=0&ap=stable-arch_x64" /installsource enterprisemsi /appargs "appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atrue%2C%22verbose_logging%22%3Atrue%2C%22msi_product_id%22%3A%2249DCD999-3A4A-30D9-8B5B-F1312CEFAB12%22%2C%22allow_downgrade%22%3Afalse%2C%22do_not_create_desktop_shortcut%22%3Afalse%7D%7D"
MSI (s) (A8:D8) [08:58:53:562]: Note: 1: 2205 2: 3: Error
MSI (s) (A8:D8) [08:58:53:562]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722Hey,
had the same issue with the newest msi Version.
Just found out there is a new parameter added for the msi Installer:
Added the parameter "DONOTCREATEDESKTOPSHORTCUT=true" to my PSADT Script and it worked.
Works with "false" as well!
Maybe it will help you too 😉
- michli
Microsoft
Hi Senturion33, if you're still facing this issue, could you send MSI command you ran, and the following EdgeUpdate log from a machine where the Edge MSI failed? %ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log
For Edge Stable, the latest Windows updates listed in this link are required for it to install, so it's possible you were hitting that error; Edge Beta does not have this requirement.
Thanks! I will check for that log on Monday from a problem computer. As a workaround, I enabled automatic updates for Edge so that clients could at least get updated. I'll see how the deployment looks with the current release of Edge MSI.
The command I am using to install Edge:
msiexec /i MicrosoftEdgeEnterprise64.msi /qn /norestart /log %temp%\update.log
SanderVR Your solution in finding lies in finding the difference between the systems that have the deviation (57) and those that have not (240).
1722 usually means that a object or action in the msi could not be completed.
I suggest looking at software that is on the IS systems versus the IS NOT systems.
* Is there already a Edge Chromium present on those systems?
* Maybe Adobe Flash is installed on the 54? Which cannot be removed without manual intervention?
reg, Henno
Thanks for your reply. It is a good starting point, but we can already check these from the list:
- No Adobe Flash
- No previous Edge Chromium installations (as this is an initial deployment)
- No lack of available space on C:
Further more, there shouldn't be much difference between these systems.
Apparently I am not the only one facing this issue, according to the reaction of tjoanp
To be sure it is not caused by any system files being corrupt, I will run a DISM / SFC scan on one of the affected systems and try again. Will keep you guys posted...
- I ran "DISM /online /cleanup-image /restorehealth" with success and a "SFC /scannow" finished with a reboot. The SFC scan found errors and repaired them, but unfortunately this did not solve the install issue for me.
I have the exact same problem here, but using Edge 80.0.361.66.
No Adobe Flash, and no Edge Dev/Beta, just the default classic Edge distributed with Win10 1903.
I'm not sure what other installed software might block the Edge installer, any suggestions?
Best regards
- As this is still happening today: The most common reason for this is that Edge (standard/home) is already installed. This is not a side-by-side install, it's one or the other, sadly.
- If you have Edge installed, just open Edge, click on the ellipsis, the 3 dots on the top right of the window, go to "Help and feedback" at the bottom of the menu, and click "About Microsoft Edge". This will update Edge and you won't need the update.
This error haunted me for some time, but it was not the fact that I ran out of disk space, neither the Edge installer version itself, it had nothing to do with WebView2 component (as it was not installed on the system) and also the Installer service ran fine – everything else worked perfectly. Except installing Edge.
What did work for me though was to remove the machine in question from the domain. After that logging on locally and installing Edge 127.0.2651.105 did the trick. I re-joined the domain afterwards. Strange, I'll have to look into it but for the time being I'm happy it worked eventually.
