Diagnosing RAD Studio IDE Startup Failures from Missing or Incompatible Runtime Packages

Recognizable condition

RAD Studio IDE fails to start or crashes during splash screen with messages about a missing required runtime package or cannot find unit, typically naming a VCL or RTL bpl/dll. The IDE may open to a blank window, show a package load error dialog, or terminate immediately. The useful takeaway is that the failure is almost always a load-time resolution problem, not a corrupted project, and it can be isolated by confirming the runtime package exists in the IDE tree, is the correct release, and is not shadowed by PATH.

BPL stands for Borland Package Library, the Delphi/C++Builder runtime package format. RTL is the Run-Time Library. Both are loaded by the IDE at startup.

Cause and diagnostic pattern

Ordered checks

1. Confirm RAD Studio release and expected runtime name

Open the installer or Help > About in a working instance to note the release, e.g. RAD Studio 11. The Studio folder version, e.g. 22.0, maps to the release. Runtime packages are named with the release identifier and live under the IDE bin directory. Do not assume a specific filename; verify by listing the bin folder for the release.

2. Verify the runtime file exists in the IDE bin

Run Command Prompt as a regular user and list the bin directory. Replace XX.0 with your Studio folder.

dir \"%ProgramFiles%\\Embarcadero\\Studio\\XX.0\\bin\\vcl*.bpl\"

Expected check: files are present and timestamps match the installed release. Risk: none for read-only listing.

3. Check PATH for shadowing

Run Command Prompt and inspect PATH.

echo %PATH%

Look for entries that point to older RAD Studio installations, shared component folders, or custom bin paths placed before the current IDE bin. If a conflicting path is found, note its order. Changing system PATH requires administrator rights and can affect other applications.

4. Inspect IDE Package Manager

If the IDE opens partially, go to Tools > Options > Environment Options > Packages. The Packages page lists design-time and runtime packages with status. Missing or broken entries are flagged. This check requires the IDE to reach the options dialog; if startup fails completely, skip to check 5.

5. Launch with default environment

Use the RAD Studio-specific command prompt that sets a clean environment for the release. From Start Menu, run \"RAD Studio XX Command Prompt\". Then launch the IDE binary directly:

\"%ProgramFiles%\\Embarcadero\\Studio\\XX.0\\bin\\bds.exe\"

If the IDE starts under the clean prompt but not normally, PATH or environment variables are the cause.

Fixes tied to findings

Version mismatch or missing file in bin

If the expected runtime package is absent or has an unexpected name/date, repair the installation. Run the RAD Studio installer, choose Modify or Repair, and ensure the Delphi/C++Builder runtime components are selected. Apply the latest IDE patch from Embarcadero for the release. Do not copy a runtime package from a different RAD Studio release; version alignment is required to avoid unresolved symbols and crashes.

Corrupted package cache

Close the IDE. Back up customizations first. Clear the package cache folder, typically %APPDATA%\\Embarcadero\\Studio\\XX.0\\Cache. Deleting the cache resets IDE-customized package registrations and third-party component configurations. Restart the IDE to rebuild the cache.

Caution: clearing the cache removes stored package state; document custom package lists before clearing.

PATH conflict

If PATH points to an older runtime, restore the original system PATH or remove the conflicting entry. Prefer launching the IDE via the RAD Studio command prompt to avoid system-wide changes. Modifying system PATH requires administrator rights and can disrupt other applications sharing the same runtime versions. Back up PATH before editing.

Incomplete installation

Use the RAD Studio installer Modify/Repair option to restore missing packages. After repair, repeat check 2 to confirm files exist in the bin directory.

Third-party package interference

Disable recently added components via the Package Manager or by renaming the component package file in the IDE directory to prevent auto-load. Re-enable one at a time to isolate the offender.

Verification

Launch RAD Studio and confirm the startup error no longer appears. Open Tools > Options > Environment Options > Packages and verify runtime packages are listed without errors or warnings.

Build and run a minimal VCL or FMX application. Successful compilation and execution without package-related errors validates the fix.

Compare the installed runtime bpl/dll file version/date with the version expected for your RAD Studio release via File Properties. Matching version and date indicates correct alignment.

Escalation criteria

Contact Embarcadero Support if the error persists after repairing the installation and clearing the cache, if the error text is undocumented in the official knowledge base, or if the issue replicates across multiple workstations with identical configurations suggesting a deeper runtime compatibility problem.

Limitations: This guide addresses load-time package resolution. Issues caused by corrupted user registry settings, damaged Windows components, or hardware faults require broader diagnostics.