Ver. 27.0.0.170 MSI returns error 1722

Forum|Forum|8 years ago
October 20, 2017
3 replies
882 views

The MSI hosted on the developer page appears to be corrupt. Halfway through it give the Error 1722. There is a probelm with this Windows Installer package. Downloaded from multiple computers and tried to install on multiple more. Same problem. Adobe please fix asap.

I need to deploy to thousands of machines and need the msi fixed.

[moderator: edited to add error to title]

This topic has been closed for replies.

Correct answer jeromiec83223024

Thanks for the feedback. It's odd, in that these binaries have been published and deployed pretty widely over the past week. It's all hosted on a CDN, and we do a bunch of stuff to ensure that bits deployed to the CDN are valid, and they're monitored to ensure that they stay that way.

If it is indeed a problem on the distribution side, it's most likely a very localized issue affecting the specific node that you're getting routed to. Any chance you have the ability to VPN to another geographic endpoint in your organization? It might get you around the problem. Also, where are you located?

divya010193

Adobe Employee

Hi,

27.0.0.183 fixes the crash and is now available.

Please go to get.adobe.com/flashplayer to download the latest version.

We can't speak as to when Google (Chrome) or Microsoft (Win 8.x/10 for Edge/IE) would release the update.

Thanks!

_maria_

Legend

Which MSI installer (ActiveX for IE, NPAPI for Firefox, PPAPI for Chromium-based browsers)?

Which OS are you attempting to install on?

Error 1722 is a generic error. To view the exact error, please provide the verbose (run with options v+x) MSI installer log file and the corresponding FlashInstall log file(s). The FlashInstall log file is located at the following location:

32-bit OS: C:\Windows\System32\Macromed\Flash\FlashInstall32.log
64-bit OS: C:\Windows\System32\Macromed\Flash\FlashInstall64.log AND C:\Windows\SysWOW64\Macromed\Flash\FlashInstall32.log
1. both files are required from a 64-bit OS

Upload the verbose MSI log and the FlashInstall log file(s) for the SAME installation attempt to cloud.acrobat.com using the instructions at How to share a document and post the link to the uploaded files in your reply.

Thank you.

--

Maria

jeromiec83223024Correct answer

Inspiring

Thanks for the feedback. It's odd, in that these binaries have been published and deployed pretty widely over the past week. It's all hosted on a CDN, and we do a bunch of stuff to ensure that bits deployed to the CDN are valid, and they're monitored to ensure that they stay that way.

If it is indeed a problem on the distribution side, it's most likely a very localized issue affecting the specific node that you're getting routed to. Any chance you have the ability to VPN to another geographic endpoint in your organization? It might get you around the problem. Also, where are you located?

J

jc73286168Author

Participant

I am thinking it may have been a localized issue. I did as you suggested re: different geographic location and the latest msi worked great. Thanks.

jeromiec83223024

Inspiring

Can you give me the IP address of the host that's serving the corrupted bits? I'd like to follow up with our CDN provider.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.