![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security5-100734739-large.3x2.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Mon, 08 Jan 2018 05:28:00 -0800<\/strong><\/p>\n Microsoft\u2019s hasty Meltdown\/Spectre patches,\u00a0released late on Jan. 4<\/a>, have started baring their fangs. Complaints about Win10 Fall Creators Update cumulative update KB 4056892 and Win7 Monthly Rollup KB 4056894 resulting in blue screens \u2014 particularly on AMD Athlon, Sempron, Opteron and Turion processors \u2014 started appearing shortly after the patches were released<\/a>.<\/p>\n With no notice or warning, Microsoft moved the Win7 patch, KB 4056894, from version 1 to version 2 on Jan. 5. As of early Monday morning, Jan. 8, version 2 is the only version available on the Microsoft Update Catalog<\/a>. The Win10 1709 patch, KB 4056892, is still at version 1.<\/p>\n According to @abbodi86 on AskWoody<\/a>, the jump from version 1 to version 2 was a metadata change \u2014 generally, a change in the way the patch is installed. The KB 4056894 patch itself didn’t change. Microsoft hasn\u2019t said anything.<\/p>\n I now see blue screen complaints on the AskWoody Lounge<\/a>, the Microsoft Answers forum<\/a>, Microsoft\u2019s TechNet forum<\/a>, on Reddit<\/a>, on MyDigitalLife<\/a>, on OverclockersUK<\/a>, and in many non-English forums<\/a>.<\/p>\n Many of the reports don\u2019t include details about the processor type or Windows version, but it\u2019s clear that AMD processors \u2014 which aren\u2019t even affected by the Meltdown vulnerability \u2014 are getting hurt the worst. That said, there are sporadic reports of other kinds of processors taking it in the shorts.<\/p>\n Oddly, all of the Win7 blue screen reports I’ve seen are associated with the 2018-01 Monthly Rollup. The manual-download Security Only update hasn’t had as many problems. Or, at least, as many reported problems.<\/p>\n Proposed fixes run a dime a dozen, but the most reliable seem to be these:<\/p>\n That said, there\u2019s at least one frustrated admin on Reddit who\u2019s tried everything<\/a> and can\u2019t seem to get any of the suggestions to work.<\/p>\n If you get your machine back and working, make sure you follow the general steps for blocking updates<\/a> until Microsoft cleans up its mess. (Win10 Pro 1703 or 1709 customers have an easier job<\/a>.) In Win7 or 8.1, simply turn off Automatic Update.<\/p>\n What I find most distressing: All of this angst is for nothing. Yes, you need to install the Meltdown\/Spectre fixes at some point, but as of this moment there are no known exploits in the wild. None.<\/p>\n No matter what the gurus on TV or in the mainstream media say, there\u2019s no reason to get these patches installed before Microsoft works out the bugs. None.<\/p>\n Chalk this up as yet another example of why you need to wait a while<\/a> after Windows patches get pushed out the automatic update chute. In spite of the scare tactics.<\/p>\n We\u2019ll keep you up to date on the latest repair techniques on the <\/em>AskWoody Lounge<\/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: Mon, 08 Jan 2018 05:28:00 -0800<\/strong><\/p>\n Microsoft\u2019s hasty Meltdown\/Spectre patches,\u00a0released late on Jan. 4<\/a>, have started baring their fangs. Complaints about Win10 Fall Creators Update cumulative update KB 4056892 and Win7 Monthly Rollup KB 4056894 resulting in blue screens \u2014 particularly on AMD Athlon, Sempron, Opteron and Turion processors \u2014 started appearing shortly after the patches were released<\/a>.<\/p>\n<\/p>\n