Copy link to clipboard
Copied
Just installed Dreamweaver on my Windows 10 laptop. After installing, when I try to open it, nothing happens. It doesn't crash. I don't get an error message. Nothing happens. When I check task manager, it shows as running in the background, but I can't actually access the program.
I've tried running as admin. I've tried compatibility mode. I've tried uninstalling and reinstalling. I tried the "Windows 10 Fix" of doing the scan for errors via cmd prompt. I've tried deleting the library file. I've even tried deleting all my Adobe programs, deleting Cloud, then reinstalling Cloud and Dreamweaver again.
Still, no dice.
Help!
I don't have any problems loading CC 2017 on Win10 with the latest updates and security patches.
I think it's fair to say that something is unique about your particular set-up. It could be almost anything from graphics drivers or anti-virus & firewall settings or Windows C++ versions to port or DLL conflicts from other software. Locating the source of your problem could take a while.
Nancy
Copy link to clipboard
Copied
Have you tried below link
Installing or opening issues in Dreamweaver CS6
This might help.
Thanks,
Lalita
Copy link to clipboard
Copied
Did you try the solution in the above post? Did that help you?
I also suggest going through the troubleshooting steps in this article DIY troubleshooting kit for Dreamweaver if you need more assistance.
If none of these solutions help, and you have a licensed version of DW CC, send me your Adobe ID, location, and phone number over a private message. Click my picture and use the Message button. We will get in touch with you for investigation.
Thanks,
Preran
Copy link to clipboard
Copied
I spent a few hours on chat support with an Adobe specialist yesterday. After the few hours, he determined that Dreamweaver CC 2017 would not load on the machine. We removed it and installed the 2015 version, which works fine. I'm not terribly upset, as 2015 does what I need it to do, but if there's a compatibility issue with DW 2017 and Windows 10 machines, Adobe should be clear about that.
Copy link to clipboard
Copied
Hi Kevinh,
I am glad that you have a workaround solution that works for you, although it definitely isn't ideal. To be sure, we haven't seen many such issues, and it looks like this could be something very specific to your computer. If you can send me your case number over a private message, I can check with the team as to why you had to go back to a previous version.
Thanks,
Preran
Copy link to clipboard
Copied
I don't have any problems loading CC 2017 on Win10 with the latest updates and security patches.
I think it's fair to say that something is unique about your particular set-up. It could be almost anything from graphics drivers or anti-virus & firewall settings or Windows C++ versions to port or DLL conflicts from other software. Locating the source of your problem could take a while.
Nancy
Copy link to clipboard
Copied
I can't open dreamweaver either, the process just hangs at 7mb of RAM on my task manager and never opens
Copy link to clipboard
Copied
Restore Preferences.
Unusual behavior in Dreamweaver? Try restoring preferences.
Copy link to clipboard
Copied
I've tried that, it doesn't do anything but attempt to launch the program. I've run the adobe cleaner tool, I've uninstalled and reinstalled the program several times, with and without adobe creative cloud launcher, I"ve uninstalled, rebooted, ran the cleaner tool, restarted, reinstalled dreamweaver. Nothing will get the program to launch. It just gets stuck at 7mb of RAM in my processes tab.
Copy link to clipboard
Copied
Which operating system?
Which version of DW?
After a clean re-install, did you re-boot computer?
Copy link to clipboard
Copied
so as not to piggyback this thread, I've created a new post here: Cannot launch Dreamweaver
To answer your questions:
Windows 10 Home
I would assume the creative cloud launcher tries to install the latest version
Yes, uninstall, reboot, cleaner tool, reboot, reinstall.
Thank you!
Copy link to clipboard
Copied
OK. I'm locking this discussion to avoid any further confusion.