After much research and extensive testing, we have found the root cause of this former issue and determined that we inadvertently fixed this issue in previous updates.

Thanks for reporting,



More...