[German]A brief message for Windows 10 users and administrators. Although Microsoft has declared Windows 10 V1803 as 'business-ready' (in the SAC), the rollout on certain machines has been stopped. Addendum: Issue fixed for several scenarios.
Issues with TLS 1.2
In Windows 10 there are serious issues, when using TLS 1.2 transport encryption in applications. User @Abbodi86, who is very active at askwoody.com, has come across this information. Microsoft has published an KB article Applications that rely on TLS 1.2 strong encryption experience connectivity failures after a Windows upgrade after a Windows upgrade dated August 15, 2018, which states:
Customers who run .NET Framework applications that rely on Transport Layer Security (TLS) 1.2, such as Intuit QuickBooks Desktop, may experience connectivity failures after they upgrade their system to a newer version of Windows.
So there are problems with systems that depend on TLS 1.2 transport encryption in applications. According to KB articles, these are mainly applications based on Microsoft.NET Framework 3.5. Within the kb article Microsoft gives some hints for workarounds to be able to establish the TLS 1.2 connection after all. As problems arise, Microsoft stopped the rollout of Windows 10 version 1803 on some machines, Microsoft writes:
Microsoft is working on a resolution, and will provide an update in an upcoming release. We have temporarily suspended offering the Windows 10, version 1803 update to customer systems that run applications for which this is known to be an active problem. (via)
Update KB4458166 fixes the TLS 1.2 issue
Addendum: According to askwoody.com, Microsoft has released on August 17, 2018 out-of-band update KB4458166, which should fix the TLS 1.2 bug (for Intuit QuickBooks) described above. For the update KB4458166 there is currently no description (only this KB article with the description of the error, and in the meantime the reference to the fix). The update is also available for download from the Microsoft Update Catalog (in addition to distribution via Windows Update).
Cookies helps to fund this blog: Cookie settings