Cumulative Update KB4482887 Windows 10 v1809 Build 17763.348 - March 1 Win Update

Page 16 of 34 FirstFirst ... 6141516171826 ... LastLast
  1. Ztruker's Avatar
    Posts : 10,229
    Windows 10 Pro X64 1909 18363.815
       #150

    What happened to the link in the 1st post to the article that told us how to install the Powershell cmdlet and how to run it? That's not there any more. It's been replaced by the updated article with the registry zaps.
      My Computers

  2. ddelo's Avatar
    Posts : 1,820
    Windows 10 Pro x64
       #151

    Ztruker said:
    What happened to the link in the 1st post to the article that told us how to install the Powershell cmdlet and how to run it? That's not there any more. It's been replaced by the updated article with the registry zaps.
    Try this Rich
    Cumulative Update KB4482887 Windows 10 v1809 Build 17763.348 - March 1 Windows Update - Page 14 - Windows 10 Forums
      My Computer

  3. IronZorg89's Avatar
    Posts : 1,665
    Windows 10 pro x64-bit
       #152

    Ztruker said:
    I applied the registry changes and now Retpoline is active for me as well:

    Get-SpeculationControlSettings
    For more information about the output below, please refer to https://support.microsoft.com/en-in/help/4074629

    Speculation 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: True [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: False
    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 : True
    SSBDWindowsSupportPresent : True
    SSBDHardwareVulnerable : True
    SSBDHardwarePresent : False
    SSBDWindowsSupportEnabledSystemWide : False
    L1TFHardwareVulnerable : True
    L1TFWindowsSupportPresent : True
    L1TFWindowsSupportEnabled : True
    L1TFInvalidPteBit : 45
    L1DFlushSupported : False
    And get the same results:

    Speculation 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: True [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: False
    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 : True
    SSBDWindowsSupportPresent : True
    SSBDHardwareVulnerable : True
    SSBDHardwarePresent : False
    SSBDWindowsSupportEnabledSystemWide : False
    L1TFHardwareVulnerable : True
    L1TFWindowsSupportPresent : True
    L1TFWindowsSupportEnabled : True
    L1TFInvalidPteBit : 45
    L1DFlushSupported : False
      My Computers

  4. eLPuSHeR's Avatar
    Posts : 2,166
    Windows 10 Home x64
       #153

    Take a look HERE.
      My Computer


  5. Posts : 295
    Windows 10 Pro x64
       #154

    @IronZorg89 Why your L1DFlushSupported : False?
      My Computer

  6. Zardoc's Avatar
    Posts : 230
    Windows 10 Enterprise
       #155

    Latest updates rollout have installed changes in Windows mail. One being a “turn on/off the lights” button. That's all fine and dandy but the problem is if you don't want to use this new toy it reverts settings to Lights OFF every time you close the app. I'm trying to find the setting or reg key to turn it off.

    If anyone finds it, please let me know.

    Thanks.
      My Computer


  7. Posts : 4
    win8
       #156

    My PC downloaded and installed 17763.348 March 1 and it took about an hour to finish.
    I then was Welcomed to the October update
      My Computer


  8. Win7ine's Avatar
    Posts : 113
    Win10 Pro x64 / WinServer 2016 Essentials
       #157

    RDC messed up by KB4482887


    Brink said:
    New known issue added for KB4482887. See first post for more details.
    This update has messed up RDC on my machines in that I can connect no problem, but when I minimise any open connection to the taskbar, after a amount of time has passed by and I maximise any of the minimized connections, the remote desktop screen is blank, only workaround is to disconnect and reconnect again to the machine (s).
      My Computer

  9. slicendice's Avatar
    Posts : 4,514
    Windows 10 Pro x64 v2004 Build 19041.264 (Branch: Release Preview)
       #158

    Win7ine said:
    This update has messed up RDC on my machines in that I can connect no problem, but when I minimise any open connection to the taskbar, after a amount of time has passed by and I maximise any of the minimized connections, the remote desktop screen is blank, only workaround is to disconnect and reconnect again to the machine (s).
    Yep, I'm having the exact same issue
      My Computers


  10. Posts : 67
    Windows 10
       #159

    0x800f0922 failed.

    Undid all the changes which keeps taking forever. Followed all the troubleshooting, nothing works.

    Sick of having days of my life wasted away with this useless M$ ****.
      My Computer


 
Page 16 of 34 FirstFirst ... 6141516171826 ... LastLast

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 04:58.
Find Us




Windows 10 Forums