RECOMMENDED: Click here to fix Windows errors and optimize system performance
These errors are exactly correlated with the reset of TCP connections when someone tries to connect via port 3389 ms-wbt-server. If the person fails due to the security of the “Black Box” system, the incoming connection is interrupted by a reset packet. The error message you see is then downloaded to the Windows system log. If you encounter many more, you should change the listening port from 3389 to something else and see if the errors decrease.
Schannel supports encryption suites. The suites are listed in the default order in which they are selected by the Microsoft channel provider. Different versions of Windows support different SSL and TLS versions. Developers specify these elements using data types ALG_ID. For more information, see Specifying Encryption Channels and Encryption Values. Application compatibility and local activation security reinforce the strategy.
This error is (as far as I know) caused by an error in the certificate negotiation, your machine tries to initiate communication with another machine / server via a certificate and TLS, and the process generates this error TLS1_ALERT_UNEXPECTED_MESSAGE (10). HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\EventLogging Value is set to “1” or 0x0001, which is “Log Error Messages”. The problem with this is that any non-SSL request that arrives on the IIS HTTPS site causes SCHANNEL to log an error. You can replicate this by trying telnet port 443 on the central server and then entering a few characters.
“The next fatal alarm has been triggered. The internal fault condition is 1203.”
Modify group policies
In the Group Policy Editor (under gpedit.msc), select Computer Configuration > Administration Templates > System > Distributed COM > Application Compatibility and “Allow security check exemptions for local activations”.
Optimize Internet properties
1. If your browser is the cause of the problem, simply open Internet Options > Advanced > Disable all TLS options > Apply.
2. But it didn’t work for me, so talk a little bit by programming from my laptop with TLS. The end result is that this problem probably doesn’t even occur on your machine, so I will disable the SCHANNEL registration.
Note: If your error is NOT: “The following fatal alarm has been triggered: 10. The internal error condition is 10″. In that case, I suggest you NOT do it.
Enter regedit in the search field and navigate to the next key;
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > SecurityProvider > SCHANNEL
Uninstalling programs that could cause the error.
Several users who discovered this problem when configuring Outlook with Outlook Anywhere reported that the problem was caused for them by a “security toolbar”. It turns out that these things could investigate Schannel’s TLS traffic, which ultimately led to the following fatal alarm: 10: The internal error state is 10′.
If you think this scenario applies to your current situation, you can solve the problem by uninstalling the third-party security software / AV toolbar via Software. Here is a quick tutorial on how to do it:
- Press Windows + R to open a Run dialog box. Then type “appwiz.cpl” and press Enter to open the Programs and Features window.
- In Programs and Features, find the security toolbar you suspect of checking and uninstalling the TLS traffic channel by right-clicking and choosing Uninstall.
RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance
CCNA, Web Developer, PC Troubleshooter
I am a computer enthusiast and a practicing IT Professional. I have years of experience behind me in computer programming, hardware troubleshooting and repair. I specialise in Web Development and Database Design. I also have a CCNA certification for Network Design and Troubleshooting.