Yes. Problem was at x64 only. There is new version available with 32-bit Win systems support.
Tnx but nothing changes: I've tested before the 64bit build on a 64bit virtual WinXP, and now this new one gives the exact problem on my real WinXP 32bit. I'm quite sure it's the new v2017.3 dll.