The Spectre vulnerability took the tech world by surprise. April’s Patch Tuesday bring a new Spectre update for Windows 10 FCU computers adding an extra layer of protection against this threat.
As Microsoft explains, update KB4093112 provides support to control usage of Indirect Branch Prediction Barrier (IBPB) within some AMD processors (CPUs) for mitigating CVE-2017-5715, Spectre Variant 2 when switching from user context to kernel context.
So, if you know that your computer is vulnerable to Spectre, then you should install KB4093112 as soon as possible.
Speaking of which, if you haven’t tested your computer yet to learn whether your machine is vulnerable to Spectre or not, you can use one of the two tools listed below:
- Download InSpectre to check for CPU performance issues
- Download this tool to check if computer is vulnerable to Meltdown & Spectre
This is not the only improvement that KB4093112 brings. The update also fixes a series of other bugs that include:
- Addressed the issue that caused access violation errors in IE when running on the Microsoft Application Virtualization platform.
- Fixed the issue that redirected users to Internet Explorer and Microsoft Edge.
- Access violation errors in Internet Explorer when rendering SVGs under a high load should no longer occur.
- Time zone information bugs have been fixed.
- Addressed the issues that might cause the App-V service to stop working.
- Fixed document.execCommand(“copy”) false returns in Internet Explorer.
- Custom controls identification issues in IE have been fixed
- Security updates to Internet Explorer, Microsoft Edge, Windows kpp platform and frameworks, Microsoft scripting engine, Windows graphics, Windows Server, Windows kernel, Windows datacenter networking, Windows wireless networking, Windows virtualization and Kernel, and Windows Hyper-V.
For more information, you can also check out KB4093112’s support page.
Some users may not be able to install this update on their computers due to error 0x80070643. In this case, simply check for updates again.
Keep in mind that in some cases, even though the update was successfully installed, Windows Update incorrectly reports that it failed to install. To make sure that you actually installed KB4093112, go to your update history and you should find this patch on the list of the installed updates.
As always, feel free to use the comments below to tell us more about your KB4093112 update experience. Did you encounter any other issues during the install process or afterwards?
RELATED STORIES TO CHECK OUT: