Fix Orbx Central’s “library path does not exist” error by restoring the missing drive, replacing a stale path and verifying installed products.
The Orbx Central “library path does not exist” error means Central is pointing to an Orbx Library folder or storage volume that the operating system cannot reach. Reconnect the drive or restore its old mount path; if that location has gone permanently, replace the stale library entry, choose a valid folder, and verify products.
This is a general Orbx Central problem, not an MSFS-only error. It can affect libraries used with Microsoft Flight Simulator, X-Plane, Prepar3D and FSX.
Why does Orbx Central say the library path does not exist?
The saved library location no longer matches a folder that Windows or macOS can access. The usual causes are:
- An external drive is disconnected, asleep or not mounted.
- Windows assigned the drive a different letter, or macOS mounted it under a different volume name.
- The Orbx Library folder was renamed, deleted or moved manually.
- A network share is unavailable or was mounted under another path.
- The library was copied from another computer while Central retained the old location.
- Folder permissions or security software are preventing Central from reading the path.
If the error followed a computer or storage upgrade, our guidance on moving simulator add-ons between PCs without breaking their paths covers the related drive-letter and installation-location issues.
How do I repair the missing Orbx Library path?
- Close the simulator and Orbx Central. This prevents Central from updating product records while the storage location is unavailable.
- Check the exact path shown in the error. Open its parent drive or volume through the operating system. If the drive itself is absent, reconnect, unlock or remount it before changing anything in Central.
- Restore the original drive letter or mount name when possible. This is the quickest fix when the library files are still intact. On Windows, assign the old drive letter only if it is free; on macOS, confirm that the volume is mounted under the same name. Mount network storage before launching Central.
- Open Central’s library manager. Look under
Settings > Libraries; wording may differ slightly between Central releases. If the old path is permanently unavailable, create a replacement library in an existing, writable folder. - Move through Central when the old library still works. Create the destination library first, then use the product move or migrate control provided by Central. Copying or renaming the library outside Central leaves its database pointing at the old path.
- Remove the stale library record only when necessary. If Central offers an edit or relink control, use that first. When removing a library, read the confirmation carefully and do not approve deletion of product files unless you intend to download them again. If removal is blocked because products remain assigned to it, reconnect the old location and migrate them, or clear their installation records through Central.
- Verify the affected products. Restart Central normally, select each affected product and run its file verification or repair command. This checks the installation and recreates simulator integration links where required.
For the normal destination-selection process, see our Orbx Central scenery installation walkthrough. It explains the difference between selecting a simulator and selecting an Orbx Library.
Which folder should I use for a new Orbx Library?
Use a dedicated, user-writable folder on storage that will remain available whenever Central or the simulator runs. It should have enough free space for the products you plan to install.
- Prefer an internal drive or a permanently connected external drive.
- Avoid protected system locations such as application or program directories if your account cannot write there.
- Avoid cloud-synchronised folders and intermittently mounted network shares.
- Select the library’s root folder, not an individual product folder or the simulator executable.
- Do not use the MSFS
Communityfolder as an external Orbx Library merely to suppress the error. Select it only when Central explicitly presents it as an installation target.
With MSFS, Central may keep products in an external library and create links inside Community. X-Plane, Prepar3D and FSX use different integration methods, so let Central manage the final simulator placement rather than copying product folders by hand.
Will fixing the path require another download?
You should not need to download the products again if the complete library still exists and you restore the exact drive letter, volume name and folder path. Once Central can reach that location, verify the products to repair their records and links.
If the original storage failed, the folder was deleted or you created an empty replacement at the same path, verification cannot recover files that are no longer present. Central must download the missing product data again.
What if the folder exists but Central still reports it missing?
An existing path can still be inaccessible to the account running Central. Check the following before recreating the library:
- Create and delete a small test folder inside the library to confirm read-and-write access.
- Run Central under the same normal user account that owns the folder. On Windows, an elevated application may not see network drives mapped for the non-elevated account.
- Confirm the full path and letter casing, especially for network storage and case-sensitive volumes.
- Temporarily rule out controlled-folder protection or security software blocking Central.
- Restart the computer after reconnecting or remapping storage so Central receives the updated mount information.
If Central cannot retain any valid library location, fails to open or shows unrelated connection errors, follow our broader Orbx Central troubleshooting checks rather than repeatedly deleting the library.