Hi, The Microsoft patch for KB980436 addressed some SChannel security issues. In the KB description they provided a way to go back to "compatibility mode" and select to provide SCSV for the TLS protocol for Windows XP (sorry if I'm not describing it well, it's all in the KB article). The registry entries they provided for XP work perfectly, however there was nothing for Windows 7. I need to be able to revert to this "compatibility mode" for Windows 7 workstations. I am currently sending my http requests unencrypted and would like to get back to https. Any help would be greatly appreciated. (the server I am talking with is Solaris 10). -- Tim

Hi Tim, do you give me the correct KB number? KB980436 is a patch that repair a security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain control over it. You can check it on: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6fc86b71-2764-4baf-9f61-4ce158b00e50#QuickInfoContainer As you said you want to revert to compatibility mode for Windows 7 workstations, you can try to use Windows XP Mode for compatibility. Hope it helps.

Hi, Yes this is the correct KB number. The program in question is run from a network share. I didn't think you run compatibility mode from a netwrok drive. I will look into it though. Thanks for the ideas. -- Tim

Dear Support team, today we installed on our server the Patch kb980436. Now our Https-calls to our report-server do not work anymore. The Report Server got the patch some time ago, but since we updated our server where the client is running. We get this exception. I get the following exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) We do the the Https call from a .NET Application before this update everything worked fine. Does anyone have an idea what else migth have to be adjust too. Thanks a lot for any help, with kind regards Jens Francke

I set things up so I could run it locally using "XP Compatibility mode". No change. This is not an application compatibility issue, rather, as described in the KB article, an HTTPS, TLS compatible mode, vs strict mode issue. -- Tim