glitch when deleting stuff

Hi Kestrel, thanks for your great work in the malware forum. Anyway, I had the same problem about a year ago when I was still using one of the generic Win7 Aero Themes graphics for the desktop. I got tired of it and replace it with a personal pic and the behavior miraculously disappeared. I haven't had any trouble with it since. I know it sounds crazy and illogical and I wouldn't have posted this suggestion unless I found at least one other instance of this "fix" working. I found one in the SevenForums board:

http://www.sevenforums.com/general-...cons-not-refreshing-deletion-windows-7-a.html

 

"Blackhole.ico" is just the name the forum poster arbitrarily used as an example, in place of whatever icon the reader is currently using. From your screencap, I see that you are using icon #55 from the icon library file C:\Windows\System32\imageres.dll, which is the default installed icon for Win7. When you double click on value (Default) in the right pane, that should pop up a small window labeled "Edit String" (see attached pic)

There you can input the path to the new icon that you want to use for the default (empty) Recycle Bin. You do the same thing with the "empty" and "full" entries by double clicking and entering the paths to the icons that you want to use for the empty and full recycle bin.

However, even if you succeed in changing these recycle bin icons to icons of your choosing, it would at most fix a problem of the recycle bin icon not automatically refreshing (becoming full) when you delete something. However, as I understand your problem it's not that the recycle bin icon fails to refresh appropriately, rather it's that your deleted desktop icons don't auto-refresh (disappear) after a delete operation (not until you refresh the desktop). In that case, the aforementioned fix would not (could not) solve your particular problem.

I'll keep looking in to it.

 

With 28,000+ posts, I don't see how you even have time to sleep
Like I said, I'll keep on it.

 

Kestrel, I was knocking around a Microsoft developers forum and came across a huge (long) thread discussing exactly the glitch you described. Lots of speculation, some tinkering with write-cache buffer flushing and the like :confused, and alas... no solutions. Here's how the thread ended:

I'll keep plugging along, but I wouldn't hold my breath for a cure to this one.