@gregneagle wrote:

With Flash Player 11.9.x, the package inside the application installs all needed components. It no longer leaves the autoupdate mechanism in a broken state.

Good to know they finally fixed that problem, goes to show how effective a collective boot up the back side to Adobe can be, thanks!

@rohrt85 wrote:

lol signing up to distribute Flash.......seriously......what's next Adobe to make my day just a little more peachy........?!

;)

http://www.adobe.com/products/air/runtime-agreement.html
http://www.adobe.com/products/reader/distribution.html?readstep

Duly noted about breaking the auto-updater; I actually prefer this (rather than trusting Adobe to push fully tested and verified updates that won't break anything for my customers). But, I understand the impulse to let it auto-updated... it just strikes me as dangerous.

You can still turn off auto updates.

Techniques referenced here still work: https://managingosx.wordpress.com/2011/05/13/disabling-auto-update-notifications-for-flash-player-10-3/

Latest info here: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flash_player_11_9_admin_guide.pdf

You can still turn off auto updates.

Techniques referenced here still work: https://managingosx.wordpress.com/2011/05/13/disabling-auto-update-notifications-for-flash-player-10-3/

Latest info here: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flash_player_11_9_admin_guide.pdf

@JPDyson, I hear you on the auto update stuff, and why you may not want that. We struggled for a long while internally here on whether to allow it to do that. Generally we don't want apps auto updating themselves since it doesn't give us a proper window to test changes and ensure it doesn't break critical functions.
But for FlashPlayer we finally settled on allowing it to auto update, because, well, less and less for us is relying on the FlashPlayer plug-in. We still need to have it there and keep it up to date due to constant security issues, but if we run across a situation where an update is reported to cause problems, we can always disable the current policy and roll back to a previous release. We keep all the previous installers going back a good ways, so they're ready to be pushed if we really need to.
In the end I guess the security implications of not auto updating Flash were greater than any potential for it to stop working with some sites, and so we chose the path of least resistance.

But, as @gregneagle mentions, you can still stop it from auto updating if you want. At least you don't need to rewrap FlashPlayer now or even bother to extract anything from the app installer, which I think is the overall win here for everyone.

@mm2270 Indeed; it's one of those cases where I have something that works, so while I appreciate the new approach (as you and @gregneagle mentioned), it amounts to a distinction without a difference. I'll probably adopt that model for the 11.9 push when I do it, anyway.

? New approach? What's new?