Fix Orbx Central downloads stuck on queued or installing: clear blocked jobs, check both drives and retry without deleting your scenery.
To fix Orbx Central stuck on queued or installing, first cancel or complete the job ahead of it, then close the simulator and restart Central. Check free space on both the temporary staging and destination drives, confirm the selected Orbx library is writable, and retry one product rather than the whole queue.
This applies to Orbx Central products for Microsoft Flight Simulator, Prepar3D and X-Plane. The two statuses mean different things: Queued usually indicates a blocked or waiting job, while Installing can simply mean Central is unpacking and copying files.
Is Orbx Central really stuck?
A download rate of zero does not prove that an installation has frozen. Once a package has downloaded, Central may spend considerable time extracting files, scanning them and creating links in the simulator.
| Status and activity | Likely cause | What to do |
|---|---|---|
Queued with another job active | Central is waiting for the earlier job | Let that job finish, or cancel it using the queue controls |
Queued with nothing active | Paused, failed or stale queue entry | Remove the blocking entry and restart Central |
Installing with disk or CPU activity | The package is still unpacking or being scanned | Leave Central running |
Installing with no disk, CPU or network activity | File lock, storage, permissions or stalled process | Close Central cleanly and work through the checks below |
Use Task Manager or your operating system's activity monitor to check Central's disk activity. Do not force-close it while files are actively being written, because that can leave a partial installation behind.
How do I clear an Orbx Central queue safely?
- Inspect the first queue entry. Open Central's downloads or queue view and find the earliest paused, failed or waiting product. Resume or retry that item, or cancel it before touching later jobs. Repeatedly adding the same product only makes the queue harder to diagnose.
- Close the simulator. Exit Microsoft Flight Simulator, Prepar3D or X-Plane, along with any add-on manager or file-syncing utility accessing the destination. An open file can prevent Central from replacing or linking scenery.
- Restart Central completely. Exit it normally and quit any remaining notification-area process. If the queue returns unchanged, restart the computer to release stale helper processes and file locks.
- Check both drives. The destination library and the drive used for temporary staging must have free space. The displayed download size is not enough by itself because the compressed package and expanded files may coexist during installation.
- Test the library path. Confirm that an external disk is connected at the same mount point and, on Windows, the same drive letter. Make sure you can create and delete a small test folder inside the selected library. If the target looks wrong, check how simulator targets and Orbx libraries should be set up rather than moving product folders manually.
- Retry one product. Cancel the failed queue entry through Central, restart the application and add only that product. If Central already lists it as installed, use its
Verify Filesaction instead of creating a duplicate installation. - Check connection and security blocks. Install any Central update it offers, then test without a VPN or proxy if the log reports network or authentication failures. If antivirus or Windows Controlled Folder Access records a block, allow only Central and the selected library; do not disable protection permanently.
- Read the diagnostic log. Central's help or diagnostic area should expose its log. Look for clear indicators such as access denied, insufficient space, checksum failure, extraction failure or network timeout. That message determines the next fix.
Why does Orbx Central keep stopping on installing?
The pattern of the failure usually identifies the cause more accurately than the status label.
- One product always fails: its downloaded package may be incomplete or damaged. Cancel it and fetch a fresh copy. If the log mentions checksum, archive or extraction errors, work through the safe checks for damaged or incomplete archives. Do not manually extract files into an Orbx library.
- Every product fails: suspect the Central installation, account session, staging drive, security software or network connection rather than an individual scenery package.
- Only an external library fails: check its drive letter, mount point, sleep behaviour, permissions and available space. Avoid cloud-synchronised folders and storage that disconnects when idle.
- The failure says access denied: select a user-writable Orbx library or correct the folder permissions. Permanently running Central as administrator is not a substitute for fixing a bad destination path.
Orbx Central cannot repair a stalled simulator launcher or built-in content manager. If the Orbx job has finished but Microsoft Flight Simulator itself cannot update packages, separate simulator update failures from a Central queue problem.
Should I reinstall Orbx Central?
Reinstall Central only when every product remains stuck after a clean restart, storage check and library test. A single repeatable product failure is more likely to be a damaged download or package-specific issue.
The Central application and Orbx product libraries are normally separate, but removal options can vary. Record your library paths and do not select any option that deletes product data. We also recommend keeping the diagnostic log before reinstalling; manually deleting Central's database or random cache folders can turn a recoverable queue problem into an unrecognised library.