Have a look in your %TMP% folder, is there a bugreport.txt file there? If so, please send it to support @ finalbuilder.com - hopefully that will help us identify the cause.
At this stage I haven’t been able to reproduce this issue. Are there any other details you can give about how the fileset->iterate->delete file actions were setup? Were they looking at a network share by any chance?
The old actions were looking at the B: drive which is a local drive. Our build machines are Hyper-V machines with an extra drive mounted from Nimble storage.
Still not having any luck reproducing things here. We have a local Hyper-V machine which I have been testing on, but haven’t been able to reproduce what your seeing.
Have you seen this issue on any other systems with Nimble attached storage, or other secondary storage?