This content has been marked as final. Show 4 replies
This was the original post, to which there was a reply from an Intel engineer to acknowledge the issue (later in the same thread)
So.... now that half a year has gone by. I have done my due diligence on updating the Intel drivers and applying all of the Win10 updates. Yet the problem still exists.
Thumbs down to Intel.