How to uninstall FinalShell on Windows
Back up saved connections and wanted downloaded files before removing FinalShell. In the tested Windows installation, program and local data shared %LOCALAPPDATA%\finalshell, so quit the app and copy that whole folder to a separate backup before uninstalling. The vendor's configuration page documents Linux and Mac locations; this Windows path comes from the test. This guide covers the official per-user installer.
Quit and run its own uninstaller
Close remote sessions and FinalShell. In Task Manager, check finalshell.exe and any Java process whose executable path is inside the same FinalShell directory; do not end every Java process on the PC.
The tested install had no Windows Uninstall registration, so it did not appear as a normal Installed apps entry. Open the actual FinalShell installation folder and run its uninstaller.exe, keeping the folder in place until it finishes. For the tested default path:
& "$env:LOCALAPPDATA\finalshell\uninstaller.exe"
If you used another location, use that copy's uninstaller. The test did not establish a winget removal flow. Keep separately installed WinPcap or other networking components unless you have established that nothing else uses them.
Review what remains
| Location | What to do |
|---|---|
%LOCALAPPDATA%\finalshell |
Mixed program and data; keep the backup and review retained files before recycling the folder |
HKCU\SOFTWARE\finalshell |
Review this app's settings separately |
| Your downloaded files | Keep anything you need outside the app folder |
An earlier vendor-only removal left the executable and JAR after its uninstaller disappeared. A missing uninstaller therefore does not prove the remaining folder is empty or safe to remove. Keep your connection backup before recycling retained files. Removing the client does not delete remote servers, a cloud-sync account or a paid service.
Check the result
Get-Process finalshell -ErrorAction SilentlyContinue
Test-Path "$env:LOCALAPPDATA\finalshell\finalshell.exe"
Test-Path "$env:LOCALAPPDATA\finalshell\uninstaller.exe"
Test-Path 'HKCU:\SOFTWARE\finalshell'
No process output means that executable name is not running. True means the exact file or key remains; False means it does not. An absent Windows installation record was already normal for this tested copy and cannot prove removal. An error leaves the check unresolved.
What Mole lists
The behavior below describes the October 3, 2026 test build. The corresponding fixes are still being tested; this does not establish that the current download includes them. The manual uninstall steps above still apply.
Matching shortcuts and usage records are selected by default. The mixed FinalShell folder is personal data, listed but not selected and excluded from bulk selection; its exact row needs an individual choice. The user settings key is listed but not selected and backed up before removal. Java firewall rules are reported but not removed, and other Java applications are separate.
What this test covered
Retested on October 3, 2026 with the official FinalShell 4.6.5 per-user installer on an ARM64 VM. The mixed folder was explicitly included in the removal set; the program directory and shortcuts disappeared after the vendor uninstall. This does not establish UI bulk-selection behavior. No real saved connections, passwords, file transfers, cloud sync or recovery from the backup were tested.