Hello Everyone,
The update I can provide at this point is that our debug team has been able to reproduce this issue, and they are currently investigating what is the root cause.
I would also like to apologize for the late reply. Our resources were focused on some critical issues (e.g. BSOD, crashes), and had to put this on a lower priority for a while. However, we acknowledge that this is extremely important as well, thus the priority of this bug report has been raised, so I'm hoping news come out faster from now on.
Thank you for your patience, and as soon as I have more information I'll share it here.
Best Regards,
Ronald M.