For the past day, Windows has repeatedly shown a message saying that the Recycle Bin on my E: drive is corrupted and asking whether I want to empty it. Clicking Yes only closes the dialog, and the warning returns whenever I restart the computer or delete something from E:.
I tried running `rd /s /q E:$Recycle.bin`, but Windows reported that the directory was not empty. The same command worked on my other drives. I also ran CHKDSK, which took about two and a half hours and reported many bad clusters. Windows continues to perform a disk check whenever I boot, but it doesn't seem to resolve anything. Files on E: are extremely slow to open—sometimes I have to wait a minute or two before a video will start.
A drive-health utility reports the disk as "Good," but its real-world behavior seems seriously abnormal. Is the drive failing, or is there a safe way to repair these problems?
2 Answers
The Recycle Bin is probably only a symptom. Bad clusters, very slow access, repeated CHKDSK scans, and long delays opening files are all strong signs that the drive may be failing. Stop running CHKDSK over and over and copy anything important from E: to a different physical drive as soon as possible. Avoid writing new data to E:.
A “Good” result from a health-monitoring tool doesn't guarantee that the drive is reliable, particularly when the filesystem is already reporting bad clusters. If the data is important, consider making a full image of the drive or using a professional recovery service before attempting more repairs. Once your files are safe, replace the drive instead of focusing on the Recycle Bin.
If the files are backed up and you only want to clear the Recycle Bin, you can try PowerShell with administrator privileges. For example:
`Clear-RecycleBin -DriveLetter E -Force`
You can also use `Clear-RecycleBin -Force` to clear the bins on all available drives. However, this only addresses the Recycle Bin message—it won't fix bad clusters, repeated disk checks, or severe performance problems. Make sure important data is safe before running cleanup commands.
I’ll try that only after securing the files. Thanks!
That’s disappointing, but I’ll start arranging a replacement and prioritize copying the important files first. Thanks for the warning.