Add package maintenance commands: autoremove, clean, cache purge and cache management and doctor.
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
This is a large feature request bundling several commands (autoremove, clean, cache management, doctor) with no implementation detail about where cache or dependency tracking lives in the codebase. Start by reading how existing commands are registered under src/AppInstallerCLICmds and how the installer cache directory is managed, then discuss scope with maintainers — this likely needs design work and maintainer buy-in before any code. Done would mean accepted command specs and then incremental implementation.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
Please add the following maintenance commands to WinGet:
- winget autoremove : Remove unused dependencies.
- winget clean: Clean temporary files and old installer data.
- winget cache: Show cache size and location.
- winget cache list: List cached installers.
- winget cache remove: Remove cache for a specific package.
- winget cache purge: Remove all cached installers.
- winget cache reset --force: Reset and rebuild the cache.
- winget doctor: Checks corrupted cache, broken package registrations, source issues, and installation problems.
Benefits:
- Saves disk space.
- Simplifies package maintenance.
- Better for power users and developers.
Proposed technical implementation details
- Track downloaded installer cache.
- Track package dependencies installed through WinGet.
- Add safe cleanup and dependency removal.
- Support --whatif for previewing changes.
- Display reclaimed disk space after cleanup.
- Support JSON output for automation.
Example:
winget autoremove --whatif winget clean --whatif winget cache purge --whatif
Add:
winget doctor
Checks:
- Corrupted cache
- Broken package registrations
- Source issues
- Installation problems
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day