After upgrading from v9.0.0.6 to v9.0.0.7 I get the following when deleting a large quantity (number and/or size) of files and/or directories in DO:
The Recycle Bin on C:\ is corrupt or invalid. Do you want to empty the Recycle Bin for this drive?
I tried reinstalling and the issue still occurred.
I reverted back to v9.0.0.6 and the issue went away. It looks like it is an issue with v9.0.0.7.
I am running Windows Vista Ultimate x64.
I had a separate issue with v9.0.0.7 which I reported here:
I'm having the same exact problems. Since 9.0.0.7 Directory Opus will report the recycle bin being corrupt. This doesn't require the deletion of a large amount of files, as it can be just a single file that I delete. It appears to only happen once per sessions, so once I reboot it will happen once then be fine until reboot.
I am also have the same network issues, where my network drives will show up as being disconnected when they are actually connected. I can still access the drive and all folders but I get the red X at the top of the tab.
I'm running Windows Vista Ultimate x64 and Directory Opus 9.0.0.9. I just re-installed the OS and all applications a week ago so it's not an issue with a bad OS.
Thanks.
Opus doesn't do anything with the recycle bin other than with the Windows API functions, so it's hard to see how Opus could corrupt it.
I don't think this is Opus either since I've seen exactly the same issue that both of you are describing (including the way you can "fix" it until a reboot) and it turned out to be caused by a video file which couldn't be deleted for some reason. Every time I told the OS to fix the recycle bin it still wouldn't be fixed because there was some stray file in there which couldn't be deleted. The problem continued even if I only used Explorer after rebooting and didn't even start Opus.
I eventually deleted the file and the hidden RECYCLER$ folders (where the recycle bin lives), then rebooted and told Windows to fix the recycle bin which finally fixed it for good. I can't remember how I deleted the file but try using Safe Mode and manually deleting the RECYCLER$ folders on each of your partitions. If you get an error go inside them and check the file permissions on all of the files.
A corrupt recycle bin can also be the result of messed-up permissions on either the root of the partition(s) or inside the RECYCLER$ folders and subfolders themselves. If there aren't any undeletable files stuck inside the recycle bin then it's probably permissions which are causing the problem. This thread may be of some help:
forums.techguy.org/windows-vista ... e-bin.html
I would reboot into safe mode, delete the (hidden-system) RECYCLER$ folder on all partitions, then ensure that the file permissions for the root drives is as shown below.
The easiest way to get a detailed summary of all permissions is to run [b]cacls.exe C:[/b] (or any other drive letter) in a command prompt window. This shows you all of the information at once, unlike the Properties dialog.
The permissions for C:\ will be different to those for other drives. Also, these are from Vista Ultimate; other OS may vary.
When editing the permissions, do not apply the changes to child directories else you will mess things up. If you're not familiar with editing file permissions or aren't sure what you're about to do, find someone who is. You'll need to know how to interpret the output of cacls.exe for this, obviously.
[b]cacls.exe C:[/b]
C:\ BUILTIN\Administrators:F
BUILTIN\Administrators:(OI)(CI)(IO)F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
BUILTIN\Users:(OI)(CI)R
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)C
NT AUTHORITY\Authenticated Users:(special access:)
FILE_APPEND_DATA
[b]cacls.exe D:[/b] (or any other local harddrive that isn't C:)
D:\ BUILTIN\Administrators:F
BUILTIN\Administrators:(OI)(CI)(IO)F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
NT AUTHORITY\Authenticated Users:C
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)C
BUILTIN\Users:R
BUILTIN\Users:(OI)(CI)(IO)(special access:)
GENERIC_READ
GENERIC_EXECUTE
After fixing the root-level permissions reboot into normal mode and delete something. If you're prompted about the recycle bin being corrupted tell it to fix it and it should be fixed once and for all.
Thanks for the quick feedback, I appreciate it. First let me address the two posted solutions…
Delete RECYCLER$: I have done this several times and still the issue persists.
Permissions: Here are the permissions on my drives:
C:>cacls c:
c:\ BUILTIN\Administrators:F
BUILTIN\Administrators:(OI)(CI)(IO)F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
BUILTIN\Users:(OI)(CI)R
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)C
NT AUTHORITY\Authenticated Users:(special access:)
FILE_APPEND_DATA
C:>cacls d:
d:\ BUILTIN\Administrators:F
BUILTIN\Administrators:(OI)(CI)(IO)F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
NT AUTHORITY\Authenticated Users:C
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)C
BUILTIN\Users:R
BUILTIN\Users:(OI)(CI)(IO)(special access:)
GENERIC_READ
GENERIC_EXECUTE
C:>cacls e:
e:\ BUILTIN\Administrators:F
BUILTIN\Administrators:(OI)(CI)(IO)F
NT AUTHORITY\SYSTEM:F
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
NT AUTHORITY\Authenticated Users:C
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)C
BUILTIN\Users:R
BUILTIN\Users:(OI)(CI)(IO)(special access:)
GENERIC_READ
GENERIC_EXECUTE
I have also done a complete format and re-install of Visa and the problem persists.
Let me re-iterate that this problem first occurred with Directory Opus 7.0.0.7 and did not occur with previous versions of Opus. The problem does not occur with windows explorer. When I delete a file I get two windows that pop up. The first window looks like it is generated by Opus (I could be wrong about this), which states..
“The Recycle Bin on E:\ is corrupt. Do you want to empty the Recycle Bin for this drive?”
The second window is definitely the windows default window for recycling that shows…
“Calculating time remaining…”
“Recycling 1 item”
The second window is frozen until I either click either yes or no on the first window. Whether or not I empty the recycle bin the problem goes away for a while.
I’m not trying to say that the problem is definitely with Opus but the evidence I have collected so far points in that direction. If you have any more ideas on how to proceed I would appreciate it.
Thanks.
I meant to say "Let me re-iterate that this problem first occurred with Directory Opus 9.0.0.7". Sorry for the typo.
The "corrupt recycle bin" message comes from Windows rather than Opus. It's odd that you're not seeing the same thing when using Explorer, though.
Do you ever Undo recycle-bin deletes using Opus's Undo command?
How do you empty the recycle bin? Using Opus, or via the icon on the Desktop?
You haven't used any registry cleaners or anything like that, I take it?
Can any other Vista 64-bit users reply to say whether they do or don't see the same thing? Maybe it's related to Opus currently being a 32-bit process (until a native 64-bit version is ready), but that would seem odd since Opus just calls the Windows/Shell Recycle Bin API to delete the files so it shouldn't cause a problem.
Once again thanks for the quick reply. I have never used Opus to undo recycle-bin deletes and haven't undone any deletes it several months. I always empty the recycle bin using the desktop icon and I have never used a registry cleaner in Vista.
Is there a way that I can download 9.0.0.6? If so I would be happy to move back to that version to verify if the problem started with 9.0.0.7 or if it was a coincidence. I would also be open to any other testing you feel would be prudent.
Also any ideas on the second issue I have which is Opus showing that the network drive is disconnected when its not?
Thanks.I was able to get a hold of a copy of Directory Opus 9.0.0.6 and have been running it for the last couple weeks. As expected, I have not had any problems with the corrupted recyclebin messages or my network drives showing up as disconnected.
It is evident that this issue only exists in Directory Opus 9.0.0.7 - 9.0.0.9. Hopefully theses issues can be fixed for the next version. If any additional information is needed please let me know.
If you haven't already, file a support request for the issue. If it is caused by a change from .6 to .7 then I expect only GPSoft will be able to work out what it is.
I believe this problem appeared in the v9.0.0.7-9 releases because explorer integration was enabled in x64 OSes. v9.0.0.6 did not have this option on a x64 OS so the problem did not occur.
Anyways, it appears that the newly released x64 version of Directory Opus has resolved this issue.
Thanks!