Windows 10: KB4100347 Intel microcode updates for Windows 10 v1803 - September 13

Page 28 of 40 FirstFirst ... 18262728293038 ... LastLast
  1.    3 Weeks Ago #270

    andyouf said: View Post
    You'd think an Intel document would have the processors in their proper place with the correct CPUIDs.

    Why are you retaining 0x22 instead of updating?

    Would a BIOS update change microcode versions on the CPU (say to 0x24) or that is at a higher level and just BIOS versions are changed? Are BIOS updates ongoing or is one update a permanent fix (or mitigation) for both Spectre and Meltdown?
    Because I think 0x24 and 0x25 contain only Spectre updates, and I'm choosing not to run them for performance reasons. Measurable CPU slowdowns don't help a gaming rig in any way. For the work laptop, I don't care about the penalties, I want to be secure as it's almost a 24/7 machine.
      My ComputersSystem Spec


  2. Posts : 71
    Win10 Pro x64 / WinServer 2016 Essentials
       3 Weeks Ago #271

    Ben Hastings said: View Post
    My thoughts on this update:


    • A lot more CPUs are supported, even down to Sandy Bridge. This is good.
    • Some CPUs are still missing, like the Intel Celeron N3050 even though Intel has released microcode for these.
    • Indeed I was able to confirm on my devices that the update will come via Windows Update if it was previously installed on the 1709 build. However, this is not shown in the update history in the Settings GUI
    Also microcode versions are way behind! Intel publications of 13 July 2018 for several CPU's.
      My ComputerSystem Spec

  3.    3 Weeks Ago #272

    winactive said: View Post
    Because I think 0x24 and 0x25 contain only Spectre updates, and I'm choosing not to run them for performance reasons. Measurable CPU slowdowns don't help a gaming rig in any way. For the work laptop, I don't care about the penalties, I want to be secure as it's almost a 24/7 machine.
    Why not use InSpectre to disable? Just a different route you are taking? Is Spectre a harder performance hit than Meltdown since it deals with the speculative execution issue?
      My ComputerSystem Spec

  4.    3 Weeks Ago #273

    andyouf said: View Post
    Why not use InSpectre to disable? Just a different route you are taking? Is Spectre a harder performance hit than Meltdown since it deals with the speculative execution issue?
    Some Spectre variants need uCode and OS to mitigate. The uCode I have is in the UEFI. It won't be changed unless software tries to patch it, in which case I hide the update. Plus then I know if the Cumulative causes an issue, it's not because of Spectre. Software can easily be altered (reconfigured) and MS are throwing the switch automatically.

    If I used InSpectre or registry to turn it on and off, then MS could turn it back on. I can spot a uCode update in the installed updates easily if anything is downloaded other than the cumulative. If the cumulative tries to turn it back on, it can't because the uCode isn't there. Just call it prior experience of WU.

    Yes Spectre is harder on performance than Meltdown. Plus I don't want to disable Meltdown and I won't if I don't mess with the OS.
      My ComputersSystem Spec

  5.    3 Weeks Ago #274

    Ah I see. I had seen discussion with you and other users talking about needing to hide updates because it was already patched at UEFI and I'm guessing making sure auto-update is off (pro only feature?) But then I thought I read that if the OS update recognizes that UEFI had been updated then it doesn't apply itself.

    winactive said: View Post
    Just call it prior experience of WU.
    Yes, I think with pro users you can do this in settings but I yesterday had to dl that "wushowhide" tool because WU update kept insisting an Intel graphics driver from '16 was more applicable than the one from 2/18 I had just installed. I checked for updates (I do manually all the time I don't know why) and there it goes throwing the old one back on, laughing at me.

    *Oddly, I saw an MS Silverlight update that was already hidden when I first opened the tool.
      My ComputerSystem Spec

  6.    3 Weeks Ago #275

    andyouf said: View Post
    Ah I see. I had seen discussion with you and other users talking about needing to hide updates because it was already patched at UEFI and I'm guessing making sure auto-update is off (pro only feature?) But then I thought I read that if the OS update recognizes that UEFI had been updated then it doesn't apply itself.



    Yes, I think with pro users you can do this in settings but I yesterday had to dl that "wushowhide" tool because WU update kept insisting an Intel graphics driver from '16 was more applicable than the one from 2/18 I had just installed. I checked for updates (I do manually all the time I don't know why) and there it goes throwing the old one back on, laughing at me.

    *Oddly, I saw an MS Silverlight update that was already hidden when I first opened the tool.
    Yes, unfortunately I'm in the same boat as you, I have to use wushowhide.cab

    Hiding KB4100347 blocks it for me. Not really sure of the wushowhide mechanism either, does it work on the description or the KB number? I'd have to assume the latter. All I know is HWiNFO shows me on 0x22 and that's what's in my UEFI so that's good enough for me.
      My ComputersSystem Spec

  7.    3 Weeks Ago #276

    winactive said: View Post
    Currently, I run uCode 0x22 (pre-Spectre) so I don't make any adjustments to the OS registry.

    Thank you for the registry file @ddelo. It will be very useful with the remarks within.
    You're welcome.

    As for your above statement, I believe that since your BIOS/UEFI is not patched with the appropriate (according to intel) μcode and your CPU is identified as vulnerable, you need to make the registry entries, to be able to receive the Microsoft updates with the mitigations.
    After all that's why the Microsoft updates exist. To cover your a**, while waiting for a BIOS/UEFI update.
      My ComputerSystem Spec

  8.    3 Weeks Ago #277

    ddelo said: View Post
    You're welcome.

    As for your above statement, I believe that since your BIOS/UEFI is not patched with the appropriate (according to intel) μcode and your CPU is identified as vulnerable, you need to make the registry entries, to be able to receive the Microsoft updates with the mitigations.
    Thank you but for this machine I am trying to avoid the uCode and mitigations. :)
      My ComputersSystem Spec

  9.    3 Weeks Ago #278

    winactive said: View Post
    Thank you but for this machine I am trying to avoid the uCode and mitigations. :)
    As long as you're aware of the issue and possible risks, you do what you believe is right for you!
      My ComputerSystem Spec

  10.    3 Weeks Ago #279

    winactive said: View Post
    Yes, unfortunately I'm in the same boat as you, I have to use wushowhide.cab

    Hiding KB4100347 blocks it for me. Not really sure of the wushowhide mechanism either, does it work on the description or the KB number? I'd have to assume the latter. All I know is HWiNFO shows me on 0x22 and that's what's in my UEFI so that's good enough for me.
    I don't know, for my hidden Intel display adapter there is no KB# just the version. I'd think the KB also since that is the version otherwise the title with date would seem odd.
      My ComputerSystem Spec


 
Page 28 of 40 FirstFirst ... 18262728293038 ... LastLast

Related Threads
Source: https://support.microsoft.com/en-us/help/4091666/kb4091666-intel-microcode-updates See also: KB 4093836 Summary of Intel microcode updates KB4100347 Intel microcode updates for Windows 10 v1803 - Windows 10 Forums KB4090007 Intel...
Source: https://support.microsoft.com/en-us/help/4091664/kb4091664-intel-microcode-updates See also: KB4346087 Intel microcode updates for Windows 10 v1607 - August 21 - Windows 10 Forums See also: KB 4093836 Summary of Intel microcode...
Source: https://support.microsoft.com/en-us/help/4091663/kb4091663-intel-microcode-updates See also: KB4346085 Intel microcode updates for Windows 10 v1709 - August 21 - Windows 10 Forums See also: KB 4093836 Summary of Intel microcode...
Source: https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates See also: KB 4093836 Summary of Intel microcode updates KB4100347 Intel microcode updates for Windows 10 v1803 - Windows 10 Forums KB4091663 Intel microcode...
Solved Intel microcode updates for 1803? in Drivers and Hardware
Is this available for download?
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 15:39.
Find Us