Microsoft Adobe Flashplayer Security Update

Yes.  We release software in 4-week cycles (as does Microsoft).  Think of them like departing trains.  Feature-bearing releases come out quarterly, followed by two monthly patch releases.  In between those, we make pre-release (beta) builds available to an audience of several million users, to collect early feedback from a much larger and more diverse population of hardware than we could ever hope to test in a lab.

The issue you're experiencing didn't show up under lab conditions, and interestingly, didn't get pointed out in beta testing, either.  It's still not good, and we've made sure that the next shipping release had a remedy.

For the October release, the next train is basically locked and loaded, and the fix is already on-board.

More specifically, we're already done with the engineering on the next release, and it's currently undergoing testing from both our teams and test teams at distributing partners like Microsoft and Google, who bake Flash Player directly into their browsers.  Once testing is complete (which is basically now), then it moves from the various test teams to the publishing and distribution teams, who manage the pipeline responsible for delivering those patches to the ~2.5 billion machines that will pick it up.  None of those steps is trivial, and it's important that fixes to Flash Player land for all users simultaneously (or as close as humanly possible as we can get), so we do a tremendous amount of coordination between multiple companies, who also have their own complex needs and internal requirements.

Hope that makes sense.