![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security12-100734741-large.3x2.jpg\"\/)
<\/p>\n<\/p>\n
Credit to Author: Woody Leonhard| Date: Fri, 17 Aug 2018 09:42:00 -0700<\/strong><\/p>\n Microsoft\u2019s <\/span>KB 4458166<\/span><\/a>, released on Tuesday, explains that the push to Win10 version 1803 has been halted for machines running .Net applications that use the TLS 1.2 security protocol. Presumably, effective Tuesday, if you have a Win10 1709 or 1703 machine that\u2019s running one of those programs (including, notably, QuickBooks Desktop), Microsoft won\u2019t try to push 1803 on it.<\/span><\/p>\n It isn\u2019t clear if the bug arose from the recent .Net updates to Win10 1803 or if it\u2019s been there all along and Microsoft\u2019s testers took four months to figure out that upgrading to 1803 hoses QuickBooks.<\/span><\/p>\n Late last night, without fanfare, Microsoft put two \u201cCritical Updates\u201d in the Windows Update Catalog that likely solve the problem. <\/span><\/p>\n I say \u201cappears\u201d because, other than the title of those (obscure!) Microsoft Catalog entries, I don\u2019t see any indication what they\u2019re supposed to do. The KB article, in particular, has not been modified to point to the new patches. It still says:<\/span><\/p>\n 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.<\/span><\/p>\n Do you still think Win10 1803 is ready for businesses?<\/span><\/p>\n Thx to an anonymous AskWoody poster.<\/span><\/em><\/p>\n Join us on the <\/span><\/i>AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Fri, 17 Aug 2018 09:42:00 -0700<\/strong><\/p>\n<\/p>\n