Windows Client Guidance against speculative execution vulnerabilities
-
-
-
-
Build 16299.192 & latest BIOS
-
Installed the latest update of Windows and this is how it looks for me, apparently it is for many users like this and means the Spectre bug hasn't been completely patched with a BIOS update. I flashed the latest BIOS version yesterday to patch a previous security problem.
Attachment 171011
Yesterday I received both the Cumulative update, and a BIOS update.
But the BIOS update made no mention about these two problems, or the ME(in BIOS, not the driver inside of Windows) problem. But the SA 00086 tool say's I'm good to go too.
So ASUS is on the ball(with the new Z370 boards at least)
Version 1003 2018/01/02
8.23 MBytes
ROG MAXIMUS X HERO BIOS 1003
Improve system performance.
Improved DRAM compatibility
-
-
Installed the latest update of Windows and this is how it looks for me, apparently it is for many users like this and means the Spectre bug hasn't been completely patched with a BIOS update. I flashed the latest BIOS version yesterday to patch a previous security problem.
Attachment 171011
Many OEM's have only the ME bug patch dated pre 12/2017... maybe they are still testing new patches?
-
For a laugh, here are the results of my scan on my eVGA X58-based mobo with a Core i7 965 EE (full specs in my profile):
I included the full screenshot to show others what exactly I did from the point of opening PowerShell as Admin from the Start context menu.
Unfortunately, with this hardware being as old as it is, I doubt I will receive any sort of BIOS update for it - the last was almost 7 years ago now.
-
For a laugh, here are the results of my scan on my eVGA X58-based mobo with a Core i7 965 EE (full specs in my profile):
I included the full screenshot to show others what exactly I did from the point of opening PowerShell as Admin from the Start context menu.
Unfortunately,
with this hardware being as old as it is, I doubt I will receive any sort of BIOS update for it - the last was almost 7 years ago now.
That board(and CPU are definitely EOL
-
If this is so serious and Microsoft and Intel were informed in June or July..Why so long to even attempt to fix this?
-
If this is so serious and Microsoft and Intel were informed in June or July..Why so long to even attempt to fix this?
I would guess: because this is something that Intel, their board partners(the OEMs), and the myriad operating system developers, HAVE to get right the first time around.
-
-
The above PowerShell com mands don't work for me running the latest version of W10 Pro. What do users need to do to run these commands?
In Windows 17046 I start Powershell as Administrator. I check policyexecution status. Then I run Install-Module SpeculationControl. I get this:
What am I doing wrong?
EDIT: Works okay in 16299.192.