VANGUARD ERRORS VALORANT

[mzotovka-a11y]

First of all, I’d like to express my gratitude for creating Atlas OS, since I’ve been using it for a long time and really like it. It delivers the best performance among custom builds. However, I recently built myself a new PC (R7 7800X3D, 5060, 32 GB DDR5 RAM) and decided to install Atlas OS on it. The system booted up perfectly, BUT I started experiencing constant crashes in Valorant with anti-cheat errors (VGN-102, VGN-5, VGN-185). After spending many hours trying to solve this problem, I decided to install the standard Windows 11 LTSC build. I installed Valorant and didn’t experience any issues with the game, but I’d still like to continue using Atlas OS because the standard build has FPS drops (from 500 to 370–380), and this is quite noticeable. If you can help me solve this problem in any way, I’d be incredibly grateful. I’ve also noticed that the VGN process changes its startup status on its own, even when I’ve manually changed it via services.msc. I’ve also noticed that Riot Vanguard closes on its own and the process doesn’t restart when I launch the game. The problem isn't with kernel isolation or VBS; the problem is specifically that the VANGUARD anti-cheat process stops on its own for some reason. TPM, Secure Boot, and so on—all of these are enabled. If you can help me solve this problem, I’d really be very grateful to you!

В первую очередь, я бы хотел выразить благодарность за создание Atlas OS, поскольку уже давно использую ее и она мне очень нравится. Она показывает наилучшие результаты среди кастомных сборок. Но, недавно я собрал себе новый ПК (r7 7800x3d, 5060, 32 gm ram ddr5) и решил установить Atlas OS на свой новый ПК. Система встала прекрасно, НО у меня появились постоянные вылеты из valorant с ошибкой античита (VGN-102, VGN-5, VGN-185). После долгих часов решения данной проблемы, я решил поставить стандартную сборку windows 11 ltsc, установил валорант и не испытал никаких проблем с игрой, но все же я бы хотел продолжить пользоваться Atlas OS, потому что на стандартной сборке имеются проблемы с просадками фпс (500 -> 370-380) и это достаточно ощутимо. Если вы как-то поможете мне с решением данной проблемы, я буду безумно вам благодарен. Также я заметил, что процесс VGN самостоятельно изменяет свой статус запуска, даже если я менял его собственноручно через services.msc. Также я заметил, что Riot Vanguard самостоятельно закрывается и процесс не стартует заново при запуске игры. Проблема заключается не в изоляции ядра и не в VBS, проблема именно с тем, что процесс античита VANGUARD самостоятельно останавливается по каким-то причинам. TPM, Secure boot и так далее все это включено. Если вы поможете решить данную проблему, я правда буду очень сильно благодарен вам!

[yhay81]

Your stock-Windows test is a good A/B result: it makes the new hardware, TPM, and Secure Boot much less likely causes. I would treat this as an Atlas configuration/version compatibility issue until proven otherwise, not keep forcing vgc in Services.

First check the exact installation with winver. Current Atlas supports Windows 11 25H2 and explicitly excludes Enterprise LTSC; the current support page says LTSC is not tested/supported (Atlas Windows support matrix). If Atlas was applied to LTSC, an older Windows build, or upgraded in place, the reliable fix is a clean supported Windows 11 Pro/Enterprise 25H2 installation followed by the latest Atlas playbook. Atlas also documents that upgrading the underlying Windows version in place is unsupported because its system changes are build-specific (upgrade guidance).

If you are already on a clean, supported Atlas v0.5/Windows 11 25H2 install, I would do this controlled reset:

1. Run as administrator:

   C:/Windows/AtlasDesktop/7. Security/Mitigations/Set Windows Default Mitigations.cmd
   C:/Windows/AtlasDesktop/9. Troubleshooting/Set services to defaults.cmd
   

   Then reboot. These are Atlas's own recovery scripts. The first restores Windows mitigation defaults (DEP, SEHOP, kernel mitigation settings, etc.) (script source); the second restores disabled/configured services from the backups created by Atlas (script source). Current Vanguard versions require Windows security mitigations, so this is more relevant than VBS alone.

2. Uninstall Riot Vanguard from Installed apps, reboot, start VALORANT so Vanguard is installed again, and reboot once more. Do not manually force vgc/vgk startup values between those steps; Vanguard owns both a user-mode service and a boot-time kernel driver, and changing one service does not repair the pair.

3. After the reboot, collect state before launching the game:

   sc.exe query vgc
   sc.exe query vgk
   sc.exe qc vgc
   Get-WinEvent -FilterHashtable @{LogName='System'; Id=7000,7001,7031,7034} -MaxEvents 40 |
     Format-List TimeCreated,Id,ProviderName,Message

   If vgk is missing or the System log names the exact dependency/termination reason, that is much more useful than the startup type changing in services.msc.

I would not disable TPM, Secure Boot, Exploit Protection, or additional mitigations to make the anti-cheat start. Riot's current guidance explicitly requires supported Windows security state, and their support form asks for a Riot Repair Tool archive for Vanguard failures. If the reset above still reproduces only on Atlas, attach the RRT archive to Riot Support and post here the Atlas version, base Windows edition/build, and the relevant Service Control Manager event text (not the whole archive or private identifiers).

So the fastest discriminator is:

• unsupported/old/LTSC Atlas base → clean install a supported 25H2 edition;
• supported current Atlas → restore Atlas's default mitigations and services, then perform a clean Vanguard reinstall;
• still Atlas-only afterward → preserve the service event/RRT evidence and treat it as an Atlas compatibility regression.

That sequence avoids anti-cheat bypasses and should tell us whether this is a stale Atlas tweak, an unsupported base image, or a reproducible current-playbook bug.

[mzotovka-a11y]

Good afternoon,
Last night, using AtlasToolBox, I enabled the default setting for “Mitigations,” and it seems the anti-cheat system hasn't been reporting any errors since then. AtlasOS was installed on the latest version of Windows 11, 25H2. I'll be actively testing how the game behaves this weekend.