Microsoft is offering an emergency Windows patch to disable Intel’s Spectre fix which is “buggy”

The way things are going for the Spectre issue is not even funny anymore. First Intel rolls out a patch for the Spectre fix, then it started rebooting the PC, and then Microsoft rolls out of emergency windows patches to undo it. In fact, some of the OEMs are not asking to roll back the BIOS patches as well.

So if you are seeing a random reboot for your Windows 10 PC, and losing data now, and then, its time to install the Microsoft’s latest patch (KB4078130), and its only for the Intel PCs, and not for AMD.

While Intel tests, updates and deploys new microcode, we are making available an out-of-band update today, KB4078130, that specifically disables only the mitigation against CVE-2017-5715 – “Branch target injection vulnerability.” In our testing, this update has been found to prevent the described behavior in devices that have affected microcode. For the full list of affected devices, see Intel’s microcode revision guidance. This update covers Windows 7 (SP1), Windows 8.1, and all versions of Windows 10, for client and server. If you are running an affected device, this update can be applied by downloading it from the Microsoft Update Catalog website. Application of this payload specifically disables only the mitigation against CVE-2017-5715 – “Branch target injection vulnerability.

That said, Microsoft is not rolling out this update through the Windows 10 Update, and instead of asking to manually download it, and install it. This also means that it might have affected some of the users. While its safe to say that unless you are having this kind of issue, stay from the update, but I would highly recommend you to download and keep it with you in case you need it.

That said, here is a twist to the story which again looks pretty messed up. According to the PCWorld,

Microsoft is allowing users to edit the Windows registry to toggle the mitigations on or off. (Instructions are here.) It’s possible to toggle Microsoft’s patch off, and then, when Intel solves its own patching problem, re-enable it. That scenario is actually what Microsoft recommends—again, only if you’ve noticed system instability and want to take action against it.


Yogesh Mankani is a freelance content writer from last 6 years. His passion for blogging, giving words to his ideas and thoughts is what makes him fall more in love with his profession which he takes very personally.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.