Hi Yeahsurelalala, it's a real shame that this was not a direct fix for you. The only other solution I could possibly suggested is first going to your 'Disk Utility' in Applications/Utilities (or use your search bar/spotlight to find it) and use the fix permissions option. Once completed, return back to the duplications process in the Applications Support folder. Hopefully this works… but that's as far as I got, as I resolved the/my issue.

I too, have tried all of the solutions and NOTHING works!!  sigh.  so frustrating.  Called tech support....was on hold for 35 min before anyone picked up.  Of course this was at 6:15 pm.....waited til 6:50...(mind you they close the north american support at 7 pm)  Tech said he would call back within an hour.  NADA!  great customer service huh?!  I don't get how come some of the fixes work for some people and others don't.

I'm running a Macbook pro 10.6.3 snow leopard.

The permissions solution also did NOT work for me.  I suspect it's a FileVault incompatibility, as I have FileVault turned on, and have experienced this before with other Adobe products.

It is company policy that we keep FileVault enabled, so I am locked out of CS5.  = (

Don't have FileVault, none of these solutions worked for me.

I finally fixed this today by installing the HTML5 extension pack (http://labs.adobe.com/downloads/html5pack.html)

Had the same problem. Never used File Vault. Did the manual permission set and on third try, it worked. Echoes the pain I had when installing CS3.

As many have noted, bad QA.

I tried every solution on here (including the permissions, repairing permissions on the entire drive, and copying the saved preferences from the dreamweaver cs4 folder to the dw cs5 folder) a few days before installing the html5 extension.

Right, just spent ANOTHER few hours trying to sort it and still DOESN'T launch!!! My wife is nearly as angry at Adobe as I am!!

I'm going to start charging Adobe my time at this rate!!!!! Why is nobody from Adobe replying on this thread? When can we expect a patch / update!? This problem is not solved, so someone better be looking into it as there are a number of VERY unhappy clients here!!!

Yeah this is a real bummer, I was looking forward to trying out the new html5 extension pack.

I have done the same thing.  I deleted the new install, first just dreamweaver, then the whole suite!  then I created a new account, re-downloaded just dreamweaver, installed and still didn't work. 

Adobe told me to go into safe mode and try to open the program.  LOL  like that's gonna work! 

Do you guys also have CS4 installed?

I also have CS4 installed at the moment, but have tried with it installed, without it installed, everything

....

The CPs & Adobe's response reminds me of  BP's response to the Deepwater Horizon disaster. Blame everyone else and don't take resposibilty for their own failings.

And why isn't someone from Adobe monitoring these forums These forums and others are where the problems are discussed and where praise would be issued by their users  to Adobe if they knew someone was listening. After sale service or lack thereof is what can bring down a company or make the company a hero with it's customers.

This morning I posted a link to this discussion in the forum you mentioned, so now we wait (and in the meantime use Coda instead (and maybe stick with it)).

The above helpful to anyone? Dreamweaver is still running smoothly on my Mac after a full day of coding. Have reinstated all my settings, so it better not crash again... *skull & crossbones*

nope, didn't help here (10.6.3 with FileVault activated) - I even installed the HTML5 Pack (AdobeDreamweaver-11.0-All-Update.dmg)

I have been testing Dreamweaver CS5 with network accounts.  We have nfs shared accounts.  Instead of trying to find the initial files required, I symlinked the entire users Library to a local location as a test.  The application still doesn't open.  So symlinking clearly isn't going to work this time.

Each time I talk to anyone at Adobe about their performance of software and network home accounts, disappointingly they never appear to be interested.  Unfortunately, they appear to still be living in 1980-90 where everyone logs in locally.   Adobe software is the only industry standard software that we use that has shown to suffer this badly on networks.  Not only should an account be a local account, but Adobe still insist that all files must be local (including not using Firewire drives).  With the size of files now, this is becoming very unrealistic, not to mention that local files aren't backed up or protected by being stored on raids; another reason why we run network home accounts.

We can only hope that they will provide an update that will get Dreamweaver working, both on network accounts and with Filevault.

I have had some success and failures with this.

I am using Snow Leopard 10.6.3

FileVault is not being used.

Non admin users with network home directories

Dreamweaver fails to launch as others described here. Changing file permissions on the network home directory did not work. But, forcing local home directory and modifying the locally created folders permissions did work. Creating a local non admin account worked as well. These are not acceptable solutions in our environment. We are a community college with teaching labs and require network based home directories.

We also had this problem with Acrobat 9 pro last year and had to revert to version 8. Hopefully Adobe resolves this problem soon.

yeah, you'll have to keep doing this...

5 times for me up to now.