Windows: Explorer 'Quick Access' polluted with deleted folders inside `.rustup`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Verification
- I searched for recent similar issues at https://github.com/rust-lang/rustup/issues?q=is%3Aissue+is%3Aopen%2Cclosed and found no duplicates.
- I am on the latest version of Rustup according to https://github.com/rust-lang/rustup/tags and am still able to reproduce my issue.
Problem
I don't know what exactly caused this but a few weeks back my explorer's 'Quick Access' got polluted with these temp dirs inside the .rustup folder.
All of these directories cannot be removed through Windows Explorer directly, simply because they don't exist anymore.
One way to get rid of them is by running del /f /s /q /a "%AppData%\Microsoft\Windows\Recent\AutomaticDestinations\f01b4d95cf55d32a.automaticDestinations-ms" to reset Quick Access.
Before this happend, I've extracted ~300K archives using the zip crate earlier that day and called fs::remove_file(path).unwrap() on files inside the newly created directory.
Steps
Unclear
Possible Solution(s)
No response
Notes
The code involved was straight forward and only involved calling standard APIs or zip/image crate functions.
I'm not sure what exactly caused this issue, may or may not be related to rustup.
Rustup version
rustup 1.27.0 (bbb9276d2 2024-03-08)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.79.0-nightly (3a36386dc 2024-04-25)`
Installed toolchains
Default host: x86_64-pc-windows-msvc
rustup home: C:\Users\root\.rustup
installed toolchains
--------------------
stable-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc (default)
active toolchain
----------------
nightly-x86_64-pc-windows-msvc (default)
rustc 1.79.0-nightly (3a36386dc 2024-04-25)
OS version
Windows 11, Version 23H2 (OS Build 22631.3527)
Contributor 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.
Research direction
No rustup source file, test, or reproducible steps are identified; start by determining whether rustup can create or remove the reported .rustup directories on Windows. Reproduce the Quick Access entries and establish whether the behavior is caused by rustup before defining a code change or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100