How to uninstall Sourcetree on Windows

Removing Sourcetree does not touch your repositories: they are ordinary folders wherever you cloned them. Push anything you have not pushed yet, since the app is going away, not your work. This guide covers Sourcetree installed per-user from the Atlassian.Sourcetree winget package.

Quit Sourcetree first

Quit Sourcetree from its window, then check Task Manager (Ctrl+Shift+Esc) for any Sourcetree.exe still listed.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find Sourcetree, and choose Uninstall, or run:

winget uninstall --id Atlassian.Sourcetree

Sourcetree's own uninstaller runs quietly, but as part of removing itself it briefly starts Sourcetree once; that is expected and part of how its uninstaller works.

Where the data lives

Location	What it holds	What to do
`%LOCALAPPDATA%\SourceTree`	Sourcetree's install folder	Removed by the uninstaller
`%LOCALAPPDATA%\Atlassian\SourceTree` and `%APPDATA%\Atlassian\SourceTree`	Small per-user data folders Sourcetree also writes to	Empty in this test; safe to remove
`%LOCALAPPDATA%\Atlassian\SourceTree.exe_Url_...` and its `%APPDATA%` counterpart	.NET application settings and cache created the moment Sourcetree's own uninstaller launched it once	Safe to remove
Saved entries in Windows Credential Manager for your git remotes	Login tokens for repositories you connected	Outside this guide; remove them yourself in Credential Manager if you want

Check the result

Run these read-only commands after the uninstall finishes:

Get-Process Sourcetree -ErrorAction SilentlyContinue
winget list --id Atlassian.Sourcetree
Test-Path "$env:LOCALAPPDATA\SourceTree"
Test-Path "$env:APPDATA\Atlassian\SourceTree"

No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means a window is still open.
A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
The first Test-Path returning False means the install folder is gone; True means files remain there.
Test-Path "$env:APPDATA\Atlassian\SourceTree" returning True means this small data folder is still there; remove it yourself if you want, since it holds nothing you would need to back up.

If you installed it with winget

winget uninstall runs the same Squirrel uninstaller (Update.exe --uninstall -s) Settings › Apps uses and removes the same program files; it does not touch the Atlassian data folders on its own.

Account and subscription

Uninstalling does not sign you out of a connected Bitbucket, GitHub or other hosted account; those stay connected on the service's own side regardless of the local app.

What Mole lists

For Sourcetree installed per-user from winget:

The install folder, the Desktop shortcut and the Start Menu Atlassian folder are selected by default.
%LOCALAPPDATA%\Atlassian\SourceTree and %APPDATA%\Atlassian\SourceTree, Sourcetree's own settings, are listed but not selected.
Sourcetree's uninstaller starts the app once, which writes .exe_Url_... folders after the review was built. Mole scans again once the uninstaller finishes and shows them in a separate section of the result, not selected, with its own Move to Recycle Bin link.
Mole does not search custom project folders for repositories, and Credential Manager entries are outside its uninstall scope.

What this test covered

Tested with Sourcetree 3.4.32 installed through winget, per-user scope. Everything in the review and in the section for what the uninstaller left behind was ticked and removed in this test. Not verified: a saved Bitbucket or GitHub account, and the official installer.