Installation failed or the app does not open

Identify where it stopped

A failed download, corrupt archive, missing dependency, refused license and crashed application have different fixes. Note the last successful step and the first error. Keep the app name, ZIP filename, installed version and operating system together.

Work through the checks

1. Confirm you selected the correct application. Compare the ZIP name with the app card. Wait for the complete download and extract it with your normal archive tool.
2. If extraction fails, download a fresh copy. Do not repair the ZIP by removing files or nesting another ZIP around it.
3. If dependency setup fails, open Installation details in Workstation or preserve the terminal output. Check free space and network access. Use that app's Linux or Mac guide for its prerequisites.
4. If a local web address refuses the connection, make sure the application launcher/controller is running. Opening an HTML file or bookmarked localhost address alone does not start its controller.
5. If access is denied, verify account, subscription and event/course permissions. Reinstalling does not grant access.
6. If it starts then crashes, collect a crash report or Workstation diagnostics. A blank window is not enough to identify the cause.

Retry carefully

Close failed instances normally and retry the failed step once after correcting the cause. Repeatedly starting copies can create port conflicts or duplicate browser windows. Avoid deleting settings or force-killing OBS while an output could still be active.

Include useful evidence

Copy the exact message and state whether the application never opened, opened a blank page or crashed after selecting a device. Redact passwords, stream keys and pairing tokens before sharing logs.