Thanks. I will look into it. But just to be clear...if you go straight to Inspection mode after launching VBAI, and open the inspection, it allows you to run the inspection without requiring it to be saved. Is that correct?
I tracked it down to the Update Custom UI step. It stores an image reference in the parameters of the step and this reference was getting a different pointer address everytime the inspection was loaded so a simple compare of the data showed there was a difference. I had already updated this for another related issue for VBAI 2015 f2 that should release in the next month or two. When it releases, use that version and just edit the Custom UI steps and OK them to correct the the dirty dot for inspections that haven't changed.
