Several of my machines have now been upgraded to Windows 10 and I think on each one of them I have had some sort of issue to resolve.
My “main” PC ended up having more serious hardware issues, in that my primary hard drive died and was replaced with a fresh install of Windows 8.1. As soon as I got the machine back home I immediately upgraded it to Windows 10.
After that, one of the first things I did was install the Adobe Master Suite CS6 that I had running previously on Windows 8.1. At first glance everything seemed to be running fine, until I tried to start Dreamweaver.
It would show the splash screen for a second or two, get to the point of loading Business Catalyst extension (which I don’t even have), and then disappear.
Grrr, my Dreamweaver CS6 not working in Windows 10
Reading through several forum sites I did try a few things. Several sites mentioned deleting the WinFileCache<>.dat file from the C:\Users\’current user’\AppData\Roaming\Adobe\Dreamweaver CS6\en_US\Configuration folder. Sounded like reasonable advice, except that file didn’t exist.
This location also showed a CrashLogs folder, and indeed crash files were being created … but were completely empty. No help there.
I tried renaming the Configuration folder and letting Dreamweaver recreate it. No dice.
I tried logging in to Windows under a different account, still no go.
I tried changing things around in Compatibility Mode, nup.
I checked in Extensions Manager and confirmed I had no DW extensions running or installed.
I tried removing everything I could using the Adobe Creative Cloud Cleaner Tool, and reinstalling while running the setup.exe as Administrator. No joy.
I was seriously considering rolling back to Windows 8 or even Windows 7, as I knew the suite was working fine under both of those environments.
Eventually I found the answer, on this Adobe forum and it was basically the same solution as to when I was having trouble sending emails from Outlook, and that is to open up command prompt in Administrator mode (Windows Key + X, Command Prompt (Admin)) and run the following:
After running this, I rebooted, tried Dreamweaver, joy!
Note (3rd Feb 2016): As one commenter pointed out, similar symptoms could be seen but with a considerable different resolution, and was basically to do with the Dreamweaver Workspace in use, and further information on it can be found here.
I hope this helps someone who is finding themselves in a similar situation.
Adrian, ¡Eres una pinche reata!
Translate: Adrian, you are a genius!
Worked perfectly for me, kudos.
Thanks it really worked.
Glad to hear it!
worked!!! thank you so much
Good to hear Justin, glad it worked for you
Thanks for pointing me in the right direction Adrian, i linked to your post here on my blog http://www.digital-zest.com/ramblings/dreamweaver-cs6-win10-crashes-edit-file/
Thanks Piers! Had a look at your solution and looks like yet another way of resolving the issue, I’ll update my blog in kind and link back if you’re good with that.
Looking at the layout of your blog reminds me of how badly I need to redo mine! 🙂
That’s what I have in store for Q1 2016 anyway …
alhamdulillah , thanks man, i try many ways to solve my dreamweaver and this ways are very useful
thanks very much
You’re welcome! I’m glad it helped.
sfc /scannow not working
pls another trick
Hi Adnan, have you explored any of the other options in the post such as reviewing any crash logs, renaming the Configuration folder, changing things in Compatibility Mode, or completely removing and reinstalling Dreamweaver?
If none of those things worked, best bet is to explain clearly what symptoms you are seeing (ie. are you getting the same as I was? Or is it a different scenario?).
Otherwise your best course of action might be to contact Adobe direct.
Hope that helps!
Yes, it works!
Thanks very much for posting this.
Awesome! Glad it worked for you Millie
You’ve saved me so much pain. Dreamweaver was the only thing I really needed and the only one that didn’t work. You’re a champion!
Glad it worked out for you Steve!
Thanks so much for posting this fix did the job for me
Glad it worked out for you Peter!
Thank you very much !!
did not work for me
Sorry to hear that, are you saying you are getting the same behaviour as before? DW is simply closing (almost) as soon as you open it?
Thanks for posting Adrian, an easy fix 🙂
Yep, easy once you know how! Glad it helped 🙂
did not work for me.
Worked perfectly thanks so much
No problemo Dave, I’m glad it worked for you!