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

Page 5 of 31 FirstFirst ... 3456715 ... LastLast

  1. Posts : 208
    Win 10
       #40

    I had to install it a second time to get version right, at first I thought that was why Retpoline showed not enabled, but even after still shows not enabled.
    I can of course manually do it unless they changed reg key values.

    Edit, Ok show enabled now with PS but reg shows it is off still.
    Edit2 reg is fine you need to read the MS link :)

    Get-SpeculationControlSettipeculation control settings for CVE-2017-5715 [branch target injection]

    Hardware support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is enabled: True

    Speculation control settings for CVE-2017-5754 [rogue data cache load]

    Hardware requires kernel VA shadowing: True
    Windows OS support for kernel VA shadow is present: True
    Windows OS support for kernel VA shadow is enabled: True
    Windows OS support for PCID performance optimization is enabled: False [not required for security]

    Speculation control settings for CVE-2018-3639 [speculative store bypass]

    Hardware is vulnerable to speculative store bypass: True
    Hardware support for speculative store bypass disable is present: True
    Windows OS support for speculative store bypass disable is present: True
    Windows OS support for speculative store bypass disable is enabled system-wide: False

    Speculation control settings for CVE-2018-3620 [L1 terminal fault]

    Hardware is vulnerable to L1 terminal fault: True
    Windows OS support for L1 terminal fault mitigation is present: True
    Windows OS support for L1 terminal fault mitigation is enabled: True


    BTIHardwarePresent : True
    BTIWindowsSupportPresent : True
    BTIWindowsSupportEnabled : True
    BTIDisabledBySystemPolicy : False
    BTIDisabledByNoHardwareSupport : False
    BTIKernelRetpolineEnabled : True
    BTIKernelImportOptimizationEnabled : True
    KVAShadowRequired : True
    KVAShadowWindowsSupportPresent : True
    KVAShadowWindowsSupportEnabled : True
    KVAShadowPcidEnabled : False
    SSBDWindowsSupportPresent : True
    SSBDHardwareVulnerable : True
    SSBDHardwarePresent : True
    SSBDWindowsSupportEnabledSystemWide : False
    L1TFHardwareVulnerable : True
    L1TFWindowsSupportPresent : True
    L1TFWindowsSupportEnabled : True
    L1TFInvalidPteBit : 45
    L1DFlushSupported : True
    Last edited by EdKiefer; 14 May 2019 at 15:20.
      My Computer


  2. Posts : 856
    Windows 10 Pro 21H2 build 19045.2193 Dual Boot Linux Mint
       #41

    Hmm failed on 503 first time but installed the rest, got 503 on second attempt so all good. Insider build update was OK though got all in one strike!
      My Computers


  3. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #42

    Comp Cmndo said:
    2 tries for everyone!
    Is this what we can look forward to with 1903?
    3 strikes & you're out Microsoft.
    I had 2 tries on 1809 but only one needed on 1903.
      My Computer


  4. Posts : 428
    Windows 11 pro X64 latest
       #43

    @EdKiefer can i have a pic from theese keys?
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-1.jpg
      My Computers


  5. Posts : 4,224
    Windows 10
       #44

    Installed on 4 of 5 current branch machines. I'll install on my wife's PC later tonight. My production PC is now weird after restart during update: the screen stays black until the lock screen comes up. Very strange! On the plus side, this update went extremely quickly. I checked the leftover packages using dism /online /cleanup-image /analyzecomponentstore and it came up with 2 packages in need of clean-up. It's taking FOREVER to run the cleanup, even though the update took virtually no time at all. Sigh.
    --Ed--
      My Computers


  6. Posts : 208
    Win 10
       #45

    boombastik said:
    @EdKiefer can i have a pic from theese keys?
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-1.jpg
    I should of read the link https://support.microsoft.com/en-us/...erabilities-in
    The default is correct, they are not using 400 values.

    FeatureSettings= DWord 800 (2048)
    FeatureSettingsOverride= DWord 0 (0)
    FeatureSettingsOverrideMask = DWord 3(3)

    Note I am not sure on featuresetting as My VM doesn't match so that might be dynamic to the system.
    The important thing si to run the PS script and see results before making changes to reg and back it up so you can revert.
      My Computer


  7. Posts : 2,557
    Windows 10 pro x64-bit
       #46

    EdTittel said:
    Installed on 4 of 5 current branch machines. I'll install on my wife's PC later tonight. My production PC is now weird after restart during update: the screen stays black until the lock screen comes up. Very strange! On the plus side, this update went extremely quickly. I checked the leftover packages using dism /online /cleanup-image /analyzecomponentstore and it came up with 2 packages in need of clean-up. It's taking FOREVER to run the cleanup, even though the update took virtually no time at all. Sigh.
    --Ed--
    I have not tried it yet, but would like to know if you come up with that infamous error 6824:

    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-error-6824-still-persistent-after-kb4471332.png

    That is an old screenshot.
      My Computers


  8. Posts : 125
    Windows 10 Home 64 bit
       #47

    2 tries to update to .503 for me as well.
      My Computer


  9. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #48

    Same happened to me.
    First time, it asked for Restart.
    I did and ran a winver. Still on 475.
    So ran the Update again. Now I have 503.
    View Update History shows a (2) at the end of the update...….
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-view-update-history.jpg
      My Computer


  10. Posts : 981
    W10 Pro v21H2
       #49

    Only one try needed here - I always go get standalone installers and do them starting with the Servicing Stack update. One thing I am curious about - the KB article for KB4499405 for .NET Framework 3.5, 4.7.2, and 4.8 gives links to two more KB numbers, 4495590 for versions 3.5 and 4.7.2, and 4495618 for versions 3.5 and 4.8.

    When I went to the MUC to get the standalone for 4499405, it gives links for two downloads, 4495590 and 4495618.

    I just installed the 4495590 update, and subsequent Check for updates found none needed, and update history shows 4495590 installed. But I see from others' screenshots their update histories show 4499405 installed. It looks like WU installs the overall KB number, but I assumed (yeah, I know...) one or the other sub-update would be used depending on whether 4.7.2 or 4.8 was installed.

    Does anyone understand why this .NET update is structured this way?
      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 16:37.
Find Us




Windows 10 Forums