David, FYI, I think you are seeing the same issue as some of the rest of us as in this thread:
As far as I know, there has not yet been a resolution. I see the issue with 2.5.1.17 and 2.5.1.16. I have not yet tried falling back to 2.1.5.15, but will before my next imaging session.
- Shane