Hi bachian,

I have encountered exactly same incident as yours, and I noticed it might be caused by recent Windows 10 update (TH2) whichinitialized some device drivers, such as Saitek Pro Flight...