So I restarted the program now, then the error always disappears. So now I will see if the error still occurs with the option "Only standard icons" set.
Give me some time to try and reproduce!

Moderators: Hacker, petermad, Stefan2, white
I will try to reproduce it and once I know how (still not much of a clue...), I will also try it with 7.56a with full icons. But... I have ran 7.56a with full icons on the same PC until a few weeks ago and I didn't have these problems. At that time I was reorganising my NAS (not cleaning, like I do now) and I moved vast amounts of data to another location (also to different network drives), also with the F2 queue. So I am pretty sure already this issue doesn't happen with 7.56a.ghisler(Author) wrote:Thanks - it would also be nice if you could try the same with TC 7.56a (with full icon display) before you clean up your NAS disk. Some people reported that it happened only with TC8, but not with TC 7.56a.
You can't be sure, it may be caused by a new shell extension of a program installed after you switched to TC8. That's why it would be great if you could check it with TC 7.56a too. I have checked all differences which may be relevant, but found nothing which could cause this behaviour...At that time I was reorganising my NAS (not cleaning, like I do now) and I moved vast amounts of data to another location (also to different network drives), also with the F2 queue. So I am pretty sure already this issue doesn't happen with 7.56a.
These two are called in the foreground each time a directory is read (to stop the background operations, and remove icons in the queue which were from the previous directory). You need to checkthe lines above them.Removing bitmaps and icons from background thread queue
Removing pending bitmap and icon notifications