Platform:

ASUS Vivobook S 15 S5507QA_Q5507QA

CPU: Qualcomm Snapdragon X Plus, Oryon, 3.42 GHz

Architecture: Windows 11 ARM64

GPU: Qualcomm Adreno X1-45

RAM: 16 GB

Storage: approximately 477 GB

Windows 11 25H2

OS Build: 26200.9550

BIOS: Insyde S5507QA.319, dated 03/04/2026

Memory Integrity / HVCI: Enabled

VRChat stable version tested: 2022.3.22.13999

VRChat Open Beta tested: 6000.0.67.56993

Qualcomm graphics driver currently installed: 31.0.152.1

Summary:

VRChat previously worked normally on this exact Snapdragon Windows-on-ARM laptop. It now consistently hangs on a white screen and becomes Not Responding when launched through Steam/Easy Anti-Cheat.

The most important distinction is that launching VRChat.exe directly works. It reaches the login screen and proceeds to the expected offline-testing-mode error because EAC is bypassed.

The failure therefore appears specifically associated with the EAC-protected launch path rather than VRChat being completely unable to run on this system.

Reproduction steps:

Launch VRChat normally through Steam.

Easy Anti-Cheat starts normally.

VRChat opens to a white window.

The window becomes Not Responding and remains that way indefinitely.

VRChat.exe remains running instead of immediately crashing.

Windows eventually records an Application Hang/Event 1002.

Expected behavior:

VRChat should complete startup and reach the normal login/menu screen when launched through Steam with Easy Anti-Cheat enabled.

Actual behavior:

VRChat reaches a white screen and becomes Not Responding during protected startup.

Important comparison:

If I launch:

C:\Program Files (x86)\Steam\steamapps\common\VRChat\VRChat.exe

directly, VRChat successfully reaches the login menu.

After attempting to log in through the direct launch, it reports that it is in offline testing mode, which is expected because this bypasses EAC.

Therefore:

Direct VRChat.exe launch:

Unity initializes

Login menu appears

No white-screen hang

No Not Responding state

Reaches expected offline-testing-mode error

Steam/EAC launch:

EAC starts

EAC kernel driver loads

VRChat starts

White screen

VRChat becomes Not Responding

Process remains alive

Does not reach the login menu

Easy Anti-Cheat observations:

During the protected hang:

EasyAntiCheat_EOS.exe:

Running

Responding: True

EasyAntiCheat_EOSSys:

Type: KERNEL_DRIVER

State: RUNNING

WIN32_EXIT_CODE: 0

SERVICE_EXIT_CODE: 0

The EAC kernel driver is therefore not simply failing to install or start.

The EAC installer was also completely reinstalled using VRChat's own EasyAntiCheat_EOS_Setup.exe with the VRChat product ID, returning exit code 0. This did not resolve the issue.

Process behavior during the hang:

Example protected-launch VRChat PID: 19420

Windows reports:

Process exists and remains alive

Responding: False

Thread count: 85

Working set: approximately 1.74 GB

Handle count: 1,267

Two threads repeatedly consume CPU while the application is frozen.

Thread 3940:

UserModeTime continued increasing while VRChat was Not Responding

Thread 4644:

UserModeTime continued increasing while VRChat was Not Responding

The process itself accumulated significant CPU time while displaying the white screen, so this does not appear to be a simple idle wait.

Windows process inspection also behaves differently once EAC protection is active.

For the protected VRChat process:

Get-Process -Id <PID> -Module

returns:

"Cannot enumerate the modules of the "VRChat" process."

with:

PermissionDenied / CouldnotEnumerateModules

WinDbg was also unable to see/attach to the protected VRChat process, even while the process was visible through PowerShell and Task Manager.

This behavior only occurred with the EAC-protected launch.

Graphics / rendering tests:

The VRChat executable can successfully initialize outside the protected launch path using multiple Unity rendering options, including:

-force-d3d11

-force-d3d12

-force-gfx-st

-job-worker-count 1

-force-d3d11 -force-single-instance

The protected launch still hangs.

The Qualcomm Adreno X1-45 driver was updated to 31.0.152.1 and the problem remained.

DxDiag reported no graphics problems and the system supports D3D11/D3D12.

This makes a basic GPU initialization failure less likely.

Windows/system troubleshooting already performed:

Steam file integrity verification

VRChat cache cleanup

VRChat/Unity registry reset

Easy Anti-Cheat repair

Complete EAC uninstall/reinstall

VRChat EAC installer reinstall

EAC factory reset

Windows Update

Qualcomm GPU driver update

ARM64 Visual C++ runtime update

Windows SFC repair

DISM health checks

Clean boot

