We noticed that this issue started to happen on old Windows 10 machines, more exactly 1703 version. So, simply put, if your windows version is