After Windows 10’s last few updates, I encountered some strange behavior on my Flight Instrument Panels (FIPs). They are connected via two USB hubs on my networked Surface Pro as described in Post 581. I normally turn them ON after the flight simulator is loaded on the main PC.
But after recent updates, a few FIPs (not the same every time) won’t turn on at all sometimes. I’ll need to cold boot the Surface Pro in order to have them back to work normally. This happens about once or twice in every 10 start ups.
The FIPs were checked; hubs – checked; power – checked. I even swapped the ports and the hubs. Nothing unusual found. Besides a little disruption, nothing really hurts either.
After some tests, now I use my FIP_Driver_Toggler to turn off the FIP driver 
before I switch off the Surface Pro every time. Then I turn on the FIP driver again using the same utility after the Surface Pro is switched on. The problem seems gone under such arrangement.
If your FIPs, whether networked or not, are having similar issues, you may try to see if the approach helps.
FS Times 
I will give it a shot. Thanks. So what i get is the first launch SpadNext my bottom left FIP does not come on, power cycle the FIP, close SpadNext and go again, the second time my top left and right FIP’s are corrupted, power cycle those two launch SpadNext and until I reboot the system everything is fine. I mean like days on end fine. So, turning them off and back on again just prior to reboot might just be the trick..
Thanks again for the tip.
Tom
LikeLike
Hope it works. Stay Safe,
Tom
LikeLike
Hey Tom, like the concept of this, but I am using SpadNext and don’t use the generic FIP drivers is there a way to adapt this or am I doing something wrong?
Regards,
Tom
LikeLike
You are having similar issue with SpadNext? If your hubs have power switches, try turning them on right before you start SpadNext and turning them off after your flight sessions. That’s what I do.
Hope it helps to you.
Tom
LikeLike