Spectre v2

Settings›Security›Microcode and CPU mitigations›Spectre v2

Recommendation

Depends on the situation

Keep the mitigation enabled.

Disabling is acceptable only on an isolated lab system for a controlled A/B test, without sensitive data and untrusted code.

BoosterX card

One option per system

Cost of disabling

Weakening of CPU protection

FPS and memory

See the research

What changes

Spectre v2 is a class of attacks via speculative execution (branch target injection). The mitigation closes this class at the level of the processor and Windows. The BoosterX setting controls the mitigation: the “Spectre v2” card either enables the protection or disables it. Disabling removes protection against speculative execution attacks and is acceptable only as a deliberate compromise.

Exceptions and differences

BoosterX shows exactly one option — enabling or disabling the mitigation — that suits the current state of the system; the second option is hidden, and you cannot see both at the same time. According to the app’s visible hints: on modern CPUs (Tiger Lake, Alder Lake, Raptor Lake and Ryzen 5000/7000), disabling lowers FPS, and BoosterX recommends keeping the mitigation enabled; on older Core (2010–2017), the app allows disabling for the sake of FPS if you confirm it with your own tests. After Windows or BIOS updates, BoosterX may again recommend enabling the mitigation.

When changing it, the app shows a warning about reduced protection; its warning about EAC and FaceIt anti-cheats applies to the VBS pages, not to Spectre v2.

How to verify the result

After the change, check the position of the toggle in BoosterX: the option shown corresponds to the current state of the mitigation. Check the performance impact with a separate A/B test in your game — the result depends on the processor, microcode and Windows.

How to change and revert

In BoosterX, open “Optimization” → “Security” → “Microcode and CPU mitigations” → “Spectre v2” and move the toggle to the “Enabled” position: BoosterX will apply the state recommended for your system — on modern CPUs this is the enabled mitigation (the default Windows state), on older Core it is disabling it for the sake of FPS. The “Disabled” position works in mirror fashion: on modern CPUs it disables the mitigation, on older ones it returns the default state. Click “Apply” at the bottom of the page; with “Instant apply” enabled, the change is made immediately. A separate reboot is not mentioned in the setting description.

Confirmation

• Research on BoosterX security settings: it is confirmed that disabling weakens protection.
• Microsoft: Windows guidance for speculative execution vulnerabilities

Last checked: 2026-09-19.