Another mystery solved since upgrading to Windows 10, and needing to add in a new VPN connection. Normally when you add in a VPN connection and connect to it, your system wants to use the default gateway of the VPN connection for IPv4 connections (eg. browsing the web).
Because I tend to have a number of VPN connections, and I’d rather be using my own bandwidth than whatever the VPN is providing, I turn the “Use default gateway on remote network” off. But for some reason under Windows 10, I’m unable to get to the properties of the IPv4 connection under the Networking tab. But now I have a work around!
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.
Solution found
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: sfc /scannow
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.
Across 3 different PCs I upgraded to Windows 10 recently I had 3 different issues. The biggest issue on the laptop that was upgraded was having the new Settings screen close immediately after opening. It would flash up for a moment, then close.
It would affect other similar screens (that kind of look the same, with that new UI) and was particularly annoying me as I wanted to set up Default Apps, connect to VPN, and do some other things that I could only access via the Settings page. Rebooting made no difference. But finally I found a fix!
I took the somewhat gentle leap from Windows 8.1 to Windows 10 across two PCs and a laptop, and the one major issue I faced with one PC only was that I could no longer send any emails that had Outlook 2010 installed. It would give me an error code 0x800CCC13, followed by ‘Task ’email address alias@domain.com- Sending’ Cannot connect to the network. Verify your network connection or modem.’
Replying to an email was fine. Any new email however would just get stuck in the Outgoing folder. The laptop, also with Outlook 2010, was fine.
