For those who would like to see the solution immediately without having to go through the details from above links, I shall brief the solution itself here.
There are basically two solutions:
Run “Windows Update” on the remote server (or the workstation) to which you are trying to connect. This will ensure that you have the latest patch on the remote box and you wouldn’t be facing this issue again. This would work provided your machine also has got the latest updates applied.
For those who cannot update the remote box for some reason(s), you would have to create a new registry entry as shown below:
Once above registry key is created, you must restart your workstation / client / computer without fail.
All good now to successfully connect to the remote box again.
This one’s another issue that was eating my brain for the past 2 days. Little bit if story first.
I have a Windows 10 Pro virtual machine on my MacBook Pro. Things went well until I tried installing SQL Server 2014 Express, which required .Net Framework 3.5. .Net 3.5 is built-in and we need to enable it from “Turn Windows Features On or Off”.
That’s where the bummer was. I could not turn .Net 3.5 on at all. Following was the error message that I was getting:
This is my first post from Perth, WA. It’s been an excellent journey and so far so good. More about my Perth life later.
This is something that I never experienced before. When you download any file from PartnerSource or CustomerSource, Microsoft would let you do that only through it’s File Transfer Manager program. If you have that installed already, any download initiation would first invoke this program and then let you set the path/folder to take in that download and etc.
However, when I tried to do that from my new Windows 10 machine, the FTM did not open. I tried to figure that out, but later remembered this same issue happening on my Windows 8.1 machine.