Windows Client Guidance against speculative execution vulnerabilities

Page 56 of 75 FirstFirst ... 646545556575866 ... LastLast

  1. Posts : 2,422
    Windows 10 Pro x64
       #550

    Your first screenshot (before BIOS update) is indeed weird....(Protected and Enable Spectre Protection).
    Now if you were not running InSpectre as Admin, pressing the button wouldn't have done anything.
    On the other hand, Inspectre, is just software and might have bugs!!!
      My Computer


  2. Posts : 2,422
    Windows 10 Pro x64
       #551

    Eagle51 said:
    Sorry, when I said InSpectre told I'm good ... I actually meant that it said I was protected and that it showed System is Spectre Protected YES, yet showed the Enable Spectre Protection button, which If I clicked on it never actually did anything and made me question if I was actually protected. After the BIOS update it shows System is Spectre Protected YES and the Disable Spectre Protection Button.

    Before BIOS Update
    Attachment 182872
    After BIOS Update
    Attachment 182873

    And come to think of it...since software bugs are only fixed when users report them, may I suggest that you take the time to send your two screenshots to the good folks at Gibson Research and let them know of this?
      My Computer


  3. Posts : 1,471
    Win10 Home x64 - 1809
       #552

    Your first screenshot (before BIOS update) is indeed weird....(Protected and Enable Spectre Protection).
    Now if you were not running InSpectre as Admin, pressing the button wouldn't have done anything.
    On the other hand, Inspectre, is just software and might have bugs!!!
    Yep, I ran it as Admin .... I'm guessing it was the cpumcupdate microcode patch and they way it's applied (ie. windows loading a driver) vs the BIOS update which I consider an actual microcode update :)
      My Computers


  4. Posts : 2,826
    Windows 10 Pro X64
       #553

    Hi,

    axe0 said:
    Do you have a source on this?
    I'll have took it up but that's just how it works and that's why a bios/efi MCU update is so much better as it is entirely OS independent and definite (unless you reflash the bios/efi of course).

    Cheers,
      My Computers


  5. Posts : 2,422
    Windows 10 Pro x64
       #554

    Eagle51 said:
    Yep, I ran it as Admin .... I'm guessing it was the cpumcupdate microcode patch and they way it's applied (ie. windows loading a driver) vs the BIOS update which I consider an actual microcode update :)

    Ahaaa.... :) you were tricking poor old InSpectre!!!
    I guess that is why you had it enabled. It sounds sensible!
      My Computer


  6. Posts : 3,446
       #555

    Remember the MCU update is for mitigation only - i.e it alters SMBIOS - software (eg. drivers) can be circumvented... just saying (anyway as interesting as it is, it's a storm in a tea-cup IMHO)
      My Computer


  7. Posts : 345
    Windows 10
       #556

    Intel has released microcode updates for more processors, but they've also cancelled development of microcode for some older processors.

    https://newsroom.intel.com/wp-conten...e-guidance.pdf
      My Computer


  8. Posts : 7,086
    Windows 10 Pro 64 bit
       #557

    Ground Sloth said:
    Intel has released microcode updates for more processors, but they've also cancelled development of microcode for some older processors.

    https://newsroom.intel.com/wp-conten...e-guidance.pdf
    I support a 3rd gen. Ivy Bridge (i5-3570k) & 4th gen. Haswell (i5 4670K) based PCs. The Intel guide above mentions only mobile processors related to Ivy Bridge & Haswell. I assume the desktop CPU fixes are being worked on but this isn't stated in the table for some reason.
      My Computers


  9. Posts : 345
    Windows 10
       #558

    Steve C said:
    I support a 3rd gen. Ivy Bridge (i5-3570k) & 4th gen. Haswell (i5 4670K) based PCs. The Intel guide above mentions only mobile processors related to Ivy Bridge & Haswell. I assume the desktop CPU fixes are being worked on but this isn't stated in the table for some reason.

    If Intel were working on microcode updates for desktop Ivy Bridge and Haswell processors, you would think it would be stated in the guidance. What makes the omission even more strange is the fact that Intel has released microcode updates for first and second generation desktop Core processors.
      My Computer


  10. Posts : 2,663
    Windows 11 21H2 (22000.593)
       #559

    Ground Sloth said:
    If Intel were working on microcode updates for desktop Ivy Bridge and Haswell processors, you would think it would be stated in the guidance. What makes the omission even more strange is the fact that Intel has released microcode updates for first and second generation desktop Core processors.
    The microcode is update for Bloomfield?
      My Computers


 

  Related Discussions
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 18:22.
Find Us




Windows 10 Forums