New
#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.
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.
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
@IronZorg89 Why your L1DFlushSupported : False?
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 PC downloaded and installed 17763.348 March 1 and it took about an hour to finish.
I then was Welcomed to the October update
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).
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$ ****.