Copy link to clipboard
Copied
OS: Win 7, SP1, 32-bit
Browser: Firefox v 49
Flash player: v 23 plugin for Firefox
I am a licensed distributor through Adobe.
I deploy Adobe Flash via Microsoft group policy using an MSI downloaded from Adobe.
The flash player MSI will only install on 64-bit versions of windows but not 32-bit versions.
When I deploy via group policy to 32-bit workstations, the install hangs and never installs.
I am able to manually install a 32-bit version of Flash but I need to install this on dozens of workstations.
Please advise and/or direct me to a 32-bit only MSI for Adobe Flash player if one exists.
Thanks!
Copy link to clipboard
Copied
Hi,
We have a single Flash Player which supports both 32 bit and 64 bit system configurations. Could you share the FlashInstall.log file from the machine where you are seeing failure. Please go through Where do I find the Flash Player installation log on Windows? ​to get the location of the logs and upload the same How to share a document and share the path here.
Thanks!
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hi normancoordinate ,
I'm a little confused by the log files you provided. Your reported issue is that the MSI installer will not install on 32-bit operating system via Group Policy. However, you provided 3 identical copies of the FlashInstall.log file that are not for an MSI installation. Instead, the most recent installation (on 03-October) is for an installation using the online installer, that appears to be successful (no errors reported in any of the log files). The last recorded MSI installation was 22.0.0.192 on August 19th.
If you are having problems with the MSI installer, please provide the previously requested verbose (with additional debugging option) MSI log file and the FlashInstall.log file for the same machine and MSI installation attempt.
--
Maria
Copy link to clipboard
Copied
I enabled verbose logging, created the ADM.trace text file in the %temp% folder and ran the MSI installer over the network via group policy. When I restart the workstation tries to install the group policy for Adobe flash Player plugin 23 but hangs at 'please wait'. If I run the MSI installer directly on the workstation (not via group policy over the network), it is successful. Logs are at link below.
Copy link to clipboard
Copied
ADM.trace file is empty, but doesn't matter because this file is for the online installer (to enable additional debugging in the Adobe_ADM.log file). AdobeARM.log appears to be an Adobe Reader log file.
Adobe_ADM.log and Adobe_GDE.log files are generated by the online (shim) installer, downloaded from https://get.adobe.com/flashplayer. They are NOT generated by the MSI installer. Since you claim to be using the MSI installer these are not relevant to the installer you are using. To confirm, what is the name of the file you are using?
How do I create an installation log? provides a tutorial on obtaining MSI verbose log files, including how to enable the system to generate the log file when installing the MSI via Group Policy (this information is towards the bottom of the page). https://support.microsoft.com/en-us/kb/2545723 may also be of assistance. I found these performing an internet search for "msi installer logging", which returned many other sources in addition to these two.
Copy link to clipboard
Copied
The file I'm using is as follows:
install_flash_player_23_plugin
windows installer package (msi)
Copy link to clipboard
Copied
Thanks for confirming. As I mentioned perviously, Adobe_ADM.log and Adobe_GDE.log files are generated by the online installer (downloaded from get.adobe.com/flashplayer) they are not generated by the MSI installer. These are not relevant to you. Only FlashInstall.log file and the (verbose + additional debugging) MSI log files are relevant and necessary to troubleshoot the issue further.
Copy link to clipboard
Copied
I enabled verbose logging and tried the MSI install through group policy again. Here's the link for the log:
Copy link to clipboard
Copied
The file uploaded, AdobeARM(1).log is an Adobe Reader log file, not Flash Player (see the very last entry here https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/Updater-Win.html which shows AdobeARM.log is a Reader file).
Here is the contents of the uploaded file (product name in bold):
[2016-10-05 15:34:02] Adobe ARM 1.7.0.0 logging started.
[2016-10-05 15:34:02] Command Line:
[2016-10-05 15:34:02] ProductCode: {AC76BA86-7AD7-1033-7B44-AB0000000001}
[2016-10-05 15:34:02] ProductName: Adobe Reader XI
[2016-10-05 15:34:02] ProductVersion: 11.0.00
[2016-10-05 15:34:02] ProductUACPatching: disabled
[2016-10-05 15:34:02] Could not collect information for Product: {AC76BA86-7AD7-1033-7B44-AA1000000001}
[2016-10-05 15:34:02] EULA not yet accepted
[2016-10-05 15:34:02] ** Setting Error Condition:
[2016-10-05 15:34:02] Error Code: 100700
[2016-10-05 15:34:03] ARM returns ERROR_SUCCESS
[2016-10-05 15:34:03] Adobe ARM 1.7.0.0 logging finished.
[2016-10-05 15:54:54] Adobe ARM 1.7.0.0 logging started.
[2016-10-05 15:54:54] Command Line:
[2016-10-05 15:54:54] ProductCode: {AC76BA86-7AD7-1033-7B44-AB0000000001}
[2016-10-05 15:54:54] ProductName: Adobe Reader XI
[2016-10-05 15:54:54] ProductVersion: 11.0.00
[2016-10-05 15:54:54] ProductUACPatching: disabled
[2016-10-05 15:54:54] Could not collect information for Product: {AC76BA86-7AD7-1033-7B44-AA1000000001}
[2016-10-05 15:54:54] EULA not yet accepted
[2016-10-05 15:54:54] ** Setting Error Condition:
[2016-10-05 15:54:54] Error Code: 100700
[2016-10-05 15:54:55] ARM returns ERROR_SUCCESS
[2016-10-05 15:54:55] Adobe ARM 1.7.0.0 logging finished.
[2016-10-06 16:20:37] Adobe ARM 1.7.0.0 logging started.
[2016-10-06 16:20:37] Command Line:
[2016-10-06 16:20:37] ProductCode: {AC76BA86-7AD7-1033-7B44-AB0000000001}
[2016-10-06 16:20:37] ProductName: Adobe Reader XI
[2016-10-06 16:20:37] ProductVersion: 11.0.00
[2016-10-06 16:20:37] ProductUACPatching: disabled
[2016-10-06 16:20:37] Could not collect information for Product: {AC76BA86-7AD7-1033-7B44-AA1000000001}
[2016-10-06 16:20:37] EULA not yet accepted
[2016-10-06 16:20:37] ** Setting Error Condition:
[2016-10-06 16:20:37] Error Code: 100700
[2016-10-06 16:20:37] ARM returns ERROR_SUCCESS
[2016-10-06 16:20:37] Adobe ARM 1.7.0.0 logging finished.
[2016-10-06 17:23:15] Adobe ARM 1.7.0.0 logging started.
[2016-10-06 17:23:15] Command Line:
[2016-10-06 17:23:15] ProductCode: {AC76BA86-7AD7-1033-7B44-AB0000000001}
[2016-10-06 17:23:15] ProductName: Adobe Reader XI
[2016-10-06 17:23:15] ProductVersion: 11.0.00
[2016-10-06 17:23:15] ProductUACPatching: disabled
[2016-10-06 17:23:15] Could not collect information for Product: {AC76BA86-7AD7-1033-7B44-AA1000000001}
[2016-10-06 17:23:16] EULA not yet accepted
[2016-10-06 17:23:16] ** Setting Error Condition:
[2016-10-06 17:23:16] Error Code: 100700
[2016-10-06 17:23:16] ARM returns ERROR_SUCCESS
[2016-10-06 17:23:16] Adobe ARM 1.7.0.0 logging finished.
If you're having issues installing Reader, please post to the Acrobat Reader forum.
Copy link to clipboard
Copied
Sorry, I attached the wrong log. verbose log is attached. Thanks!
Copy link to clipboard
Copied
How exactly did you configure the system to obtain that log file and how did you run the MSI installer (did you include any msiexec commands)? Normally a MSI installer run with the /l*vx commands (verbose and additional debugging) generates a log file that is several hundred lines long. For I ran the NPAPI MSI from the command with the /*vx option (msiexec /i install_flash_player_23_plugin.msi /l*vx msi.log) and the file generated with over 160 lines long (uploaded at Shared Files - Acrobat.com). However, the file you provided is only 26 lines long. Much too short to include detailed verbose and debugging information.
In your first post, when you say "I am able to manually install a 32-bit version of Flash but I need to install this on dozens of workstations." what exactly do you mean? Did you run the MSI installer directly on the system and it installed fine?
Copy link to clipboard
Copied
To obtain the log file i created a registry key to enable verbose logging:
hkey_local_machine\software\policies\\microsoft\windows\installer\logging with a value of voicewarmupsx
The MSI is not run with any special commands that I know of. Perhaps I'm looking in the wrong place for the log file. The file I posted was found: c:\temp\windows\temp\MSIadd0
Copy link to clipboard
Copied
I mean manually running the MSI installer on the workstation. However, the online installer also works because it's downloading and install a 32-bit version of the flash plugin.
There is only one Flash Player installer that contains both the 32-bit and 64-bit versions of Flash Player. On a 32-bit OS only the 32-bit version is installed. On a 64-bit OS both the 32- and 64-it versions are installed to be used by either 32- or 64-bit browsers.
The FlashInstall.log file you previously provided didn't contain a recent NPAPI (plugin for Firefox) MSI installation attempt. According to the log file, the most recent MSI installation was on Aug 19th when version 22.0.0.192 ActiveX (for IE) was installed. The last time the NPAPI plugin was installed via MSI was in October of 2015. Since the log file doesn't show a recent NPAPI MSI installation, what happens when you run the MSI NPAPI installer manually on the workstation?
Is C:/temp/windows/temp a typo? Is there a MSI###.log file in C:/Windows/Temp with a date/time stamp close to when you ran the installer?
When you deploy via GPO, are users logged on or does the deployment occur when no user is logged on?
When the installation hangs, which process is hanging and who is the owner of that process?
Copy link to clipboard
Copied
sorry, I meant c:\windows\temp. Group policy updates occur during workstation restart so no one is logged in. the process is group policy is linked to the organizational unit (OU) on the server, the workstation in that OU is restarted and during restart the system hangs at the 'please wait' screen.
I think I found the log you're looking for and the link is below.
Copy link to clipboard
Copied
Thank you. That looks more like what we're requesting.
Can you also provide the FlashInstall.log file from the same machine this MSI log file was retrieved from?
Thank you.
Copy link to clipboard
Copied
Additional log file at the link below.
Copy link to clipboard
Copied
Based on the verbose MSI log file provided (on Oct 11) you may be encountering an issue we resolved a while back.
Please read through the tech note at https://helpx.adobe.com/flash-player/kb/msi-installation-problems.html for more information on the bug and the solution to clean the impacted system. The tech note mentions a number of MSI GUIDs, but you only need the one for the 16.0.0.235 NPAPI MSI, which is 61F2FFE4-56BA-4F5E-91FB-BD34F92E44CE. Run the MSIZap tool, as instructed in the tech note, on this GUID on the impacted system. If you have multiple systems impacted, hold-off on running this on those systems. We want to ensure this will fix the problem first before running it on multiple systems.
After running MSIZap on 61F2FFE4-56BA-4F5E-91FB-BD34F92E44CE attempt the NPAPI MSI installation following your normal deployment procedure. If the installation doesn't succeed, please provide the following:
Copy link to clipboard
Copied
On your first post, when you said "I am able to manually install a 32-bit version of Flash" Are you referring to manually running the MSI installer on the workstation or using the online installer (downloaded from get.adobe.com/flashplayer)?
Copy link to clipboard
Copied
I mean manually running the MSI installer on the workstation. However, the online installer also works because it's downloading and install a 32-bit version of the flash plugin.
Copy link to clipboard
Copied
Regarding the log files, the FAQ linked to requests Adobe_ADM.log and Adobe_GDE.log files. These are generated by the online installer, not the MSI installer, so these will not be necessary.
Instead, please provide a verbose MSI log file, with debugging enabled (option v for verbose logging and option x for extra debugging information), and the C:\Windows\system32\Macromed\Flash\FlashInstall.log file. Both files should be from the same machine for the same installation attempt.
Thank you.
Copy link to clipboard
Copied
This could be your issue with GPO install.
Install Adobe Flash Player 27 using Windows 7 Group Policy (100% Working Method)