I like to know if the corrupted recycle bin issue has been fixed in Thinapp 4.6? In the last build, if the app is installed using writecopy mode, and if I try to delete a file to the recycle bin (such as from within a dialog box opened inside the thinapp'd client application), the recycle bin will return a message saying that it is corrupted and ask me if I want to "clear" it. However, the recycle bin error message will reappear each time a file is deleted. This only occurs if the package is made using writecopy mode but not merge mode.
Please answer?
Please see the ThinApp Release Notes for a list of some of the more prominent bugs resolved in ThinApp 4.6.
http://tinyurl.com/ThinAppRelNotes
-Dean F.
http://pubs.vmware.com/thinapp4/help
I don't quite understand your reply. I had already looked at the release note, and I could not find any reference to the recylce bin. Can you elaborate?
It's not fixed yet. It relates to NTFS security descriptors which are not fully supported by ThinApp yet. I apologize for any inconvenience.
Is there a current workaround for a temporary fix? The bug is very annoying. I have even tried to put a merged attribute to $RECYCLE.BIN, but this does not work at all. Otherwise, it basically makes the writecopy mode useless since any client application that has the ability to make deleion as part of its functionality will cause a corrupted operation.
