How to uninstall SQLiteStudio on Windows
This guide covers the official SQLiteStudio 3.4.21 x64 Windows installer. Save database changes and quit SQLiteStudio before uninstalling.
Back up settings and data first
After quitting the app, copy any data folder you want to keep to another location and check the copy. These locations were observed in this test; keep your own projects and files separate.
| Location | Contents | What to do |
|---|---|---|
%LOCALAPPDATA%\SalSoft\SQLiteStudio |
Client settings | Keep for reuse; remove only to reset |
HKCU\SOFTWARE\SalSoft\SQLiteStudio |
Client settings | Export this exact key in Registry Editor before resetting it |
Uninstall the app
Uninstall SQLiteStudio from Windows Settings, confirm the vendor prompt and close the completion message. The measured program folder was %ProgramFiles%\SQLiteStudio.
Check the result
Test-Path "$env:ProgramFiles\SQLiteStudio"
Test-Path "$env:LOCALAPPDATA\SalSoft\SQLiteStudio"
Test-Path 'HKCU:\SOFTWARE\SalSoft\SQLiteStudio'
Test-Path "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\SQLiteStudio"
Test-Path "$env:PUBLIC\Desktop\SQLiteStudio.lnk"
Test-Path returns False when that exact path is absent and True when it still exists. A data path returning True is expected if you kept your settings or data. If a query reports an error, resolve it before deciding whether the path is absent.
What Mole lists
The program folder, Start menu and public desktop shortcuts, and usage records are selected by default. %LOCALAPPDATA%\SalSoft\SQLiteStudio and HKCU\SOFTWARE\SalSoft\SQLiteStudio appear as rows listed but not selected by default. Leave these rows unchecked to keep your settings.
When you select the settings key, Mole exports it to %LOCALAPPDATA%\Mole\backups before removing it. Shared SalSoft parents and the machine sqlitestudio.pl registration are kept.
What this test covered
Tested on October 6, 2026, in a Windows 11 ARM64 VM with a Mole development build. The measured bulk uninstall selected both data rows. All five checks returned False, the native app list had no matching entry, and a successful process query found no owned process. Real databases, external uninstall and a released Mole package remain untested.