How to uninstall UltiMaker Cura on Windows

UltiMaker Cura keeps your printers, custom profiles, material settings and preferences in a configuration folder per Cura version, and its uninstaller leaves that folder behind. Open it from Help › Show Configuration Folder and copy it first if you might reinstall. Your project files and sliced G-code stay wherever you saved them. This guide covers UltiMaker Cura installed machine-wide from the Ultimaker.Cura winget package, which is a Windows Installer (MSI) package.

Quit Cura first

Close Cura before uninstalling. It runs UltiMaker-Cura.exe and, while slicing, CuraEngine.exe; check Task Manager (Ctrl+Shift+Esc) that neither is still listed. If Cura is still running, the uninstaller cannot remove its program folder until the next restart. Cura added no startup item in this test.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find UltiMaker Cura, and choose Uninstall, or run:

winget uninstall --id Ultimaker.Cura

The Windows Installer package asks for administrator access, since Cura was installed for all users. If it reports that a restart is needed, restart before you check the result.

Where the data lives

The paths below use Cura 5.13; each Cura version gets its own numbered folder.

Location	What it holds	What to do
`Program Files\UltiMaker Cura 5.13.0`	Program files	The uninstaller removes it, after a restart if Cura was still running
`%APPDATA%\cura\5.13`	Printers, profiles, materials, plugins and preferences	Back it up first; keep it if you plan to reinstall, the next version can import it
`%APPDATA%\cura`	The version folders plus Cura's logs and crash reports	Safe to remove once you have what you need from the version folders
`%LOCALAPPDATA%\cura\5.13`	Cache	Safe to remove
`%LOCALAPPDATA%\Ultimaker B.V\UltiMaker-Cura`	Data written by Cura's interface	Safe to remove once Cura is gone
`HKCU\Software\UltiMaker\UltiMaker Cura`	A few settings the installer and app keep	Safe to remove once Cura is gone

Check the result

Run these read-only commands after the uninstall finishes, and after a restart if one was requested:

Get-Process UltiMaker-Cura, CuraEngine -ErrorAction SilentlyContinue
winget list --id Ultimaker.Cura
Test-Path "$env:ProgramFiles\UltiMaker Cura 5.13.0"
Test-Path "$env:APPDATA\cura"
Test-Path "$env:LOCALAPPDATA\cura"
Test-Path "$env:LOCALAPPDATA\Ultimaker B.V"

No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown.
A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
The program folder returning True means files remain there; if you have not restarted since the uninstall, restart and check again.
%APPDATA%\cura returning True means your configuration is still there, which is expected unless you removed it yourself.
The last two returning True mean the cache and interface data are still there; remove them yourself if you want a clean start.

Account

Uninstalling does not sign you out of your UltiMaker account or delete backups you made with Cura's cloud backup. Manage those from your account.

What Mole lists

For UltiMaker Cura installed machine-wide from winget:

Mole recognizes Program Files\UltiMaker Cura 5.13.0 as Cura's program folder: it shows its size, asks you to quit Cura before the uninstall, and says so in the result when Windows holds files there for the next restart. Removing the folder is left to Cura's uninstaller.
The Start Menu folder is selected by default.
HKCU\Software\UltiMaker\UltiMaker Cura is listed but not selected.
%APPDATA%\cura and %LOCALAPPDATA%\cura are listed as personal data, unchecked and excluded from bulk selection. %LOCALAPPDATA%\Ultimaker B.V remains a manual check because the vendor namespace can hold other products.

What this test covered

Tested on 2026-09-28 with UltiMaker Cura 5.13.0 installed through winget, machine-wide. Cura was still running when the Windows Installer uninstaller ran, so the entry went away and the result asked for a restart, while the program folder waited for it. Every listed row was ticked in this test. Not verified: a configured printer, importing settings into a newer Cura, a UltiMaker account, or the state after the restart.

On 2026-10-04, the added residue rules were checked with controlled files in the Windows VM using the current source: exact ownership, another installed copy and source-path absence after recycling. This did not repeat the vendor uninstall or verify a released package.