Troubleshooting

1. Select Start engine
   If the recovery screen offers Start engine, use it once and wait for the result.
2. Check Windows Security
   Open Protection history and look for a quarantined Zorro engine or helper.
3. Shut off and restart
   Select Shut off from the account menu, let Zorro close, then start it again.
4. Reinstall if a file is missing
   Add the install-folder exclusion described in Windows Security setup, then reinstall.

Expected result: The engine status becomes online and Attach a client is available.

Common symptoms are an engine that immediately stops, a missing-engine message, or an installation that succeeds but cannot start.

1. Add the exclusion first
   Exclude C:\Program Files\Zorro before restoring files.
2. Restore or reinstall
   Restore the detection from Windows Security or reinstall the current build from your account.
3. Restart Zorro
   Do not copy individual binaries from another machine or an old release.

• Confirm you started a client listed under Supported clients.
• Wait for the Minecraft 1.8.9 menu, not just the launcher window.
• Leave Attach a client open; discovery refreshes automatically.
• Restart both Minecraft and Zorro if the game was updated or relaunched into a new process.

Zorro can attach in the background. Focusing the Minecraft window should not be required.

Auto-attach deliberately waits until the JVM, Minecraft runtime, modules, and game window are stable. A client can look ready before those internal checks pass.

1. Wait for the menu
   Let the client finish loading and give auto-attach a short moment to re-check readiness.
2. Try one manual attach
   If the card remains available, select it once. Do not click repeatedly.
3. Clear a stuck running state
   Select Shut off, close Minecraft fully in Task Manager, then relaunch both Minecraft and Zorro.
4. Collect the failure
   Copy Diagnostics and open the log folder before restarting again.

Use Check again once after confirming your internet connection. If Zorro says an update is required, install that update; an older build may be intentionally refused. Check Account → Manage subscription when the subscription is inactive, and Account → Devices when the wrong PC is linked.

Temporary server or network failures should be retried rather than treated as a permanent sign-out. If the same reason code repeats, include it with your logs.

Forge: use Minecraft 1.8.9 and allow the complete mod list to load before attaching. A custom mod that changes core Minecraft classes can conflict with supported mappings; reproduce with a minimal mod list when possible.

Orbit: Orbit is detected as its own supported client even though it is Forge-based. Choose the Orbit-labelled process rather than treating it as generic Forge.

In Zorro, open Maintenance → Open log folder. The folder is %LOCALAPPDATA%\Zorro\logs and may contain:

• desktop — sign-in, access, updater, and app lifecycle diagnostics.
• engine — client discovery, readiness, attachment, and session lifecycle.
• dll — the attached runtime for each Minecraft process.
• bootstrap — early DLL load and unload traces.

When you can reproduce a product defect, use the authenticated bug-report form. If Zorro is showing a fault, send its technical report first and paste the resulting ZR reference into the form.