@Izowiuz Thanks! Yes that looks like the exact same problem. But the fix committed didn't include Windows 10. The fix comments mentioned the problem didn't occur under Windows 10, but we now reproduced here on Windows 10 1607 long term support branch.