As I write in my original post, I experience this problem only with 32-Bit-Win10Pro. Another VM with 64-Bit-Win10Pro doesn't show this issue.
