How to uninstall Glary Utilities on Windows

Before uninstalling Glary Utilities, decide whether you still need its Restore Center backups. Removing the program is not the same as undoing registry or cleanup changes it previously made.

Save your data and quit

Open the top-right menu and Restore Center to review retained backups while the application still works. Keep any backup needed for recovery and finish active maintenance tasks before exiting. Do not run another cleanup merely to prepare for uninstalling.

Uninstall the tested package

In Windows 11, open Settings › Apps › Installed apps, find Glary Utilities, and choose Uninstall. In Windows 10, use Settings › Apps › Apps & features. Keep the installed program folder intact until its uninstaller finishes. If this was the winget package, first confirm its exact identity:

winget list --id Glarysoft.GlaryUtilities --exact

If the successful query shows the intended installation, remove that package:

winget uninstall --id Glarysoft.GlaryUtilities --exact

This follows the package’s registered removal method; portable packages use their package-manager removal instead. An error or a missing winget match is not proof that the app is absent: check the Windows app list and the original installation method. Follow any vendor confirmation or restart request after saving other work. See Microsoft’s uninstall command documentation.

Data and components to check

The following locations or components need separate decisions. A remaining folder is not automatically disposable.

See Glary Utilities’s official documentation.

Check the outcome

winget list --id Glarysoft.GlaryUtilities --exact
Test-Path -LiteralPath "$env:ProgramData\GlarySoft\Glary Utilities"
Test-Path -LiteralPath "$env:APPDATA\GlarySoft\Glary Utilities"

A successful package query with no matching row means that package registration was not found. A matching row means it still exists; an error leaves the result unknown. For each Test-Path, True means that exact location remains and False means it was not found; an access error does not mean it was removed. Keep deliberately retained data. Check Task Manager for a process whose executable belongs to this installation, and distinguish another version or a separate companion app before acting.

What Mole lists

The test explicitly removed the app-owned directories and settings key. Empty vendor containers, shared locations and machine-wide service registrations remained outside that cleanup. Inspect data rows before selecting them; retained empty containers do not justify a broader registry deletion.

What this test covered

The machine-wide NSIS removal completed and reported a restart requirement; the test did not restart Windows. Registration was absent afterwards. An upgrade and restoring earlier system changes were not verified.

These results are from a development build of Mole. Other released builds were not individually tested.