try to run scandisk or chkdsk, that should fix the problem

0

Chkdsk? Proabably not - nor is scandisk likely to correct things (although it won't hurt) The 'bin' will be recreated next boot after its removal - all should (hopefully) be well after that. Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

0

If the files are actually gone (drive was removed) then a registry cleaner should find the entries as orphan entries.

0

The registry is NOT used to keep track of files in the Bin. The only method that will work is to deltree 'recycled' folder(s) from all partitions and reboot as already posted (kinda). BUT further, Windows recycle bin will not be in a working state when you get back into windows. You'll need to then throw away a copy of file into it and then 'empty' the bin using the right click context menu choice. At this time you will be asked if you really want to delete x+1 files? x being the number of the files that were in the bin before you deleted it. Click yes and THEN you have a working, usable bin again. Chkdsk, scandisk, defrag also play no part in rebuilding the bin or in it's operation. deltree c:\recycled deltree d:\recycled deltree e:\recycled deltree f:\recycled deltree g:\recycled deltree h:\recycled deltree i:\recycled etc.

0

""BUT further, Windows recycle bin will not be in a working state when you get back into windows." I have to disagree on this point. There will be no recycle bin in evidence when you first restart, but the first deletion performed will recreate it. "At this time you will be asked if you really want to delete x+1 files? x being the number of the files that were in the bin before you deleted it. Click yes and THEN you have a working, usable bin again." I've never seen this. If there are "X+" files listed, then the registry must contain reference to these files in order for them to be "tracked/listed". I don't believe this is the case. Once the "dumping ground" (ie; Recycled sub-directory) is gone, there is no reference to "find" the files. It's a good day when you learn something

0

I've never seen this. If there are "X+" files listed, then the registry must contain reference to these files in order for them to be "tracked/listed". Actually, all the information about the Recycle Bin is stored in a hidden database file, typically located at C:\RECYCLED\INFO (no file extension.) The registry has very little to do with the Recycle Bin at all, other than storing the name of the "Recycle Bin" shortcut on the desktop (which of course can be renamed through registry hacks.) You can actually hex edit the INFO file in pure DOS with edit /70 C:\RECYCLED\INFO and replace E:\ references with C:\ but that can get rather messy. I recommend deleting the C:\RECYCLED directory in pure DOS as others have suggested. If you're still uncertain, you can always rename the Recycled directory in DOS instead.

0

".. but the first deletion performed will recreate it." Ah, gotcha (a subtle distinction) I had something like this after a drive copy & switch operation - items could not be removed from the bin (cheated and used a 3rd party app to remove the 'bad bin') Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

0

".. but the first deletion performed will recreate it." Ah, gotcha (a subtle distinction) Actually, I think my original statement (Reply #4) was more correct. I don't see it because my autoexec.bat deletes it on every boot. So on a "normal" system setup (which mine isn't) it should be there empty when you boot. It's a good day when you learn something

0

Either way, ok Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

0

err NTFS isn't readable / mountable from a 'raw dos' boot. and this problem can easily occur on a NTFS partition. also XP doesn't support a deltree command

0

There are "dos" tools available which allow reading of NTFS partitions. Where does XP come into the picture? The poster has indicated the O/S is 98SE. It's a good day when you learn something

0

err NTFS isn't readable / mountable from a 'raw dos' boot. and this problem can easily occur on a NTFS partition. also XP doesn't support a deltree command Even though XP was never previously mentioned in this thread (or any other NT-based OS for that matter), I suppose you could get around the problem with NT's Disk Administrator, since it allows you to change drive letters on the fly. Obviously, you wouldn't want to change a critical drive letter like C:, but you could safely change the drive letter of a CD-ROM drive temporarily, fix the Recycle Bin, then change back the drive letter in Disk Administrator. Another possible fix would be to kill explorer.exe with Task Manager, then modify C:\RECYCLER\some-long-string-of-numbers-for-your-profile\INFO (assuming it's not locked down by another process) with a hex editor, save, and re-open explorer. I haven't verified either method myself, but it seems like at least one of the methods should work, in theory.

0