Plugin compatibility state not restored after JetBrains Toolbox rollback of failed Android Studio upgrade

Context

Android Studio upgrades managed through JetBrains Toolbox provide a one-click rollback to the previous IDE version. The rollback preserves project-level settings and the Gradle wrapper, but the research indicates that disabled plugins are not automatically re-enabled after rollback, requiring manual review. There is no built-in upgrade transaction that atomically reverts all changes on failure.

Uncertainty

The exact plugin state after a Toolbox rollback remains unclear: whether plugins disabled due to incompatibility during the failed upgrade remain disabled, whether their configuration files are reverted alongside the IDE binary, and whether the "Import Settings" dialog on the subsequent launch of the rolled-back version might re-import corrupted plugin settings from the partially upgraded instance. Deleting configuration directories to force a clean state would lose custom keymaps, inspection profiles, and UI preferences unless exported beforehand.

Goal

Determine the reliable procedure to restore a fully functional plugin environment after a Toolbox rollback without losing user customizations.

What is the definitive plugin state immediately after a Toolbox rollback following a failed upgrade? Does the rollback revert plugin enable/disable flags and plugin-specific configuration files, or only the IDE binary and core settings? Can the "Import Settings" dialog be safely skipped to avoid re-importing corrupted plugin state from the failed upgrade attempt?