Defender Firewall diagnostic test

Defender exclusions for VRChat and EAC

Compatibility-layer/compatibility-mode checks

Removal of an old RUNASADMIN compatibility override

Multiple complete Windows restarts

Stable VRChat testing

Open Beta testing

None of these resolved the protected-launch hang.

HVCI / Memory Integrity:

Memory Integrity/HVCI is enabled.

If HVCI is disabled, VRChat/EAC instead produces an explicit:

"Launch Error, HVCI is required to play"

Therefore HVCI cannot simply be disabled as a workaround.

Historical crash evidence:

There is also an older valid VRChat crash dump from this system:

VRChat.exe.10300.dmp

WinDbg analysis showed:

Failure.Bucket:

INVALID_POINTER_READ_c0000005_UnityPlayer.dll!Unknown

Exception:

c0000005 - access violation

The failing instruction was:

cmp byte ptr [rbx+20h],1

At the time of the crash:

rbx = 0x40

which resulted in an invalid read from approximately address 0x60.

The crash stack was overwhelmingly inside UnityPlayer.dll, including:

UnityPlayer!UnityMain+0x40368a

UnityPlayer!UnityMain+0x445ef4

UnityPlayer!UnityMain+0x441b42

UnityPlayer!UnityMain+0x439cf1

UnityPlayer!UnityMain+0x431f69

UnityPlayer!UnityMain+0x42eada

UnityPlayer!UnityMain+0x42d301

UnityPlayer!UnityMain+0x445654

UnityPlayer!UnityMain+0x445570

with VRChat.exe below the UnityPlayer stack.

UnityPlayer.dll was:

Version: 2022.3.22.13999

ProductVersion: 2022.3.22f2-DWR

This suggests that at least one failure observed on this system reaches an invalid-pointer access inside UnityPlayer.

Current log behavior:

Fresh protected-launch output logs initialize Steam successfully and identify AppID 438100, then stop very early during startup.

The log reaches entries such as:

"[SteamManager] Initializing Steam API for AppID"

"initialized Steam connection - AppID: 438100"

"Using server environment: Release"

"VR Disabled"

"Found 143 time zones, default: 'Eastern Standard Time'"

After that, normal startup does not proceed and the application becomes Not Responding.

System context:

This is a Snapdragon X Plus Windows-on-ARM64 machine, not an Intel/AMD x64 Windows machine.

VRChat has previously been able to run on this exact machine, so this is not a case where the hardware has never been capable of running VRChat.

There are also other VRChat Windows-on-ARM reports describing white-screen/Not Responding behavior on Snapdragon systems.

One current VRChat report describes the same key distinction I am seeing:

Steam/EAC launch → white screen and Not Responding

Direct vrchat.exe launch → launches, but bypasses EAC and enters offline mode.

Another Windows-on-ARM report describes VRChat getting stuck Not Responding on a white window on Snapdragon X hardware.

My issue appears highly consistent with this class of Windows-on-ARM/EAC-protected startup problem.

What I am asking VRChat to investigate:

Please investigate whether there is currently a regression or compatibility problem involving:

Windows 11 ARM64

Snapdragon X Plus/X Elite

ARM64/ARM64EC execution

Easy Anti-Cheat/EOS protected VRChat launch

UnityPlayer

EAC process protection

Unity startup/thread suspension/protection behavior

The strongest reproduction distinction is:

VRChat.exe directly:

WORKS

Steam/EAC protected VRChat:

WHITE SCREEN + NOT RESPONDING

The machine is otherwise capable of running VRChat and Unity rendering successfully.

I would appreciate confirmation whether this is a known Windows-on-ARM/EAC issue and whether there is a current workaround or upcoming fix for Snapdragon systems.

I can provide the full diagnostic ZIP, VRChat output logs, crash dump, DxDiag information, driver inventory, and Windows event logs if needed.

When launching from Steam, it displays a white screen and becomes unresponsive.　Checking file integrity, uninstalling and reinstalling (which had worked previously), and restarting the PC were all ineffective. I was able to launch directly from the folder, but since it bypassed EAC, it resulted in an offline state. In fact, it might be more accurate to assume that the application simply fails to launch when EAC is involved. I have attached the logs from both the successful launch (bypassing EAC) and the failed launch (using EAC).

When VRChat is launched, it gets stuck on a white screen and on "Not Responding".

It used to also do that, but after a few tries, it would launch. Now it doesn't launch at all, Live or Open-Beta.

Launching the .exe (aka offline mode, without EAC) launches without issues, but that's pointless.

Logs are quite empty and don't show anything useful, still included one regardless.

Surface Pro 11th Edition, Snapdragon X Elite.