How to uninstall Loom on Windows

Recordings that finished uploading live in your Loom library on the web, and removing the desktop app does not delete them. Before you uninstall, open your library on loom.com and check that your latest recordings are there; if one has not finished uploading, keep Loom installed until it appears online. This guide covers Loom 0.379.4 installed for the current user through winget.

Quit Loom

Quit Loom, then use Ctrl+Shift+Esc to check Task Manager. The test showed 15 Loom processes, including Loom.exe, loom-recorder-production.exe and loom_crashpad_handler.exe. Loom added a startup entry (the electron.app.Loom Run value, shown in Settings › Apps › Startup), which Mole removed with the app.

Uninstall Loom

Open Settings › Apps › Installed apps, select Loom and choose Uninstall; Windows 10 calls this page Apps & features. The uninstaller is NSIS, and the test ran its registered quiet command (Uninstall Loom.exe /currentuser /S).

For a winget installation:

winget uninstall --id Loom.Loom --exact

winget runs the vendor's uninstaller. It does not delete your Loom account, workspace or recordings on loom.com.

In a separate test run that used only Loom's own uninstaller, %LOCALAPPDATA%\Programs\Loom, %LOCALAPPDATA%\loom-updater, the loomDesktop registration and the electron.app.Loom startup value were still there afterward. Check them with the commands below if you removed Loom without Mole.

Locations observed in testing

Check the result

winget list --id Loom.Loom --exact
Test-Path -LiteralPath "$env:LOCALAPPDATA\Programs\Loom" -ErrorAction Stop
Test-Path -LiteralPath "$env:APPDATA\Loom" -ErrorAction Stop
Test-Path -LiteralPath "$env:LOCALAPPDATA\Loom-updater" -ErrorAction Stop
Test-Path -LiteralPath 'HKCU:\Software\Classes\loomDesktop' -ErrorAction Stop

A winget row means the package is still listed; empty output or a source error alone does not prove removal, so also check Installed apps. For each Test-Path, True means that folder or key exists, while False without an error means it does not. An access error leaves the result unknown. None of these commands checks your recordings online.

What Mole lists

With Remove data and settings with apps off, the test's rows are:

• The install folder, selected with the Application row.
• %APPDATA%\Loom, listed but not selected.
• Its seven cache, crash-report and log folders, each selected by default.
• The Loom Start Menu shortcut, selected by default.
• %LOCALAPPDATA%\Loom-updater, selected by default.
• The loomDesktop link registration, selected by default.
• The electron.app.Loom startup value, selected by default.
• Usage records for the Loom program path, selected by default.

Select all and Also remove data include %APPDATA%\Loom. The data-default preference never selects it, since it is an Electron profile. Files Mole removes go to the Recycle Bin, and registry entries are exported to a .reg backup before removal.

All 14 listed rows were selected in the test. Mole removed the install folder, the updater folder, the link registration, the startup value and the usage records; %APPDATA%\Loom with its cache folders and the shortcut were already absent after the vendor uninstaller. The test's before-and-after comparison found no other Loom location.

What this test covered

Loom 0.379.4 was installed for the current user through winget and removed on October 21, 2026, in a Windows 11 ARM64 VM using a development build of Mole. The test did not sign in or record, so uploads, recovery of failed recordings, account data and updates were not verified, and neither was the downloadable Mole package. In the separate vendor-only run above, Mole's Clean did not list those surviving items, and that gap is still open.