If you hover the mouse over the error message a tool tip window will display the entire message. What version of Flash Player are you trying to install? If it's the message I'm thinking of the message normally displays when trying to install a beta version on a system that has a stable version installed, or vice versa.
Please post a screenshot of the tool tip error message and the installer dialog window.
The FlashPlayerInstallManager.log file should provide more information. The file is saved at /Users/YourUserID/Library/Logs. Please upload the file to cloud.acrobat.com/send using the instructions at How to share a document and post the link to the uploaded file in your reply.
And trying to find the folder, it gives me, "Folder not found".
1 person found this helpful
Thanks for the screenshot. I believe if you click on the 'i' in the message, the rest of the text will display.
Are you trying to install Flash Player for Safari?
The folder is there. It's a standard Apple OS folder. It's the user's Library folder, as opposed to the system Library folder. Please do the following:
1. Select the Go -> Go to Folder... menu item from the Finder menu
2. Copy and paste ~/Library/Logs into the Go to Folder dialog
3. Locate the "FlashPlayerInstallManager.log" in the folder that appears.
Thank you. I uninstalled it and got the beta.
Thanks for confirming that the message. Essentially that message only displays when a stable version is installed a user is attempting to install a beta version, or vice versa. In these instances the installed version (beta or stable) needs to be uninstalled in order to install the other (beta or stable) version.
Well when I restored my pc, I put in my eBay bought Adobe Flash Professional CS3. I don't know if it has to do anything, but I have an application called, "Install Flash Player 9 UB". It could've been the cause of it. Well, thanks anyway Maria.
Yes, that could very well be the reason. Some version of Flash Professional included Flash Player (some had the stable version, some had the content debugger version, I don't recall the details). It's likely this is the reason for the behaviuor you were experiencing.
Thanks for your help.