Looks like the issue was due to a rare error occurring in the windows application. I believe I now have this fixed. Keeping my figures crossed.

More...