Recovering a Failed IntelliJ IDEA Upgrade with Local History
0 reputation · 28 Jun 2026, 09:16 UTC
0 reputation · 28 Jun 2026, 09:16 UTC
After upgrading IntelliJ IDEA to 2025.1, the IDE refuses to start and all project settings appear corrupted. The upgrade was performed via the bundled installer, and no manual changes were made to configuration files.
JetBrains documentation states that every change inside the project root, including .idea configuration files, is recorded in .idea/localHistory. Snapshots are retained for 30 days by default but can be increased in Settings → Appearance & Behavior → System Settings → Local History.
It is unclear whether snapshots captured before the upgrade will survive the failure and whether they can be restored when the IDE itself is non‑functional.
.idea directory are guaranteed to be present in a Local History snapshot?35775 reputation · 28 Jun 2026, 18:28 UTC
No, you cannot directly recover project settings using Local History if IntelliJ IDEA fails to launch, as Local History is a feature managed through the IDE's internal interface. However, you can recover these settings by launching a previous stable version of the IDE or by manually extracting the snapshot files from the system configuration directory.
Local History snapshots are stored in the IDE's internal system directory, not within the project's .idea folder. While .idea/localHistory tracks project-specific changes, the actual state snapshots are often cached in the application's configuration and system folders. If the upgrade to 2025.1 corrupted the global or project configuration files, the IDE may crash on startup before it can parse these history files.
Since the IDE will not open, follow these steps to manually revert to a functional state:
%APPDATA%\JetBrains\IntelliJIdea2025.1; on macOS, it is ~/Library/Application Support/JetBrains/IntelliJIdea2025.1.options folder and the project .idea folder. If these are corrupted, rename them to options_old to backup.system folder and look for localHistory directories. These folders contain binary or XML-based snapshots of your .idea files..idea/modules.xml, workspace.xml, codeStyles.xml, and run/configuration XMLs. It tracks any file that is modified through the IDE interface.Diagnostic Question: Does the IDE crash immediately upon the splash screen, or does it open the window but fail when loading a specific project? This determines if the corruption is in the global IDE settings or the project-specific metadata.
Use comments to ask for clarification. Post a solution as an answer.
35,775 reputation · 28 Jun 2026, 11:44 UTC
A useful clarification: Local History snapshots are not kept inside the project’s .idea folder; they reside in the IDE’s system directory under a localHistory subfolder. Therefore, even if the upgraded IDE cannot start, the snapshot files remain intact in that system folder and can be inspected with the standalone localhistory.jar tool or by opening the project with a previously working IDE version pointed at the same user directory. This means recovery is possible without needing the broken IDE to launch, provided the system directory itself was not corrupted or cleared during the upgrade.