Slicer Cleaner — Fix Slicer Problems When Reinstalling Is Not Enough

I have read and understood all rules of the Innovation Fund Phase 2

on

I consent to my project information (username, project cover, summary, etc.) being publicly displayed for review and showcase

on

Username (for public display)

AlphaStudioDE — Damian Brokowski

Project name

Slicer Cleaner

Project URL

Project cover

Project Category

Software

Project Summary

Fix slicer problems when ordinary uninstall/reinstall is not enough.

Slicer Cleaner is a free Windows utility for reviewing and removing slicer installations, settings, caches, temporary files and old-version leftovers, with protection for recognized models, projects and backups.

I am Damian Brokowski (AlphaStudioDE), a Snapmaker U1 owner. The tool supports the workstation side of U1 printing, including recovery workflows around Snapmaker Orca.

A reinstall may preserve broken configuration or cache. Manual cleanup is difficult when application folders also contain a forgotten model or backup.

Four guided steps: Choose a slicer or residue; Review locations and file actions; Protect recognized models in a separate folder; Confirm cleanup with explicit consent.

Safeguarding defaults on. Copies are hash-verified before eligible originals leave cleanup locations. Recognition covers 262 model/project/CAD/job/backup filename tokens, including 3MF, STL and STEP/STP. Managed package removal adds Recovery staging. Opaque caches/databases may contain embedded or renamed projects still treated as disposable data; recognition is not universal content recovery.

Real test — Snapmaker Orca, Windows 11 25H2, 5 November 2026: six selected locations; 881.5 MB of proposed non-model data. Exact slicer version was not recorded. The application reported:

  • 11,563 files removed
  • 708 empty folders removed
  • 1,492 recognized model/backup files secured
  • 0 issues to review

Counts may include samples/vendor resources. Secured-file reopening and physical U1 validation remain to be documented. This run predates RC2.

Six genuine screenshots with private paths redacted: Slicer-Cleaner/docs/REAL-WORLD-TEST.md at main · AlphaStudioDE/Slicer-Cleaner · GitHub

The catalog has 73 desktop policies plus 5 informational entries, including Snapmaker Orca, OrcaSlicer, Bambu Studio, PrusaSlicer, Cura, Creality Print and named forks/aliases. Historical coverage groups: 34 recorded full vendor-test entries; 39 incompletely tested entries marked *. Results are version-specific.

RC2 and a clean export each passed 875 RAM scenarios/10,318 assertions and 15 GUI cases/2,193 assertions per isolated configuration, plus guided UI checks. RC2 fixes Cleaner appearing in its own inventory and protects its application/Recovery storage. It is unsigned; fresh native/installer lifecycle acceptance remains pending.

No account or application telemetry. Own logic runs locally; reports can contain paths. Vendor package actions may need network access.

Cash Fund support would strengthen validation, model-protection edge cases, packaging and U1 recovery documentation.

Source/build/docs: GitHub - AlphaStudioDE/Slicer-Cleaner: Fix slicer problems when normal uninstall/reinstall fails. Windows cleanup with verified model safeguards. By Damian Brokowski (AlphaStudioDE). · GitHub
Windows test release: Release Slicer Cleaner 2.6.2 RC2 — Cleaner storage protection · AlphaStudioDE/Slicer-Cleaner · GitHub

Open Source Status

Open Source

Please specify the open source license used by this project

Slicer Cleaner Attribution License 1.0 — custom MIT-derived license permitting free use, modification and redistribution, with mandatory visible original-project and author credit in distributed forks/derivatives. Not standard MIT; no OSI approval claimed. Author: Damian Brokowski (AlphaStudioDE). Slicer-Cleaner/LICENSE.txt at main · AlphaStudioDE/Slicer-Cleaner · GitHub

Cash Fund or U1 Hardware Sponsorship

Cash Fund

Originality

Original New Idea

If based on an existing project — your independent contribution

N/A — Original New Idea. New standalone project developed from scratch, with no inherited core from another cleaner/uninstaller and no version predating 28 October 2026. Own implementation combines discovery, ownership checks, review, model safeguarding, Windows package/restart handling and guided cleanup. .NET Framework and NSIS retain their own terms.

Is it a paid project?

No

Snapmaker Orca cleanup — real Windows test

Here is the documented cleanup workflow from my Windows workstation.

  • Operating system: Windows 11 25H2
  • Slicer: Snapmaker Orca; exact version not recorded
  • Test date: 5 November 2026
  • Reviewed scope: six selected locations, with 881.5 MB of proposed non-model data

The application reported 11,563 files and 708 empty folders removed, 1,492 recognized model/backup files secured, and 0 issues to review.

These are genuine application screenshots. Private local paths have been covered with opaque rectangles. The result counters and all pixels outside those rectangles are unchanged.

1. Choose the slicer

Snapmaker Orca selected from the detected applications.

This early candidate also listed Cleaner itself. That observation was retained in the evidence and led to the RC2 detection correction.

2. Review locations and file actions

The user can inspect the proposed locations and disposable files before proceeding.

3. Protect recognized models and backups

Safeguarding is enabled, and a separate destination has been selected.

4. Confirm the cleanup scope

The final summary and separate confirmation are shown before removal.

5. Follow the cleanup activity

The activity view records removal of files from the selected Snapmaker Orca installation.

6. Read the completed result

The final screen reports the cleanup and safeguard counters and provides the model-archive and activity-log locations.

The 1,492 count covers recognized model/backup files, which may include samples and vendor resources. Reopening the secured files and physical U1 validation remain to be documented.

This run predates RC2. The newer release includes the detection correction and additional protection for Cleaner’s own application and recovery storage.

Source, documentation and catalog:

Current Windows test release:

Detailed evidence notes:

Created by Damian Brokowski — AlphaStudioDE.