1 Reply Latest reply on Mar 14, 2012 3:34 PM by historicalshavlikemployee

    adobe flash for firefox 10 - APSB12-05

      This patch shows as missing on several W7 machines and does not seem to "take."  Running install_flash_player_10318316.exe manually from C:WindowsProPatchesPatches appears to work properly.  However, the test that causes the patch to be marked as missing still shows the patch as missing after running the install file manually: C:WindowsSystem32MacromedFlashNPSWF32.dll is still at version as opposed to as expected.

      The lines below are from FlashInstall.log.  Things appear to have run properly.
      Can you help?

      =O====== M/ 2012-03-13+15-07-14.371 ========
      0000 [I] 00000010 "C:WindowsProPatchesPatchesinstall_flash_player_10318316.exe"
      0001 [W] 00001036 SoftwareMozillaFirefoxextensions/Plugins 2
      0002 [W] 00001036 SoftwareMozillaMozilla Firefoxextensions/Plugins 2
      0003 [W] 00001036 SoftwareOpera Software/Last CommandLine 2
      0004 [W] 00001036 SoftwareOpera Software/Last CommandLine 2
      0005 [W] 00001036 SoftwareOpera Software/Plugin Path 2
      0006 [W] 00001036 SoftwareOpera Software/Plugin Path 2
      0007 [I] 00000014 C:Windowssystem32MacromedFlashNPSWF32.dll
      0008 [I] 00000015 C:Windowssystem32MacromedFlashFlashUtil10za_Plugin.exe
      0009 [I] 00000017 C:Windowssystem32MacromedFlash
      0010 [I] 00000019 C:Windowssystem32FlashPlayerCPLApp.cpl
      0011 [I] 00000020 C:Windowssystem32FlashPlayerCPLApp.cpl
      0012 [W] 00001024 C:Windowssystem32FlashPlayerCPLApp.cpl 183
      =X====== M/ 2012-03-13+15-07-23.321 ========
        • 1. Re: adobe flash for firefox 10 - APSB12-05
          If the file version is still at then Protects detection logic is operating correctly as the vendor patch appears not to have installed correctly.  Protect will essentially detect the patch as missing using the file verison within its detection.  After that is will push the patch out to the propatches folder and run the vendor patch with a quiet switch.  Adobe patches are notorious for not installing properly which is more a vendor specific issue. 
          I suggest uninstalling the patch, then installing it again using a pre and post deployment reboot to ensure that Adobe is not currenlty running in memory.