Skip to content
All products Downloads Release log
Everything on Nyxall
Latest release Nyxall VRCS 2026.11.03 Nov 3, 2026

Nyxall VRCS

Troubleshooting

Common issues and how to fix them

On this page

“Windows protected your PC” (SmartScreen)

Expected for now — installers are not yet code-signed. Verify the download’s SHA-256 against the published checksum, then More info → Run anyway. See Installation for the exact command.

An update failed or won’t install

  • Restart the app once — a downloaded update installs on the next start.
  • If a toast says the update could not be verified or no matching file was found, download the latest installer from the downloads page and run it manually. A manual install over the old version is always safe.

The app says my Nyxall account has no access

The app unlocks for a Nyxall account that has been approved for VRCS. Check these in order:

  • Is your request approved? Your account page shows your access. If the request is still pending, wait for approval — the app re-checks on its own.
  • Did you sign in with the same account? Access belongs to the account that requested it. Sign out of Nyxall in the app and sign in with that account.
  • No account or request yet? Follow Getting Started from step 1. No access key is needed.

Signing in also needs a working connection to Nyxall; corporate proxies or aggressive firewalls can block it. If Nyxall can’t be reached, an app that was recently confirmed keeps working offline for a while.

Login or VRChat data problems

The app links here when a VRChat sign-in keeps failing and when it finds a damaged local database.

Sign-in keeps failing, or the app reports connection errors. VRChat rate-limits repeated attempts, so trying again straight away makes it worse — wait a few minutes. Check that the same credentials work on vrchat.com, that two-factor codes are current (a clock more than a minute out will fail every code), and that a VPN, proxy or firewall is not blocking the connection. During a VRChat outage nothing will sign in until it is over.

The app misbehaves after a crash — missing history, or database errors on startup. The local database may be damaged; see Repairing the local database below. Please also report the crash through your Nyxall members channel — a database that damages itself is a bug here, not something you should have to repair twice.

Repairing the local database

VRCS keeps its history and settings in one SQLite database. Since VRCS 2026.10.06 it is VRCS.sqlite3 in %APPDATA%\VRCS: the update copied your data there once from %APPDATA%\VRCX and left the old folder as it was. Older versions use VRCX.sqlite3 in %APPDATA%\VRCX, and so does VRCS for a start on which that copy couldn’t be made. On Linux the database stays VRCX.sqlite3 in ~/.config/VRCX. The steps below are for Windows and VRCS 2026.10.06 or later; on an older version, use %APPDATA%\VRCX and VRCX.sqlite3 instead. If VRCS reports a damaged database, SQLite’s own recovery usually gets everything back:

  1. Close VRCS completely, including the tray icon.

  2. Copy the whole %APPDATA%\VRCS folder somewhere safe. Every step below works on the original folder, so this copy is your way back.

  3. Get the SQLite command-line tools from sqlite.org/download.html (“Precompiled Binaries for Windows”, the sqlite-tools package) and unzip sqlite3.exe into %APPDATA%\VRCS.

  4. Recover into a new file. Open Command Prompt (not PowerShell, which changes the text encoding of the pipe), then run:

    cd /d "%APPDATA%\VRCS"
    sqlite3 VRCS.sqlite3 ".recover" | sqlite3 VRCS-recovered.sqlite3
    sqlite3 VRCS-recovered.sqlite3 "PRAGMA integrity_check;"

    The last command should print ok.

  5. Swap the files: rename VRCS.sqlite3 to VRCS-damaged.sqlite3, then VRCS-recovered.sqlite3 to VRCS.sqlite3. Delete sqlite3.exe from the folder again.

  6. Start VRCS. If it still reports a problem, put your copy from step 2 back and report it through your Nyxall members channel with a recent log file.

Where are my logs and data?

Everything local lives in %APPDATA%\VRCS on Windows since VRCS 2026.10.06 (%APPDATA%\VRCX before that) and in ~/.config/VRCX on Linux: the SQLite database, app settings, and log files. After the 2026.10.06 update the old %APPDATA%\VRCX folder is still there, unchanged; VRCS no longer uses it. Including a recent log file with a bug report makes it much easier to help you.

Reporting a bug

Report bugs through your Nyxall members channel, with your app version (Settings → About), your OS, and what you expected vs. what happened. Attaching a recent log file from %APPDATA%\VRCS\logs (~/.config/VRCX/logs on Linux) makes it much easier to help you.