George++
Well-Known Member
- Joined
- Oct 16, 2010
- Messages
- 3,084
- Likes
- 762
That looks like it, and I chose the large patch for what DLAD mentioned. Other things needed patching as well.Is it this one?
That looks like it, and I chose the large patch for what DLAD mentioned. Other things needed patching as well.Is it this one?
I just manually patched my system too with the 600mb cumulative one. With this kind of a bug, I wasn't going to wait on it being pushed during the week. At least now when something could have gone wrong (due to a possible av incompatibility, but nothing did) I had a whole weekend to fix things.
Though some reports (I think even a M$ one) say a software patch like this may potentially only be able to partially fix things and a bios update could be needed.
I normally don't do many such bios updates when a system is fully stable and up and running, but if one is required I'll probably have to.
Sent from my Nexus 6P with Tapatalk
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\WINDOWS\system32> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]
Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: False
Windows OS support for branch target injection mitigation is disabled by system policy: False
Windows OS support for branch target injection mitigation is disabled by absence of hardware support: 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]
Suggested actions
* Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injection mitigation.
BTIHardwarePresent : False
BTIWindowsSupportPresent : True
BTIWindowsSupportEnabled : False
BTIDisabledBySystemPolicy : False
BTIDisabledByNoHardwareSupport : True
KVAShadowRequired : True
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : True
KVAShadowPcidEnabled : True
PS C:\WINDOWS\system32>
Care to point me to the link for my Z170 M8Formula (RedFox 1 has that one too afaik). When I visit the Asus download page for win 10 x64 I get a whopping 0 downloads for the 'tools and utilities' section
Sent from my Nexus 6P with Tapatalk
My patch went fine though ASUS Ui Suite thew an error about not being able to address memory (it's now uninstalled)
Mine did the same thing.
https://www.asus.com/us/Motherboards/ROG-MAXIMUS-VIII-FORMULA/HelpDesk_Download/Care to point me to the link for my Z170 M8Formula (RedFox 1 has that one too afaik). When I visit the Asus download page for win 10 x64 I get a whopping 0
Sent from my Nexus 6P with Tapatalk
I havent seen any 2018 releases yet.ugh can't run the script. something about "running scripts disabled on this system"
edit. Fixed by setting to "remotesigned".
Result. False, true, false false, true x5. Looks like i'm still partialy vulnerable. Identical results as DLAD
@RedFox 1 already have that one. Doesn't apply to the issue at hand here. That IME was released in november, pre-meltdown & spectre. Unlikely to contain any fixes
[...]
AMD has fixed, but not yet released BIOS/UEFI/firmware updates for the general public for a security flaw affecting the AMD Secure Processor.
[...]
Looks like AMD processors have a bug of their own that is separate from all of this.
Fudzilla: AMD suffers from an "Intel like" bug