ES
EnglishEN FrançaisFR EspañolES DeutschDE Português (Brasil)PT ItalianoIT PolskiPL TürkçeTR
Prevention

Prevention

Check this before you touch requirements. Your Windows build decides how safe you are.

Why this matters

Microsoft removed trust for the old cross-signed driver program on 24H2, 25H2, and 26H1. That change is what V4nguard leans on: running any driver-based tool on those builds is closer to telling it "please flag me" than actually hiding anything.

Not our bug

This is a Microsoft / V4lorant issue, not ours

It's not a flaw in this tool. The entire market is affected, nothing driver-based is safe on 24H2/25H2/26H1 right now. The fix is your Windows build, not the loader.

Check your build first

  1. Press Win + R, type winver, press Enter.
Run box with winver typed in
  1. Read the version number in the popup, it's your build (e.g. 23H2, 24H2, 25H2).
Winver popup showing Windows build number

Where you stand

On 22H2 or 23H2? You're good. Fully supported, no known issue. Stay here.
On 24H2, 25H2, or 26H1? It works, but it's vulnerable to the driver trust issue above. We strongly advise downgrading, see Downgrade Windows.