This has been reported and were hoping there’s a possibility that this can be solved with a Firmware Update. However since this issue did not seem to exist under WIN8 it could very well be that with a next WIN10 update the issue will go away … we will announce news on this when we receive it.