How to uninstall Shotcut on Windows

This guide covers the official Shotcut 26.9.27 ARM64 Inno Windows installer. Exit Shotcut before uninstalling. The vendor registration displayed YY.MM.DD; the installer version was fixed by its official manifest and matching SHA-256.

Back up settings and data first

Copy %LOCALAPPDATA%\Meltytech\Shotcut after quitting if you want to keep settings. Keep your saved projects, source clips and exported videos in their own locations.

Uninstall the app

Uninstall Shotcut from Windows Settings. The measured program folder was %ProgramFiles%\Shotcut.

Check the result

Test-Path "$env:ProgramFiles\Shotcut"
Test-Path "$env:LOCALAPPDATA\Meltytech\Shotcut"
Test-Path "$env:LOCALAPPDATA\Meltytech\Shotcut\Cache"
Test-Path "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\Shotcut.lnk"
Test-Path 'HKCU:\SOFTWARE\Meltytech\Shotcut'

All five checks returned False in this batch. Keeping a settings row unchecked can leave its path present. A query error does not prove absence.

What Mole lists

The application, cache, Start Menu shortcut and usage records are selected by default. The whole Shotcut settings folder and HKCU\SOFTWARE\Meltytech\Shotcut are unchecked Review rows.

What this test covered

Tested on October 6, 2026, in a Windows 11 ARM64 VM with a Mole development build. This batch selected both ordinary settings Review rows. Six outcomes were three Removed and three Missing. The cache child was already absent after its parent was removed. The exact registration, all five unique review paths, native app list and successful ordinary and SYSTEM process inventories showed no owned application. The two empty Meltytech vendor parents were retained. Real video projects, settings recovery and the released Mole package were not tested.

A separate vendor uninstall left the settings. The development probe listed one owned usage-record row immediately and four owned rows at least ten minutes later, including the settings folder, cache child and settings registry key. All six measured residue entries were covered. Detection was checked without removing orphan data; the native Clean page and released package were not tested.