Skip to main content
Participating Frequently
May 5, 2017
Answered

Dreamweaver 2017 crashes at startup with Mac 10.11

  • May 5, 2017
  • 1 reply
  • 2678 views

Have not used DW since upgrading to 2017 a few months ago. It won't run at all and crashes on startup. Shows a crash report. Tried installing Java but that did not work. Found a tutorial on removing preferences but you have to be able to open DW to do that. Running Mac OS 10.11.6 on Macbook Pro early 2011.

This topic has been closed for replies.
Correct answer Nancy OShea

I did that and Dreamweaver worked just fine. The problem is that all my files that I need are on my current log in.


All I can say is your user account is corrupted.  That means you must contact Apple and see if it can be repaired or just bite the bullet and move everything to the new user account.  

1 reply

Jon Fritz
Community Expert
Community Expert
May 5, 2017

You can manually remove the prefs folder by turning on your OS's hidden files and following the instructions here...

Restore preferences in Dreamweaver CS4, CS5, and CS5.5

Substitute CC2017 for any CS version reference and you should be fine.

Another item to check is whether you have Lavasoft's Web Companion installed. Uninstalling Web Companion will allow DW to start correctly (if it was there).

Participating Frequently
May 5, 2017

Thanks for the help. I renamed the Prefs file to "Old" yada but that did not work. Apparently do not have Lavasoft on this machine.

Community Expert
May 30, 2017

Yes I did.

We even installed the CC 2015 version of Dreamweaver, and had the same issue. To change our user profile here, because of security issues, we will have to reformat.

This is not good. I have already lost a day of work and will lose another day next week trying to resolve this.

There has to be a way to fix the user profile. Is it linked to Java version? Network preferences?


Garrett, I hear your pain as I've worked in similar circumstances.  Unfortunately, the issue that is happening is OS related and not DW related.  Unfortunately, most of us here who have been through the pain have found that a new profile is the easiest way because  digging into the OS to try and fix an OS issue is often difficult because there are many points at which the user profile could have been corrupted (system updates, application installs, etc.).  If you can find someone who is very familiar with your OS, you may be able to find ways to troubleshoot the OS more.  However, I fear that if you are in a restricted environment, that system level files related to the user account may not be accessible to you.