Have you checked in the root user account ?
I downloaded the standalone installer for DW CS6, and used my Master Collection serial number to authorize it. Dreamweaver is now installed but it fails to run if it is not run from an account with Admin privileges.
When first launched after rebooting my MacBook, it bounces in the dock for a few minutes, and then vanishes with no warning. Attempting to launch it a second time leads to the icon zooming out, as if it were about to launch, followed by nothing. No bouncing in the dock, no alerts, nothing.
You can find here a screenshot showing the System Requirements for Dreamweaver, plus evidence that my MacBook conforms to these requirements.
It runs from an account with Admin rights, but not from a standard account. Always running from an account with admin privileges is not an option.
Option 1 use the cs cleaner tool:
Then try to re-install.
Create a new admin user and try installing from that
Try installing as the root user.
The final issue I mentioned is not with the installation but with the first launch.
My solution was to:
- Open System Preferences at the Accounts pane
- Click on the Lock icon in order to make changes, and enter an admin user name and password.
- Select the standard user account that is to use Dreamweaver
- Check the Allow User To Administer This Computer checkbox
- Reboot the computer
- Launch Dreamweaver from the user's account (now with admin privileges)
- Dreamweaver does whatever it is that it needs admin privileges for
- Repeat steps 1 to 3
- Uncheck the Allow User To Administer This Computer checkbox, so that the user goes back to a standard account
- Reboot the computer
- Dreamweaver will now launch happily from the chosen user's standard account.
I imagine that it would not take a whole morning to fix Dreamweaver CS6 so that it throws up a "Please give me temporary Admin privileges" dialog on first launch. It might also not take that much longer to do whatever it is that it has to do on first launch in a folder where admin privileges are not required.
This would save hours of frustration on the part each of the thousands of end users who are likely to encounter these symptoms.