"The Recycle Bin on C:\ Is Corrupted" Error on Windows
"The Recycle Bin on C:\ is corrupted. Do you want to empty the Recycle Bin for this drive?" appears when you sign in or delete a file, and Microsoft's explanation is one line: the drive's hidden $Recycle.Bin folder is damaged. Its documented fix is to delete that folder from an elevated Command Prompt and restart. Either way, answering Yes or running the fix, what was in that drive's Recycle Bin is gone, so if the Recycle Bin still opens, restore anything you need first. Only the drive named in the message is affected.
What the message means
Microsoft's support article quotes the message as "The Recycle Bin on \<Drive> is corrupted. Do you want to empty the Recycle Bin for this drive?" and gives the cause: "a corrupted $Recycle.bin file". It adds that the drive "might be a logical volume or a mounted volume", which is a reminder that every drive has its own Recycle Bin. A message about D:, or about an external disk, says nothing about the bin on C:.
Inside each drive's $Recycle.Bin, Windows keeps a subfolder per user account, named by the account's security identifier (a long S-1-5-… string). Each deleted item is a pair of files there: a small $I… record holding the original path, the size and the deletion time, and a $R… file or folder holding the content itself. When the records or the folder structure are damaged, Windows cannot read the bin for that drive and offers to empty it.
| You see | Likely cause | Try |
|---|---|---|
| The message at sign-in or when you delete a file | Damaged $Recycle.Bin on that drive |
Restore what you need, then Microsoft's fix |
| The message names an external or USB drive | That drive's own bin | The same fix with that drive letter |
| The message returns after the fix | File system errors on the drive | chkdsk with /f |
| The message appears together with read errors or a failing-drive warning | The drive itself | Back up first, then check its health |
Before you delete anything
- Open the Recycle Bin from the desktop. If it opens, restore the items you deleted from that drive and still want; they go back to their original folders.
- Remember that the fix removes the whole folder, so deleted items from every user account on this PC go with it, not only yours.
- If you want to see what is there first, list it from Command Prompt:
dir /a C:\$Recycle.Bin
Each S-1-5-… folder is one account's bin on that drive.
Microsoft's fix
Open Command Prompt as administrator and run the command from Microsoft's article, with the drive letter from the message:
rd /s /q C:\$Recycle.Bin
Then restart the PC, as the article says. For drive D:, the command is rd /s /q D:\$Recycle.Bin.
Use Command Prompt, not PowerShell. In PowerShell rd is a short name for Remove-Item, which does not take /s /q, and $Recycle is read as a variable, so the same line does something else or fails.
What the command removes: every item in that drive's Recycle Bin, for every account, permanently. The files do not move anywhere else, and there is no undo. What it keeps: everything that is not in the bin, and the Recycle Bins of other drives. If you find out later that something in it mattered, Microsoft's Windows File Recovery is a command-line app for files that can no longer be restored from the Recycle Bin, and any further use of the PC can overwrite what it would recover.
Answering Yes to the original message asks Windows to empty that drive's bin. If the message comes back after that, run the command above.
If the message comes back: check the drive
A bin that breaks again on the same drive points to file system damage underneath. Run chkdsk from an elevated Command Prompt:
chkdsk C: /f
/f "fixes errors on the disk", and the disk must be locked to do it. On the system drive chkdsk cannot lock C: while Windows runs, so it asks to check the drive at the next restart; answer Y and restart. /r adds a search for bad sectors and takes much longer. Microsoft documents the exit codes: 0 means no errors were found, 1 means errors were found and fixed. Afterwards, the results are in Event Viewer's Application log under the Chkdsk and Wininit sources.
If chkdsk keeps finding errors, or Windows warns that the drive is failing, stop fixing the bin and copy your files somewhere safe first. A drive that is dying will keep breaking folders, the Recycle Bin among them.
What not to do
- Do not run the
rdcommand against anything other than<drive>:\$Recycle.Bin. A typo in anrd /s /qline deletes without asking. - Do not answer Yes, or run the fix, before restoring what you still need, if the bin still opens.
- Do not run
chkdsk /ron an SSD again and again. Microsoft notes that repeated full-surface scans add unnecessary write and erase cycles, while an occasional check is not a concern.
Where Mole fits
Mole for Windows does not repair a corrupted Recycle Bin. It does not run rd, delete the $Recycle.Bin folder or run chkdsk. Clean's Recycle Bin section lists your own account's bin on every fixed drive item by item, read from each $I record, and only complete pairs it can parse are listed, so a damaged entry is skipped rather than fixed. The section's note says it plainly: "Everything in the Recycle Bin. It can't be recovered once emptied". Entries start unticked, and Recommended never selects them; ticking them yourself, or using the section box or Select all, does. Mole deletes each chosen pair directly, and entries that only an administrator can delete go into one administrator prompt. Only drives Windows reports as fixed are scanned, so USB flash drives are not. Doctor shows "Recycle Bin is over 5 GB. Empty it from Clean to reclaim space." when the system drive's bin passes 5 GB and the drive is not already nearly full. For space in general, see Disk Cleanup or Storage Sense and a full C: drive.
FAQ
What does "The Recycle Bin on C:\ is corrupted" mean?
The hidden $Recycle.Bin folder on drive C: is damaged, so Windows cannot read the deleted items stored there. Microsoft's fix deletes that folder and asks for a restart.
Will I lose files if I fix a corrupted Recycle Bin?
You lose what was in that drive's Recycle Bin, for every account. Files outside the bin, and the bins of other drives, are not touched. Restore what you need first if the bin still opens.
Is it safe to delete the $Recycle.Bin folder?
Microsoft's own fix does exactly that with rd /s /q <drive>:\$Recycle.Bin from an elevated Command Prompt, followed by a restart. The cost is the items in that bin.
Why does the Recycle Bin keep getting corrupted?
Repeated damage on the same drive points to file system errors. Run chkdsk with /f on that drive, and back up first if it keeps finding errors.