Getting it on multiples machines with Win10 on v2.30.8. For now we reverted to v2.30.2 where this issue is not present.