Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14 Win Update

Page 31 of 31 FirstFirst ... 21293031
  1. ddelo's Avatar
    Posts : 1,819
    Windows 10 Pro x64
       #300

    Ooops, I'm sorry about the last part. I didn't see that you had updated your post, regarding MDS enablement via registry!
    With which, seems that we agree.....
      My Computer


  2. Posts : 110
    Windows 10 Pro 1903
       #301

    ddelo said:
    Ooops, I'm sorry about the last part. I didn't see that you had updated your post, regarding MDS enablement via registry!
    With which, seems that we agree.....

    Not totally agree,


    It is not clear if you enable mitigation for CVE-2018-3639, will keep MDS enabled,

    Microsoft state:

    To enable mitigations for Microarchitectural Data Sampling (CVE-2018-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130) along with Spectre (CVE-2017-5753 & CVE-2017-5715) and Meltdown (CVE-2017-5754) variants, including Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) as well as L1 Terminal Fault (L1TF) (CVE-2018-3615, CVE-2018-3620, and CVE-2018-3646) without disabling Hyper-Threading:


    To be in the safe side, use the value 72, can't be sure unless the new Microcode released and tested,
      My Computer

  3. ddelo's Avatar
    Posts : 1,819
    Windows 10 Pro x64
       #302

    JenyJ said:

    Not totally agree,


    It is not clear if you enable mitigation for CVE-2018-3639, will keep MDS enabled,

    Microsoft state:

    To enable mitigations for Microarchitectural Data Sampling (CVE-2018-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130) along with Spectre (CVE-2017-5753 & CVE-2017-5715) and Meltdown (CVE-2017-5754) variants, including Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) as well as L1 Terminal Fault (L1TF) (CVE-2018-3615, CVE-2018-3620, and CVE-2018-3646) without disabling Hyper-Threading:


    To be in the safe side, use the value 72, can't be sure unless the new Microcode released and tested,

    OK... your opinion and I fully respect it.

    To end this "misalignment" between us, please take a look at the first post of this thread:
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-mds_registry_entries.png

    Which is fully inline with the output of Speculation control:
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-mds_withoutregentries.png

    Meaning that, adding the Registry entries "FeatureSettingsOverride" (0x048) and "FeatureSettingsOverrideMask" (0x003), is redundant as the CU KB4494441, has already enabled them, for MDS mitigation!
    But as you said, it won't hurt if you also do it manually!
    ---End
    Last edited by ddelo; 19 May 2019 at 05:32.
      My Computer

  4. Brink's Avatar
    Posts : 48,615
    64-bit Windows 10 Pro for Workstations build 19631
    Thread Starter
       #303
      My Computers


  5. Posts : 16
    Windows 10 Pro
       #304

    Hi, can anyone tell me what can i do with the vulnerable direct and indirect branch and the others (except the new side channel vulnerabilities)?

    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-untitled.jpg

    Thanks!!!
      My Computer


  6. Posts : 548
    Windows 10
       #305

    NiceAndShy said:
    Okay I've got a problem here.

    I had 3 updates that were at "Pending restart":
    --The Adobe Flash Security Update
    --The 2019/05 cumulative update
    --The Microsoft frameworks update.

    However, before I could do the restart my Windows 10 PC crashed and I had to shut it down by pulling out the power cable and then turning it back on.

    It seems that the Adobe Flash Security Update and the Microsoft Frameworks update both installed, but the 2019/05 cumulative update didn't?

    It says that the 2019/05 cumulative update is "pending restart" but it also says that it was installed when I check "View update history".
    Should I just try restarting again to complete the install?
      My Computer


  7. Posts : 16
    Windows 10 Pro
       #306

    NiceAndShy said:
    Should I just try restarting again to complete the install?
    Check winver (win+r: winver). If you have the latest version of Windows (the update was installed and it's trying to install it again), hide the "duplicated" update with this: https://download.microsoft.com/downl...owhide.diagcab
      My Computer


  8. HempOil's Avatar
    Posts : 8
    Windows 10
       #307

    JenyJ said:
    Yes! you have updated correctly, and you have now the latest firmware

    - - - Updated - - -



    I big to differ, these values still enable other mitigations than the retpoline,

    The best is to set it to 72 waiting for the microcode

    - - - Updated - - -



    What is your CPU?
    My CPU is a Core i7-2630QM.
      My Computer

  9. HempOil's Avatar
    Posts : 8
    Windows 10
       #308

    Just an FYI that I got some guidance over at Wilders. I applied the KB4465065 standalone update. This upgraded me to the 0x2E microcode and with the already applied registry keys, I now have SSBD mitigated.

    I'm not sure why my microcode was stuck at 0x2D prior to applying the update. The only fishy thing that occurred recently was a BSOD after an automatic Windows cumulative update (KB4494441, I believe). My PC also experienced a BSOD after I applied the KB4465065 standalone update. I ran both crashes through WhoCrashed. It identified the HAL as the culprit. Perhaps, the blue screens have something to do with the microcode updates not getting applied?

    The only question that remains is whether to keep hyperthreading enabled or disabled! Google decided to disable it on all Chromebooks.
      My Computer


 
Page 31 of 31 FirstFirst ... 21293031

Related Threads
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 19:52.
Find Us




Windows 10 Forums