In April 2014, I had IIS Express running SSL on several projects in Visual Studio. Then when I installed Update 4 to Visual Studio, this broke all SSL capabilities. (See Thread http://forums.iis.net/t/1210695.aspx?Visual+Studio+2012+Update+4+broke+IIS+Express+ability+to+require+client+certs+for+SSL )
This was fixed after a call to Microsoft Support which required me to make a registry key. After this was done everything worked correctly. Then I had to switch to a different machine (still Windows 7) with Visual Studio 2012 Ultimate rather than Professional. This was completed Sunday a week ago. All the projects and the applicationhost.cfg files were carried over. I went into the registry and made the required registry edit. When I opened Visual Studio 2012 and ran my project everything worked fine even though it was update 4.
Yesterday 12/14/2015 IE 11 was installed on my machine.
Today I tried to run one of my SSL projects and I got a 403.13 error. I checked both the registry and the applicationhost. no changes had been made. I then created a brand new SSL Web Forms project and ran that. Same error. I checked the list of certificates on the local machine. My certificate, the intermediate certificate and the root certificates were all listed. I checked the local machines certificate store. It listed the localhost IIS Express development certificate and my Root certificates and my intermediate certificates. I added the localhost certificate to the Trusted Root Certificates. Still same error.
I have seen virtually nothing on the web specifically addressing this error.
The only thing I've see talks about IE6 default settings. Our configuration for IE 11 required that the SSL 3.0 be disabled on only the Transport Layer Security cryptographic protocol is checked. However for fun and giggles I enabled SSL 3.0. Still no difference.
I am out of ideas. I am checking here first while I was still allowed to access this site before it gets blocked likewww.asp.net .
Can anyone suggest a course of action I haven't taken?