PsyBorg
Wake up! Time to fly!
The whole problem I have found with windows (specially if you are smart enough to NEVER let it do things on its own like update drivers) is if the drivers are not computer hardware drivers Windows does not play well. External hardware like flight controllers and the little programming things like arduino boards and all that Windows seems to think its own crappy generic drivers are better suited then the manufacturers drivers because a lot are not signed since Microsoft charges to do that.
When I install a new fc driver I will always do a cold start on my computer as that makes windows forget what IT thinks it should use and actually loads the new drivers properly when it is supposed to. Between Zadig and the Impulse driver fixer I am not sure why the guys working on the guis do not just embed one or the other into the gui and save all of us this freakin nightmare. You should plug the board in.. windows generic drivers will see it to talk thru the gui in most cases. Then have the gui auto execute zadig or impulse tool when DFU is typed in the CLI. Both are free to use and I am sure their devs would allow it to be part of the Guis as we normally use it anyways.
When I install a new fc driver I will always do a cold start on my computer as that makes windows forget what IT thinks it should use and actually loads the new drivers properly when it is supposed to. Between Zadig and the Impulse driver fixer I am not sure why the guys working on the guis do not just embed one or the other into the gui and save all of us this freakin nightmare. You should plug the board in.. windows generic drivers will see it to talk thru the gui in most cases. Then have the gui auto execute zadig or impulse tool when DFU is typed in the CLI. Both are free to use and I am sure their devs would allow it to be part of the Guis as we normally use it anyways.