On this page
Troubleshooting
Start with the problem you see. Each section says what the message means and what to try, and links to the page with more detail.
Pre-release documentation: this page describes Atlas for Windows as built from source in September 2026, before public release. Labels and behavior can change before release.
Atlas does not open
If Atlas closes right away without showing a window:
- Start Atlas from the Start menu or its desktop shortcut. Atlas only runs as the installed app.
- Restart your PC and try again.
- Repair the app from its Advanced options page in Windows Settings (see Find your Atlas version for where that page is), then select Repair.
- Check that your processor supports AVX2. See What you need.
- Uninstall Atlas and install it again from the official download.
If Atlas says Atlas release trust validation failed. This build cannot start., install the latest version from the official download.
Atlas cannot connect
Atlas needs to reach the Atlas service to open and to keep running. If signing in keeps failing, or protected features keep stopping:
- Check that the PC is online.
- Make sure Windows has the correct date, time and time zone.
- Allow Atlas through your firewall, and allow
api.atlascomputervision.com. - Try without a VPN or proxy. Atlas only accepts connections whose security certificate Windows trusts.
- For updates, Atlas also checks Microsoft's certificate revocation servers, so those must be reachable too.
Sign-in and activation
Sign-in messages, recovery keys and interrupted activations are covered in Sign-in problems. Before you sign in, make sure your plan is active and your Discord account is linked on your account page.
Authorization messages
When Atlas refuses an action, it shows Atlas Authorization with a message such as
Script execution blocked. Authorization denied for script.execute (lease_expired). The name before the
brackets is the feature, such as script.execute, script.editor or
remote_play.playstation. The code in brackets tells you why:
| Code | Meaning | What to do |
|---|---|---|
authorization_required | Atlas has no active authorization, for example after a required update, a failed update check, or a connection problem. | Install any required update and check Atlas cannot connect. Then sign in again with Login with Discord at the top of the window (or Activate Atlas in the Atlas Account panel). |
lease_expired | Atlas could not renew its authorization in time. | Check your connection (see Atlas cannot connect). Atlas renews on its own when it can. |
feature_unavailable | Your plan does not include this feature, or the feature is not available in this version. | Check your plan on your account page. |
authorization_changed | Your plan changed while Atlas was open. | Wait a moment for Atlas to renew, then try again. |
build_unsupported or build_mismatch | This version of Atlas is no longer allowed. | Install the latest update. See Updates. |
device_mismatch or session_mismatch | The authorization belongs to a different PC, Windows user or sign-in. | Restart Atlas and sign in again. |
lease_invalid, authorization_denied or unknown_feature | Atlas could not accept its authorization. | Restart Atlas. If it keeps happening, contact support. |
Update messages
- A required signed Atlas update must finish before Atlas can open. Finish the installation in Windows App Installer, then start Atlas again.
- Windows App Installer could not be opened. App Installer failed to start. Install or update App Installer from the Microsoft Store, then restart Atlas.
- Atlas blocked an invalid signed update package. The downloaded update changed or disappeared after Atlas verified it, so Atlas did not install it. Restart Atlas to check again.
How updates work is explained in Updates.
Video, controller and Remote Play
- Start blocked means something in the Connections card needs attention before a session can start. The rest of the message says what.
- No picture, or a capture card that isn't found: see If there is no video.
- Controller or Cronus Zen not found: see If your controller is not detected and Set up a Cronus Zen.
- Consoles not found, sign-in or registration errors, or a session that is rejected: see Remote Play problems.
- When a session ends unexpectedly, the log shows Capture stopped or Remote Play stopped with the reason.
Scripts, editor and models
- Editor unavailable. Your running session is unaffected. Install or repair the Microsoft Edge WebView2 Runtime, then restart Atlas.
- Script errors and warnings: see Script problems and Script diagnostics.
- A model that finds nothing: see If a model finds nothing.
- Atlas Library is temporarily unavailable. Check your connection, then select the refresh button (↻) in the Library.
Session logs
The session log is open below the preview in the Vision view. Select Hide logs to close it and Show logs to open it again; in a small window, Open logs shows it in its own window. Each line starts with the time it happened.
Atlas also saves the important lines (errors, stops and refusals) to a new file each time it starts. The first line
of the log, Atlas started. Log file: …, shows where that file is. Windows can keep the files of
installed apps in a private folder, so if the folder shown does not exist, look under
%LOCALAPPDATA%\Packages in the folder whose name starts with AtlasComputerVision.Atlas,
then in LocalCache\Local\Atlas\logs.
Getting help
The support page does not take requests in this preview yet; until it does, use your existing Atlas support channel. Include:
- Your Atlas version. See Find your Atlas version.
- Your Windows version, your video source and your output device.
- What you did, what you expected, and the exact message Atlas showed.
- Any support reference that starts with
ATLAS-. - The session log file from the time of the problem.