![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security14-100734743-large.3x2.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Tue, 29 Oct 2019 12:18:00 -0700<\/strong><\/p>\n October started out on an extraordinarily low note. On Oct. 3, Microsoft released an \u201cout of band\u201d security update to protect all Windows users from an Internet Explorer scripting engine bug, CVE-2019-1367<\/a>, once thought to be an imminent danger to all things (and all versions) Windows.<\/p>\n It was the third attempt to fix that security hole and each of the versions brought its own set of bugs<\/a>.<\/p>\n What? You haven\u2019t heard of any CVE-2019-1367 exploits in the wild? Me, neither. What was once the bogeyman du jour<\/em>, topic of many local TV station warnings and plenty of PC-busting online screams of terror, turned into another…meh.<\/p>\n Since then, we\u2019ve had the usual crop of two cumulative updates (security and \u201coptional\u201d) for each current version of Windows 10, as well as monthly rollups, security-only patches and monthly rollup previews for Win7 and 8.1. Pretty typical.<\/p>\n Here\u2019s the rest of the story.<\/p>\n G\u00fcnter Born opines<\/a> that this bug is a retrograde mistake from an earlier buggier patch, KB 4512941, the second (\u201coptional,\u201d non-security) August Win10 1903 patch released on August 30. Whatever its origin \u2013 and in spite of Microsoft\u2019s claim that it has fixed the bug \u2013 I\u2019m seeing lots of reports that it\u2019s still breaking systems.<\/p>\n Here\u2019s what Microsoft posted on Sept. 19<\/a>:<\/p>\n Some users report issues related to the Start menu and Windows Desktop Search<\/strong><\/p>\n “Microsoft has received reports that a small number of users are having issues related to the Start menu and Windows Desktop Search.<\/p>\n “Affected platforms: Client: Windows 10, version 1903<\/p>\n “Resolution: At this time, Microsoft has not found a Search or Start issue significantly impacting users originating from KB4515384 [the first cumulative update for September -WL]<\/em>. We will continue monitoring to ensure users have a high-quality experience when interacting with these areas.”<\/p>\n You don\u2019t need to look very far to see complaints that Start in particular \u2013 and for some, Search \u2013 don\u2019t work right after installing any of the most recent patches. On Oct. 11, MS engineer Paul Sey said on the Answers Forum<\/a>, \u201cWe are aware of this issue and estimate a resolution to be released in late October.\u201d<\/p>\n At this point, KB 4522355, the only Win10 1903 patch \u201creleased in late October,\u201d still throws both Start and Search errors, as Lawrence Abrams discusses in BleepingComputer<\/a>.<\/p>\n Continuing problems with RDP, disconnects and unresponsive VMs<\/strong><\/p>\n Microsoft has had another lingering problem \u2013 this one with disconnected Remote Desktop connections triggering big time redline<\/a> spikes \u2013 that may be solved in this month\u2019s second (\u201coptional\u201d non-security) cumulative update for Win10 version 1903. That bug, and one described by Noel Carboni<\/a> as triggering jitters in mice running over RDP, may be connected to a change in display driver model used in RDP.<\/p>\n There\u2019s a post on the Microsoft Answers forum from Kevin Marchant<\/a> that complains about the \u201chigh CPU after disconnecting\u201d problem on Win10 1903, which is now marked \u201c*** PROBLEM RESOLVED BY KB4522355 RELEASED OCTOBER 24TH 2019. ***\u201d<\/p>\n It\u2019s possible that the KB 4522355 cumulative update may have fixed the problem. This is one (of many!) changes listed in the KB article:<\/p>\n “Addresses an issue with high CPU usage in Desktop Window Manager (dwm.exe) when you disconnect from a Remote Desktop Protocol (RDP) session.”<\/p>\n It\u2019s still too early to tell, but that may have finally fixed the bug.<\/p>\n Older programs using Visual Basic on Win10 1903 throw \u201cunexpected error\u201d<\/strong><\/p>\n It took a while for this one to surface, but it appears as if older programs running on 32-bit Win10 Home version 1903 may fall over with the error \u201cunexpected error; quitting<\/a>.\u201d Granted, there aren\u2019t many people running programs on Win10 1903 that use VBRUN300.CLL \u2013 the apparent proximate cause of the error message \u2013 but Microsoft hasn\u2019t acknowledged the problem.<\/p>\n I\u2019m also seeing reports of the Win10 version 1903 cumulative updates for both September and October causing a Realtek LAN adapter<\/a> to stop working with an Error 10. Again, the problem hasn\u2019t been officially acknowledged.<\/p>\n Don\u2019t get me started on the Autopilot sorta-security patch<\/a> that was pushed out the automatic update chute then pulled without any warning or description. A Microsoft engineer has confessed<\/a> that they made a mistake in releasing it \u2013 and, no, you don\u2019t need to uninstall it.<\/p>\n We\u2019re still shaking our fists at clouds <\/em>on AskWoody<\/em><\/a>.<\/em><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Tue, 29 Oct 2019 12:18:00 -0700<\/strong><\/p>\n October started out on an extraordinarily low note. On Oct. 3, Microsoft released an \u201cout of band\u201d security update to protect all Windows users from an Internet Explorer scripting engine bug, CVE-2019-1367<\/a>, once thought to be an imminent danger to all things (and all versions) Windows.<\/p>\n It was the third attempt to fix that security hole and each of the versions brought its own set of bugs<\/a>.<\/p>\n<\/p>\n