I'm having the same issue with VS Express 2013, but running the script below using Powershell as Admin the issue went away, even after restarting the machine. The issue not re-occur
Run Powershell as Admin:
New-ItemProperty -path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft.NetFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null
Thanks @Andrew Doering for your resolution.