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

Page 20 of 34 FirstFirst ... 10181920212230 ... LastLast

  1. Posts : 2,557
    Windows 10 pro x64-bit
       #190

    ddelo said:
    To run the script as in the command above, you must save it on your Desktop. If saved let's say in your Downloads you change the first command to
    CD $env:USERPROFILE\Downloads

    In other words either within PowerShell navigate to the folder where the scripts is saved and type .\CPU-info.ps1
    or to run it from the current location in PowerShell type:
    & <Full path to the location the script resides>\CPU-info.ps1
    Sorry, it took me a while to see your post, but I was making some tweaks in the registry to have PS in my right-click context menu. It seems that the one I had before was broken and not working anymore.

    Thanks a lot for your recommendations.
      My Computers


  2. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #191

    Seems all is in order here?:
    Code:
    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           : False
    BTIKernelImportOptimizationEnabled  : False
    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


  3. Posts : 2,450
    Windows 10 Pro x64
       #192

    IronZorg89 said:
    Sorry, it took me a while to see your post, but I was making some tweaks in the registry to have PS in my right-click context menu. It seems that the one I had before was broken and not working anymore.

    Thanks a lot for your recommendations.
    Did you finally get it to run?
      My Computer


  4. Posts : 2,557
    Windows 10 pro x64-bit
       #193

    ddelo said:
    Did you finally get it to run?
    Not yet, but I will definitely post back with a screenshot once it is done. I definitely want to see my microcode number to see if x25 has anything to do with "L1DFlushSupported: False or True"
      My Computers


  5. Posts : 2,450
    Windows 10 Pro x64
       #194

    slicendice said:
    Seems all is in order here?:
    Code:
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]For more information about the output below, please refer to https://support.microsoft.com/en-in/help/4074629[/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]Speculation control settings for CVE-2017-5715 [branch target injection][/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]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[/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]Speculation control settings for CVE-2017-5754 [rogue data cache load][/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]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][/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]Speculation control settings for CVE-2018-3639 [speculative store bypass][/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]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[/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]Speculation control settings for CVE-2018-3620 [L1 terminal fault][/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]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[/FONT]
    [FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif]
    BTIHardwarePresent                  : True
    BTIWindowsSupportPresent            : True
    BTIWindowsSupportEnabled            : True
    BTIDisabledBySystemPolicy           : False
    BTIDisabledByNoHardwareSupport      : False
    BTIKernelRetpolineEnabled           : False
    BTIKernelImportOptimizationEnabled  : False
    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
    [/FONT]

    Two observations:
    1. Retpoline enablement
    BTIKernelRetpolineEnabled : False
    BTIKernelImportOptimizationEnabled : False

    You can enable them via Registry update or wait until a future Update (unknown when) does it for you.

    2. There is a discussion whether L1DFlushSupported, should be True (mine is). Check if you have the latest available microcode revision. Check this post
      My Computer


  6. Posts : 2,450
    Windows 10 Pro x64
       #195

    IronZorg89 said:
    Not yet, but I will definitely post back with a screenshot once it is done. I definitely want to see my microcode number to see if x25 has anything to do with "L1DFlushSupported: False or True"
    Mine is the latest (0x2B) and the L1DFlushSupported is True
      My Computer


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

    ddelo said:
    Mine is the latest (0x2B) and the L1DFlushSupported is True
    Finally done and here is the screenshot with mine at 0x24 (red square). Thanks again mate!

    Cumulative Update KB4482887 Windows 10 v1809 Build 17763.348 - March 1-microcode-revision-cpu.png
      My Computers


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #197

    Also, for me there was a line break after -force so .\CPU-info.ps1 was split to a second line and therefore wouldn't run. I had to append it to the first line, then it ran okay.
    @ddelo, will try installing KB4465065 and then re-running the Powershell script.

    Many thanks again for your continued excellent support and advice.

    Edit: Turns out that was not true. It's supposed to be two separate commands, sorry for the misinformation.


      My Computers


  9. Posts : 2,450
    Windows 10 Pro x64
       #198

    Ztruker said:
    Also, for me there was a line break after -force so .\CPU-info.ps1 was split to a second line and therefore wouldn't run. I had to append it to the first line, then it ran okay.
    @ddelo, will try installing KB4465065 and then re-running the Powershell script.

    Many thanks again for your continued excellent support and advice.



    Most welcome Rich!
      My Computer


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

    Ztruker said:
    Also, for me there was a line break after -force so .\CPU-info.ps1 was split to a second line and therefore wouldn't run. I had to append it to the first line, then it ran okay.
    @ddelo, will try installing KB4465065 and then re-running the Powershell script.

    Many thanks again for your continued excellent support and advice.



    I will definitely do the same and see what gives
      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 01:30.
Find Us




Windows 10 Forums