Troubleshooting
Quick fixes for common problems.
App Won’t Open
Nothing happens when I double-click XBVault.exe
Most likely: A pre-flight check detected corruption or a fatal error occurred.
- Open a terminal (Command Prompt / PowerShell) in the app folder
- Run
XBVault.exe --checkto see the health report - Run
XBVault.exe --reset-datato wipe settings, cache, and logs - Try launching again
Still won’t open? Download a fresh copy from the latest release.
“The application failed to start” dialog
This is a fatal boot error. The dialog tells you which exception occurred. Common causes:
- File access denied — extract the ZIP to a writable folder (not Program Files, unless run as admin)
- Missing DLL — re-extract the ZIP, make sure all files are present
- Corrupted settings — run with
--reset-datato wipe and restart
App opens but window is blank / hangs
- Wait 10-15 seconds — catalog may be loading for the first time
- Check if your firewall is blocking the app
- Run with
--consoleto see log output in real-time - Check
%APPDATA%/XBVault/logs/for error messages
macOS: “Unable to load shared library ‘libAvaloniaNative’” or “code signature not valid”
This is a macOS Gatekeeper issue. When you download the ZIP, macOS marks all files with a quarantine attribute. The Avalonia native library (libAvaloniaNative.dylib) is then blocked from loading.
Fix — run this in Terminal:
xattr -cr /path/to/xbvault
Replace /path/to/xbvault with the actual folder path. For example, if you extracted to Desktop:
xattr -cr ~/Desktop/XBVault
Or use the included helper script:
cd /path/to/xbvault
./xbv-fix-macos.sh
You only need to do this once after extracting. If it still doesn’t work:
sudo spctl --master-disable # temporarily lower security
# launch XBVault
sudo spctl --master-enable # re-enable after
Note: The
--checkcommand works fine because it doesn’t load the UI native libraries — it only runs diagnostics.
Can’t Connect to Xbox
“Connection refused”
Your Xbox is not accepting connections.
- Is the Xbox powered on and in Dev Mode? (not retail mode)
- Is Remote Access enabled? (Dev Mode Home → Remote Access → Enable)
- Is the IP address correct? (shown on Dev Mode Home screen)
- Try pinging the Xbox:
ping <xbox-ip>— if it fails, network is the issue
“Authentication failed”
Wrong username or password.
- Default username is
DevToolsUser(unless you changed it in Dev Mode) - Password is whatever you set in Dev Mode settings
- Reset password in Dev Mode: Settings → Remote Access → Reset Credentials
- Update the credentials in XBVault Settings and test again
“Connection timed out”
Xbox is reachable but not responding to the Dev Mode API.
- Firewall — some networks block port
11443. Try a different network or check router settings. - Same network — PC and Xbox must be on the same local network
- Restart Dev Mode — on Xbox, quit Dev Mode and re-enter
- Restart Xbox — full power cycle (hold power button 10s)
Connection works but “No packages found”
- Your Xbox may have no packages installed yet — install something from the catalog first
- Try clicking Refresh in the Installed view
Install Problems
“Package manager busy”
The Xbox is already installing something. The app now retries automatically (up to 3 times) when the upload gets a 409 Conflict, so a busy manager usually resolves by itself within ~30 seconds. If it persists, wait a couple of minutes and try again.
“Dependency missing”
The custom install wizard should resolve this automatically:
- Use Custom Install instead of one-click
- Make sure all dependencies are selected in Step 3
- If a dependency fails to install, try installing it individually from the catalog
Install gets stuck at 0%
- The package may be large and the transfer hasn’t started yet
- Check the log file for errors
- Cancel and retry
- If it keeps failing, the Xbox may not have enough free space
“Failed to upload package”
- Disk space — check available space on your Xbox
- File too large — some very large packages may timeout during upload
- Network — WiFi can be slow for large packages; wired Ethernet is recommended
- Try uploading via SFTP (File Explorer) directly to verify the connection works
“Install completed but package manager reported failure”
The package manager reported a deployment error, but the app now re-checks the installed-packages API before failing, so a successful registration is reported as success even when the manager’s own error text was stale. If this error appears at all:
- Wait a moment and check if the package appears in Installed view
- Try installing again — sometimes a second attempt works
- Check Dev Mode on the Xbox for any error messages
App Crashes
Crash on startup
- Run
XBVault.exe --checkto run diagnostics - Run
XBVault.exe --reset-datato wipe corrupted data - If it still crashes, download a fresh copy
Random crashes during use
- Check
%APPDATA%/XBVault/logs/for error details - Run
XBVault.exe --checkfor a health report - Logs show the last 50 lines before the crash — include them if reporting a bug
How to report a crash
When reporting, include:
- App version (
XBVault.exe --version) - Your operating system (Windows 10, Windows 11, macOS version, etc.)
- Xbox model and OS version (shown in System Info)
- Steps that led to the crash
- The log file from
%APPDATA%/XBVault/logs/
Open an issue at: github.com/marcelofrau/xb-homebrew-vault/issues
USB / File Issues
USB drive not detected
- USB detection is Windows-only — macOS and Linux users need to specify the drive path manually
- Make sure the drive is connected before launching the app
- Try a different USB port
- The drive must be formatted as NTFS (not FAT32 or exFAT)
“Failed to grant USB permissions”
- Run XBVault as Administrator (right-click → Run as Administrator)
- The USB drive must be formatted as NTFS
- Make sure the drive letter is correct
- Some USB drives have hardware write-protection — disable it
Can’t see files in File Explorer
- The connection may be slow — wait for the file list to load
- Some Xbox directories are restricted and won’t show
- File Explorer requires an active Dev Mode connection — check your connection settings
Other Issues
Search not finding anything
- Search requires at least 3 characters — try a longer query
- Catalog may still be loading — wait for the spinner to finish
- Use the category filter to narrow results
- Press Refresh to reload the catalog
Performance is slow
- Catalog loading — first launch is slower because it downloads the full catalog
- App startup — pre-flight checks run on every startup (typically < 1 second)
- Connection — WiFi is slower than wired Ethernet for transfers
- Logging — setting log level to Debug can slow things down; use Info or Warn for normal use
“Settings file corrupted” message
This is logged at startup when the settings file is unreadable. The app auto-recovers by resetting to defaults. No action needed — unless you had custom settings, in which case you’ll need to re-enter them.
“Cache schema mismatch” message
The catalog cache format changed between versions. The app auto-clears the cache and re-fetches the catalog. No action needed.
Still Stuck?
- Run diagnostics:
XBVault.exe --checkprints a health report - Check logs: Look in
%APPDATA%/XBVault/logs/(Windows) or~/.local/share/XBVault/logs/(Linux/macOS) - Open an issue: github.com/marcelofrau/xb-homebrew-vault/issues
- Ask the community: Click the Discord icon in the app sidebar