Finally, if these problems are blocking you from using Flash Player we recommend, as a last resort, you either revert back to Flash Player 11.2 or temporarily disable Protected Mode. We strongly recommend that Protected Mode is manually enabled once this issue is resolved.
To revert to a previous version of Flash Player, please see this FAQ: How do I revert to a previous version of Flash Player?
To disable Protected Mode, add the following line to your mms.cfg file located in:
Windows 32bit: C:\windows\system32\macromed\flash
Windows 64bit: C:\windows\syswow64\macromed\flash
If the mms.cfg file does not exist, create one using any standard text editor (e.g.. notepad)
Depending on your operating system, you might need to first save the mms.cfg file to a writable location (such as your documents or desktop folder) and then copy the file into the destination folder using Windows Explorer.
To re-enable Protected Mode, simply remove the line from the mms.cfg file.
Unfortunately, it looks like this was issued without enough testing and caused some of the problems that you, I and others have suffered over the last 10 days or so. Most Firefox users aren't affected - only the Chosen Ones :grin:Our Protected Mode implementation allows Flash Player to run as a low integrity process with several additional restrictions that prohibit the runtime from accessing sensitive resources.
By running the Flash Player as a restricted process, Adobe is making it more difficult for an attacker to turn a simple bug into a working exploit.