HI all,
I myself found the fix
we have to enable TLS 1.0 from registry
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\
TLS 1.0 ->Client --> Enabled Dword value 1
issue got resolved
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
we have an outage for 3 users in a project where they are not able to login to visual studios upgrade 5 2013 it shows an error like
sorry we ran into a problem
online service not aviable
145999-screenshot-13.png
i am attaching the error screenshot here also issue has been reported in Microsoft website and we have followed all the FLS mentioned by other user in the forum which still remains un answered
Not able to sign in to Visual Studio 2013 with update 5. - Microsoft Q&A
requesting inputs for resolving this
HI all,
I myself found the fix
we have to enable TLS 1.0 from registry
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\
TLS 1.0 ->Client --> Enabled Dword value 1
issue got resolved
I ran into this problem as well, but the solution was not enabling TLS 1.0 in the registry. I think it is due to Microsoft discontinuing support for TLS 1.0. Visual Studio 2013 natively calls that protocol to sign-in. You have to force the .Net Framework VS 2013 was built upon to use a more modern protocol, i.e. TLS 1.2
For me, VS 2013 Update 5 appears to be built against v4.0.30319. I forced the 32 bit framework to use strong crypto.
PowerShell script that will add the key:
New-ItemProperty -path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null
You can find more information here: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client
Thanks
New-ItemProperty -path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null
That solved my Problem. Run PowerShell with admin rights and run the above given script.
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.