Windows 10: Windows Client Guidance against speculative execution vulnerabilities

Page 2 of 73 FirstFirst 12341252 ... LastLast
  1.    05 Jan 2018 #10

    Latest Windows Insider build which supposedly already has the fix applied:



      My ComputerSystem Spec

  2.    05 Jan 2018 #11

    Cliff S said: View Post
    Are you guys running as admin?

    It will want to install nuget first if you don't have it installed yet(like if you are a Chocolatey user).
    I got these commends to work by letting PowerShell install nuget and enabling PowerShell scripts (under Settings / Developer Options).

    Change PowerShell Script Execution Policy in Windows 10 General Tips Tutorials
      My ComputersSystem Spec

  3.    05 Jan 2018 #12

    Build 16299.192 & latest BIOS

    Click image for larger version. 

Name:	2018-01-05_101719.jpg 
Views:	9 
Size:	220.8 KB 
ID:	171018
      My ComputerSystem Spec


  4. Posts : 21,006
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       05 Jan 2018 #13

    axe0 said: View Post
    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
      My ComputersSystem Spec

  5.    05 Jan 2018 #14

    axe0 said: View Post
    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?
      My ComputerSystem Spec


  6. Posts : 1,534
    WinX Pro x64 IP current
       05 Jan 2018 #15

    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):

    Click image for larger version. 

Name:	ProcessorCheck.PNG 
Views:	12 
Size:	61.4 KB 
ID:	171024

    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.
      My ComputersSystem Spec


  7. Posts : 21,006
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       05 Jan 2018 #16

    johngalt said: View Post
    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):

    Click image for larger version. 

Name:	ProcessorCheck.PNG 
Views:	12 
Size:	61.4 KB 
ID:	171024

    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
      My ComputersSystem Spec

  8.    05 Jan 2018 #17

    If this is so serious and Microsoft and Intel were informed in June or July..Why so long to even attempt to fix this?
      My ComputerSystem Spec


  9. Posts : 21,006
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       05 Jan 2018 #18

    Josey Wales said: View Post
    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.
      My ComputersSystem Spec


  10. Posts : 549
    Windows 10 Pro 17134.167
       05 Jan 2018 #19

    Steve C said: View Post
    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:

    Click image for larger version. 

Name:	Spec 1.jpg 
Views:	24 
Size:	202.9 KB 
ID:	171030

    What am I doing wrong?

    EDIT: Works okay in 16299.192.
      My ComputerSystem Spec


 
Page 2 of 73 FirstFirst 12341252 ... LastLast

Related Threads
The PowerShell script execution policies enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer. Windows PowerShell has four different execution policies: Execution Policy Description ...
Source: Mitigating speculative execution side-channel attacks in Microsoft Edge and Internet Explorer - Microsoft Edge Dev Blog See also update: Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192 - Windows 10 Forums
Source: Google Online Security Blog: Disclosing vulnerabilities to protect users
Windows 10 - Need some guidance on recovery in Installation and Upgrade
One of my spare Windows 10 machines is on life support. I must have clobbered it somehow when I was tweaking the multiple display settings ( to incorporate a HDMI projector). It actually worked fine all week, but today, when I tired to set it...
Read more: http://www.zdnet.com/article/microsoft-offers-it-guidance-to-prepare-for-windows-as-a-service/
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:14.
Find Us