Upgrade failure: missing backup folder during Dyalog APL rollback

Goal

To restore a Dyalog APL system to a fully operational state after an interrupted upgrade, ensuring that user workspaces, functions, and configuration files remain intact.

Constraints & Uncertainty

The documented rollback feature restores the previous installation files only if a full backup of the installation directory and user registry entries has been created beforehand. When this backup is absent, the system may remain in a partially upgraded state, leaving configuration files corrupted. It is unclear whether the installer automatically backs up all user‑defined functions and workspaces before proceeding, as the current documentation suggests this responsibility lies with the user.

Questions

• Does the Dyalog APL installer automatically create a backup of user workspaces and functions before initiating an upgrade?
• In the event of a rollback, are third‑party modules and extensions restored to their pre‑upgrade state, or must they be handled manually?
• What configuration options or command‑line switches can enforce a comprehensive backup prior to an upgrade?