I'm experiencing issues deploying the Adobe Flash Player 32-bit/64-bit ActiveX 15.0.0.223 update via WSUS PP which I have imported from the Adobe catalog (AdobeFlashPlayerCatalog_SCUP.cab). The update is presented to me via Windows Update console so detection logic is fine but it just fails to install with the generic Microsoft 8024200D Error code. Funnily enough the Adobe Flash Player 32-bit/64-bit Plugin 15.0.0.223 is presented and installs fine on my client machines and earlier versions of the ActiveX component have installed without issue in the past.
Has something changed with Flash Player ActiveX 15.0.0.223 component that I am struggling to understand which is preventing it's installation ?
I'd appreciate any feedback or things to attempt to try and resolve.
I can supply logs if necessary but to be honest they are not really telling me anything.
Thanks in advance.
Dave........
Comments: I've deployed the update from the SCUP catalog here and I haven't seen this error (or any errors from this update, though my sample size is admittedly small, as many users' computers are turned off for vacation right now). I'm curious about whether this is a client issue or a one-off WPP issue. So, before you delete the update, can you verify that the update can be installed from the package you have in WSUS? In WPP, you can right click on the update, export it, and then extract the files on a test system and run the extracted file from an elevated SYSTEM context command line (since Windows Update runs in this context; you can use "PSExec -i -s -d cmd.exe" from SysInternals Suite to get a command line running as SYSTEM). I don't see any special flags in the metadata, so just running an msiexec.exe /qn /i [path-to-flash-msi] should be sufficient for testing here, though you can enable verbose logging for more info with a /L*v [path-to-log-file] For taking a hammer to the windows update client components (if the install from the exported update works fine): You can reset all of the Windows Updates components by following instructions in this article: http://support.microsoft.com/kb/971058 I'd also check out whether BITS is properly patched on the systems with errors. See http://support.microsoft.com/kb/331716 for a list of BITS updates.
Has something changed with Flash Player ActiveX 15.0.0.223 component that I am struggling to understand which is preventing it's installation ?
I'd appreciate any feedback or things to attempt to try and resolve.
I can supply logs if necessary but to be honest they are not really telling me anything.
Thanks in advance.
Dave........
Comments: I've deployed the update from the SCUP catalog here and I haven't seen this error (or any errors from this update, though my sample size is admittedly small, as many users' computers are turned off for vacation right now). I'm curious about whether this is a client issue or a one-off WPP issue. So, before you delete the update, can you verify that the update can be installed from the package you have in WSUS? In WPP, you can right click on the update, export it, and then extract the files on a test system and run the extracted file from an elevated SYSTEM context command line (since Windows Update runs in this context; you can use "PSExec -i -s -d cmd.exe" from SysInternals Suite to get a command line running as SYSTEM). I don't see any special flags in the metadata, so just running an msiexec.exe /qn /i [path-to-flash-msi] should be sufficient for testing here, though you can enable verbose logging for more info with a /L*v [path-to-log-file] For taking a hammer to the windows update client components (if the install from the exported update works fine): You can reset all of the Windows Updates components by following instructions in this article: http://support.microsoft.com/kb/971058 I'd also check out whether BITS is properly patched on the systems with errors. See http://support.microsoft.com/kb/331716 for a list of BITS updates.