Question
Unable to load required components: Sourcetree upgrade failure
Mira Echo
0 reputation · 03 Jan 2025, 09:53 UTC
46.6K views1
Loading…
0 reputation · 03 Jan 2025, 09:53 UTC
A silent upgrade of Sourcetree (e.g., 4.x to 5.x) may terminate mid‑install, leaving the application directory with a mix of old and new binaries. The installer does not create a backup or expose a rollback option, and the Windows Installer transaction may not fully revert file changes. Consequently, launching Sourcetree can result in a crash with the message "Unable to load required components", and the registry may point to a non‑existent executable path.
• No official rollback mechanism is provided. • The registry does not record the previous version, making manual re‑registration difficult. • Windows 10 and Windows 11 may handle incomplete transactions differently. • User data (repositories, settings) is stored outside the installation directory, so a full reinstall risks data loss if not preserved.
1. How can we reliably detect whether the upgrade was partially applied and identify which files remain in an inconsistent state?
2. What manual steps can restore a functional installation while preserving user data, given the lack of a backup or rollback feature?
3. Is there a supported method to force a clean reinstall that automatically restores missing components without affecting user repositories?
32775 reputation · 03 Jan 2025, 13:57 UTC
If Sourcetree shows "Unable to load required components" after an upgrade, the most reliable fix is to perform a clean reinstall while preserving the user data folder (%APPDATA%\Atlassian\Sourcetree). Delete the corrupted installation directory, back up the Atlassian\Sourcetree folder, uninstall the current package, then run the latest installer.
1. Registry check: Open regedit and navigate to HKLM\Software\Atlassian\Sourcetree\InstallPath (or the HKCU equivalent). Verify the path points to an existing sourcetree.exe.
2. File comparison: Extract the latest installer to a temp folder and run a file‑by‑file checksum comparison against the installed directory. Missing or mismatched DLLs (e.g., libgit2.dll) usually cause the crash.
3. Event viewer: Look for errors under Application log that reference missing components.
sourcetreexcopy /E /I /H %APPDATA%\Atlassian\Sourcetree %APPDATA%\Atlassian\Sourcetree_backupAdd or Remove Programs.
C:\Program Files\Atlassian\Sourcetree (or the 32‑bit equivalent).%APPDATA%\Atlassian\Sourcetree if it was removed.Atlassian’s installer supports a silent reinstall that will overwrite missing components without touching the %APPDATA% folder. The sequence above is effectively that process: uninstall, clean, reinstall. It restores all required binaries and registry entries automatically.
InstallPath registry key pointing to the new executable.
%APPDATA%, so it remains untouched.
regedit and confirm InstallPath points to …\Sourcetree.exe.
sourcetree.exe from the command line; it should start without the error.
settings.json and credentials.xml in the backup folder are present after reinstall.
To tailor the recommendation further, could you confirm whether you have a recent backup of the %APPDATA%\Atlassian\Sourcetree folder? This ensures no credentials or SSH keys are lost during the clean reinstall.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.