How to uninstall Git LFS on Windows
Finish Git transfers and keep a backup of repositories and large files before removing Git LFS. This guide covers the standalone GitHub.GitLFS package, installed machine-wide. Git for Windows also includes Git LFS, so a second executable may remain after removing this package.
Uninstall the standalone package
Close terminals running a Git transfer. Go to Settings › Apps › Installed apps › Git LFS › Uninstall, or run:
winget uninstall --id GitHub.GitLFS --exact
This invokes the package's Inno Setup uninstaller. Do not remove Git for Windows just to remove a separately installed Git LFS copy.
Keep repositories and configuration
| Location | What to do |
|---|---|
%ProgramFiles%\Git LFS |
Let the standalone uninstaller remove its binaries |
.git\lfs inside each repository |
Keep local LFS objects, including files not yet uploaded |
.gitattributes and repository hooks |
Keep the repository's tracking and transfer configuration |
| Git for Windows installation | Keep its own binaries and bundled Git LFS |
The git lfs uninstall command removes filters and hooks; it is not the Windows package uninstaller. Changing those settings can disrupt repositories that still use LFS. Removing the local package does not delete remote objects or end remote storage billing.
Check which copy remains
Open a new PowerShell window after uninstalling, then run:
winget list --id GitHub.GitLFS --exact
Test-Path "$env:ProgramFiles\Git LFS"
Get-Command git-lfs.exe -All -ErrorAction SilentlyContinue | Select-Object Source
git --version
No winget match means the standalone record is gone. False means its program directory is absent; True means it still needs inspection. Get-Command reports executables available on PATH, including a bundled copy; no matching output from a confirmed successful query means none was found there. git --version confirms Git still starts, not that LFS transfers work. An error is an unresolved check.
What Mole lists
The standalone program folder and its usage records are selected by default. Repository files, local LFS objects, Git for Windows and PATH entries are not removed with this package. Mole's registry cleanup backs up registrations before removing them.
What this test covered
Tested on October 3, 2026 with Git LFS 3.8.0, machine-wide winget installation on an ARM64 VM. The Inno uninstaller removed the standalone program; Git for Windows remained usable and a machine PATH entry was kept. A separate vendor-only uninstall was also checked immediately and after ten minutes. Real LFS uploads, repository hooks, remote storage and cross-version upgrades were not tested.