Windows 10: Windows Client Guidance against speculative execution vulnerabilities

Page 38 of 64 FirstFirst ... 28363738394048 ... LastLast
  1.    27 Jan 2018 #370

    [QUOTE=fdegrove;1279698]Hi,



    That may be true for very old machines. Nowadays any bios worth its salt can be recovered.
    In my entire career as a pc engineer I've never seen a single machine that couldn't been recovered unless it had hardware damage.

    [As far as I know, Window sdoes not have the ability to load microcode after the fact, superseding what is in the BIOS (but I may be wrong on this if Microsoft is, in fact, offering update(s) via WU that are microcode-specific, as we seem to be seeing here recently). And if it does, then they have been doing this all along without many of us knowing about it.

    But when the OS makes use of newer microcode, it does not overwrite the BIOS / UEFI./QUOTE]

    It is possible to load microcode in Windows through third party software (from VMWare for instance) but I've never seen any evidence of microcode being updated by Windows itself, not ever. If it does then I'd like to see evidence of it.

    Cheers,
    I have legacy BIOS so the Problem is in my BIOS not in Windows or anything else. MSI probably will never upgrade my BIOS so I am at their mercy.
      My ComputerSystem Spec


  2. Posts : 1,471
    WinX Pro x64 IP current
       27 Jan 2018 #371

    Josey Wales said: View Post
    FUD, Maybe you ought to tell Intel that. Well since I do not know everything involved on this Planet, I will listen to the head of Intel --You can listen to whoever you please.
    I'm sorry, I know that I said I wasn't going to argue with you anymore, but if you want to laugh, then I'll get the last laugh on you.

    You prefer to trust the CEO of Intel, (while at the same time saying this is all Intel's fault), after he made MILLIONS on stock sale after the vulnerability was revealed to them:

    Intel CEO dumped stocks\ - Google Search

    Read any of those links. I read most of them in the beginning.

    Now, keep laughing, buddy, because apparently you think you know a lot because of media report bullshit, but I'm here to tell you, you are in the wrong of this.

    Stock slides lmfao - In case you missed it, as of yesterday, their stock is UP 10% to over 50, first time since 2000.

    Furthermore, that nice little report you quoted - notice how ARM said most of its processors were not affected?

    NOT ALL, just most.

    I've done more than enough research on this topic, and you can continue to post all your FUD, but buddy, you're flat out wrong.

    And you can take that to the bank.

    [QUOTE=fdegrove;1279698]Hi,



    That may be true for very old machines. Nowadays any bios worth its salt can be recovered.
    In my entire career as a pc engineer I've never seen a single machine that couldn't been recovered unless it had hardware damage.

    [As far as I know, Window sdoes not have the ability to load microcode after the fact, superseding what is in the BIOS (but I may be wrong on this if Microsoft is, in fact, offering update(s) via WU that are microcode-specific, as we seem to be seeing here recently). And if it does, then they have been doing this all along without many of us knowing about it.

    But when the OS makes use of newer microcode, it does not overwrite the BIOS / UEFI./QUOTE]

    It is possible to load microcode in Windows through third party software (from VMWare for instance) but I've never seen any evidence of microcode being updated by Windows itself, not ever. If it does then I'd like to see evidence of it.

    Cheers,
    ^^^^ this - I've not ever seen evidence that Windows has ever done this in the past - which is why I was completely floored to learn that this could even be done in the first place.

    And that VMWare utility is how I learned of the microcode releases by Intel in the first place. I spent a few days trying to see if there was a way I could put this into Windows myself lol. But, alas, it requires kernel level access....
      My ComputersSystem Spec

  3.    27 Jan 2018 #372

    Hi,

    I have legacy BIOS so the Problem is in my BIOS not in Windows or anything else. MSI probably will never upgrade my BIOS so I am at their mercy.
    The problem is with the OS as well as it is the way it "talks" to the cpu that is actually part of the source of the vulnerabilities.

    Cheers,
      My ComputersSystem Spec

  4.    27 Jan 2018 #373

    fdegrove said: View Post
    Hi,



    The problem is with the OS as well as it is the way it "talks" to the cpu that is actually part of the source of the vulnerabilities.

    Cheers,
    Yes I get that but if The Chip makers did not produce faulty chips The OS would not have a problem now would it?
      My ComputerSystem Spec


  5. Posts : 32,359
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       27 Jan 2018 #374

    fdegrove said: View Post
    Hi,



    That may be true for very old machines. Nowadays any bios worth its salt can be recovered.
    In my entire career as a pc engineer I've never seen a single machine that couldn't been recovered unless it had hardware damage.



    It is possible to load microcode in Windows through third party software (from VMWare for instance) but I've never seen any evidence of microcode being updated by Windows itself, not ever. If it does then I'd like to see evidence of it.
    Microcode that's incompatible with the cpu present won't load.
    You can't flash a bios with an incompatible bios if the flashing programme is written properly. Ditto for MC updates.

    Cheers,
    Maybe I'm totally misinterpreting all this, but with my Surface Pro 3, that is how I have received BIOS and other firmware updates in the past. Thru Windows Update. Download Surface Pro 3 from Official Microsoft Download Center
      My ComputersSystem Spec

  6.    27 Jan 2018 #375

    f14tomcat said: View Post
    Maybe I'm totally misinterpreting all this, but with my Surface Pro 3, that is how I have received BIOS and other firmware updates in the past. Thru Windows Update. Download Surface Pro 3 from Official Microsoft Download Center
    Probably because MS makes The Surface Pro 3
      My ComputerSystem Spec


  7. Posts : 19,780
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       27 Jan 2018 #376

    f14tomcat said: View Post
    Maybe I'm totally misinterpreting all this, but with my Surface Pro 3, that is how I have received BIOS and other firmware updates in the past. Thru Windows Update. Download Surface Pro 3 from Official Microsoft Download Center
    Maybe the Surface has an integrated Bios updater? Surface Firmware Tool.msi
      My ComputersSystem Spec


  8. Posts : 32,359
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       27 Jan 2018 #377

    Josey Wales said: View Post
    Probably because MS makes The Surface Pro 3
    Exactly. So the ability is there. Not like it's impossible for some technical reason.
      My ComputersSystem Spec


  • Posts : 19,780
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       27 Jan 2018 #378

    Firmware
    Surface Pro 3 device firmware is provided as a driver package and can be updated by deploying the latest firmware
    drivers from the Firmware and Driver pack to the device. This process can be performed during deployment, as is
    described in Chapter 3. However, when new firmware is deployed to an existing device, the process can be a bit more
    complicated. The firmware updates are made available through the standard Windows Update channel, so if your
    Surface Pro 3 device receives updates directly from Windows Update, it will be updated automatically. The firmware
    updates are not made available for use with Windows Server Update Services (WSUS), so if your organization manages
    updates with WSUS, the firmware must be deployed separately.
    Note: To deploy updated firmware without performing an operating system deployment, the following PowerShell
    script can be placed in the root folder of the extracted Firmware and Driver Pack. To save this PowerShell script, copy
    the text into Notepad and save the file as a .ps1 file.
    Code:
    $ScriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition
    $files = get-childitem -path $Scriptpath -recurse -filter *.inf
    foreach ($file in $files)
    {
    Write-host "Injecting driver $file"
    pnputil -i -a $file.FullName
    }
    Asset Tagging
    The firmware of Surface Pro 3 devices supports asset tagging, where a customized string used to identify a device can be
    written directly into the firmware of the device. This enables devices to be easily tracked and identified, even when the
    operating system is changed through deployment or when the device is passed between users. The process for writing
    the asset tag is covered in the Asset Tagging section of Chapter 8.
    Download Deployment and Administration Guide for Surface Pro 3 from Official Microsoft Download Center
      My ComputersSystem Spec

  •    27 Jan 2018 #379

    Hi,

    Josey Wales said: View Post
    Probably because MS makes The Surface Pro 3
    Exactly. But that also implies this is not the case for machines not made by MS.

    Firmware updates that flash firmwares can often be run from within Windows but are either released through the OEM which get them in some cases form their Intel partnership or are written entirely in house.

    Cheers,
      My ComputersSystem Spec


  •  
    Page 38 of 64 FirstFirst ... 28363738394048 ... 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 14:22.
    Find Us