![]() ![]() Use the workaround described in the registry section workaround in to go back to the 512-bits settings. Nothing related to these changes points to Windows 10, but as we can conclude, these changes are introduced with June 2016 CU for Windows 10 (and thereby carried forward to July CU and any other CU to come). Note that this KB was released in May 2016 but not anywhere stated to affect Windows 10. Windows as of update no longer support ciphers with 512-bits. The Windows SChannel error state is 808.ĭoing a network trace showed that the web app server negotiated the TLSCipherSuite TLS_DHE_RSA_WITH_AES_128_CBC_SHA. The TLS protocol defined fatal error code 40. This may result in the termination of the connection. Looking at the System log in Event Log showed Schannel errors:Ī fatal alert was generated and sent to the remote endpoint. ProblemĪfter installing June (KB3163018) or July (KB3172985) cumulative updates for Windows 10 a specific web app was broken, when browsing to it in Internet Explorer 11 or Edge lead to ”The page can’t be displayed”. ![]() Some web apps might not work after installing the June (or July) 2016 Cumulative Update for Windows 10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |