Hay Guys/Gals....

Its been a minute since Ive been able to post, due to me waiting on parts etc..

So I finally was able to return my SB F7V3 Stack, And then purchase a new one. So once I recieved my new stack I immediately did a back up of Everything. Im not F'ing around this time, Im getting really tired of coming into all of these hurdles and obstacles.... 

So that being said, And Ill do my best to get right to the point and not waste anyone's time on here...

So stack recieved, hooked up to PC and was able to immedietly get into the new stack via BF.. ( I did NOT go about using the bluetooth option on my phone to set this up... Should I have initally gone that route??)

Then I proceeded to hook everything back up exactly as it was!!
I installed the ESC, connected the motors, added the FC
soldered up my :
* GPS
* Buzzard
* My TBS Sixty 9 (which I thought I fried, due to the pins in the harness touching. But I removed the power and ground wires and physically connected them to the board, and she lit-up, just like always and thats good.
* Power Wires
* Cap
* All of my Antenna's 
yatta yatta yatta.......

   

I then grab the exact same cable I have been using since thew get-Go
And using the same laptop....

Open BF - Connect to FC - I get lights on the FC, but no connection sound via USB on my laptop like I used too????

And I cant Connect!!!!!  Im like WTF Man....!!!!!
went into device manager and made sure my port setting were good. I made the baud rate 9600, like default...
thats all good.
unplugged in various USB devices like keyboard, mouse etc and my laptop DID make that connect / Disconnect sound

Restarted my laptop multiple times
still No-Go..
Went to oscars area and looked up his troubleshooting forum. Even downloaded the "ImpulseRC Driver Fix" program - Which was UN-EVENTFULL...

Tried multiple cables etc..

BF was on Com3 / Baud was set Auto (11500)
My options were - Com3, Com4 Bluetooth peripheral device and lastly I had an Virtual Mode (which up until now I've never used) and then the manual mode.

Normally I use Com3. I can remember a time or too, a while ago it used Com5. But since then Ive added a couple monitors to myset up, and now have 4 external monitors set-up. which I thought as well maybe that was my issue, so I disconnected 2 of them, just as it was before, and still NO Go!!

So I took the same cable I mentioned earlier, and went on my work laptop, opened BF, and it appeared to work, but stopped me and said I was using an older version of BF, and needed to istall 10.9 to continue. And BC its my work laptop, I DO NOT have ADMIN Rights, so I literally cant install or change squat on that!!

And so now Im back on the original New Dell Laptop - And that's running "Windows 11 Home"...

And tried connecting and still no go..

SO......

(AGAIN THANKS FOR STAYING WITH ME, AS IM TRYING TO BE AS DETAILED AS POSSIBLE FOR TROUBLESHOOTING PURPOSES)

i THEN TRIED COM4 IN bf - nope

Then !!!!
I tried the and I immedietly got into the program...
But it was weird.. It was like completly blank, and yes, I know...lol But what was weird is all of the options uptop, like GPS,SONAR etc were all lite up????
I never saw that or just never noticed that.

And me not being sure if that was the right thing to do, I paniced and IMMEDIETLY disconnected and came here to post and hopefully get some HELP......

Should I not use the  "Virtual Mode / Experimental" ???????
 
Im literally Scratching My Head at All of this.....

If ANYONE has anything I might of Missed, By All Means "Im ALL Ears"


Thanks Again......




im

Now I tried to use COM4

And it said serial port successfully opened with ID: 2 (whatever that means)
and then it like boots me out and then the connect button is lit up like it normally does when you arent connected????

I GOTTA be missing something.......


Hopefully our GuRu "SNOW" will see this relatively Soon.....lol




   

If everything was fine and working prior, Should I need to or Do I need to utilize any of these drivers on the BF main page under Hardware???

*CP210X USB /Zadig for windows / Impulse RC driver fix ????



   

stupid Question....

Should I have to flash new firmware onto the FC/ESC in order for BF to work???

If that was the case, Why would I be able to connect to the FC initially when I first recieved it??


And if Im unable to connect using Com3, Would/Should I flash new firmware onto the FC?


Any and All Help here would be greatly Appreciated...

So either your computer is the problem. Which is possible. Or PEBKAC.

I have no idea. You've had two stacks, both have died after you wired them up and plugged them in. Either the FC is a POS, you are doing something very wrong, the computer you use is a POS that has bricked two FC in some way, or a mixture of those three. I suspect it's the computer. Beyond that i can't help, I use Linux, it just works, no drivers (but some udev rules and perms changes), no fking around beyond that. I would suggest that as a possible solution, but Linux is hard to learn and well, hard in general. I've been using it for 20 years and it's not user friendly. As ever, YMMV.

(21-Mar-2024, 02:28 AM)Pathfinder075 Wrote: So either your computer is the problem.  Which is possible.  Or PEBKAC.

I have no idea.  You've had two stacks, both have died after you wired them up and plugged them in.  Either the FC is a POS, you are doing something very wrong, the computer you use is a POS that has bricked two FC in some way, or a mixture of those three.  I suspect it's the computer.  Beyond that i can't help, I use Linux, it just works, no drivers (but some udev rules and perms changes), no fking around beyond that.  I would suggest that as a possible solution, but Linux is hard to learn and well, hard in general.  I've been using it for 20 years and it's not user friendly.  As ever, YMMV.

OKAY.........

I completly understand where your coming from.....
And I pretty much agree with you bro....

Tell me this......

Lets say you just ordered a new stack
and your not using Linux.....

What are the steps you'd take to get this new stack going????

Would you.......

Recieve the new stack
Hook it up to power, and then proceed to set-up BF..
Right????

So you hook it up to power.....
You then open BF
then if the stack is connected to BF
And your options are to use Com3, Com4, or the Experimental feature...
Say you chose com3, and could'ny connect...
Then you try Com4...... Same result...

Is that bc your suppose to use the Virtual Mode/ Experimental mode.
And in that mode, you are suppose to set up your UARTS..
And that being said, you then are SUPPOSE to do a firmware update?????

and once you finally update the firmware to the latest release, you then can connect normally using com3 or com4???

And then continue as normal????

I feel like when recieving a new stack, your then suppose to do:

WHAT?????

Do you always have to do a firmware update in order to use BF? 
(is that the issue Im facing, I cant connect because the FC isnt sending data back to the BF software..
Hence the error I get that states, Serial port connected successfully, but "NO CONFIGURATION RECIEVED WITHIN 10 SECONDS, COMMUNICATION FAILED?????

Look Brother........

You get this error...
And then WHAT????

What your next "Go-To"......

Explain that error.......

Is that bc BF dosent see any info on that FC? and thats why it closes the serial port......

Im NOT trying to be a smart ass, Im just trying to understand the errors Im getting from BF, that are preventing me from getting into the program, and configuring my set-up????


Like:

yes these stack sit on a shelf for a some certain duration of time before getting shipped into the hands of the users. And in such the revisions that are put out, continue to be put out, which result in the level of patched continuing tyo go... 

10.0
10.2
10.3
10.4
etc etc etc.....

And the software that came on my FC is too old to be used or recognized by BF due to newer versions being put out?????

I very much so apprechiete your input and thank you for taking the time to read and respond to my post...
I just hope you understand where im coming from and my frustrations

Thanks, John

Can you connect to BF, without having to update the firmware on the new stack?

You'd choose what?????

   



Im doing my best here to explain the issues Im currently having.....


With all due Respect.......  Im going to leave it at that for right now....

The clue is in post #1 where you stated the following...

(20-Mar-2024, 11:04 PM)Coleon Wrote: So I took the same cable I mentioned earlier, and went on my work laptop, opened BF, and it appeared to work, but stopped me and said I was using an older version of BF, and needed to istall 10.9 to continue. And BC its my work laptop, I DO NOT have ADMIN Rights, so I literally cant install or change squat on that!!

And so now Im back on the original New Dell Laptop - And that's running "Windows 11 Home"...

And tried connecting and still no go..

That statement points the finger firmly at your Dell laptop with Windows 11 installed on it. If you've already tried the ImpulseRC Driver Fixer and Zadig then I'm not sure what else to suggest. I had a similar issue 2-3 years ago and nothing I tried resolved the issue. I work in IT so I'm no numpty when it comes to computers. The only thing that eventually resolved the issue was a complete format of my hard disk and a reinstall of Windows. I have no idea what the original root cause of the issue was because I wasted far too many hours unsuccessfully trying to fix the problem. There was probably a corrupt driver or a driver conflict somewhere but I never managed to find out what it was. If you resort to doing the same, make sure you have a backup of any important files on your computer first before you format the disk. The safest way to ensure that is to take an complete backup image of the whole hard drive to an external drive as an insurance policy using something like Acronis Cyber Protect Home Office (formerly Acronis True Image). The advantage of that over manual file backup is that you can't miss any files by mistake because it contains everything on your hard drive, so you simply just open/mount the backed up disk image and grab the files from it that you need.

As for installing a newer version of Betaflight Configurator on your work laptop, even without admin permissions to install anything you should still have write permissions to your user profile folder area. So download the "portable" version (betaflight-configurator_10.9.0_win64-portable.zip) from the Assets section, then go to the C:\Users\<YourLoginName> folder in Windows Explorer and unzip the contents of the Betaflight Configurator zip file to that folder. Everything will get unzipped to a new subfolder named "Betaflight Configurator". Just navigate into that folder and manually run the Betaflight-configurator.exe file from there. If you want you can also put a shortcut on your desktop to that file so it's quicker and easier to run each time.

https://github.com/betaflight/betaflight...tag/10.9.0

With regards to the "Virtual Mode (Experimental)" COM port option in Betaflight Configurator, that just allows you to mimic connection to an FC without an FC actually being attached to your computer so you can open the configurator and navigate through all the tabs and options. Even if you have an FC connected to your computer, if you select the "Virtual Mode (Experimental)" COM port it will just open a connection to a virtual (fake) FC and not the physical FC that is connected to your computer. Obviousy you can't save any configuration changes to a virtual FC bechase there is nothing to actually save those changes to, so each time you connect to the "Virtual Mode (Experimental)" COM port you will end up with default Betaflight setting shown in all the tabs.

I suspect it's called the Windows 11 virus. Windows 10 was bad enough for mangling drivers or just deleting them for no reason, 11 is apparently worse for it.

@OP, you asked what i do when I get a new FC.

If an AIO (and most I own are):

In terms of what i would do for a stack, pretty much the same.

I honestly do it the same way every time and I have my process down and it generally works every time without issue. Problems are identified quickly and early in the process, if they exist. Most of the time besides applying defaults after flashing the BF version i like, I setup everything else by hand, with the VTX table generally being the only thing that can be a pain in the ass. I've done it this way for five or six builds now and have had zero issues.

The problem on Windows is usually the STM driver. I did manage to get it installed on Windows 10 and it did work, but my Windows laptop was not a home version and I have some clue how to lock down Windows to stop Microsoft fking everything up on a regular basis. But nowadays I don't use Windows full stop any more, so it's moot for me.

If I was a serious builder, I would probably run a small desktop or laptop with Debian on it, set it all up just for running configurators and put it on my workbench. It would be there for configuring stuff and nothing much else. You wouldn't need a powerful system to do that. Like an old (cheap) 3rd or 4th gen intel laptop or desktop (with a couple of gig of ram and a 16gb ssd) or equivalent would be fine. Possibly even one of those old old netbooks from yesteryear with an intel atom cpu, that can be found on ebay for pocket change.

----

Based on your screenshot, you have driver issues probably caused by Windows.

(21-Mar-2024, 04:38 AM)Coleon Wrote: And the software that came on my FC is too old to be used or recognized by BF due to newer versions being put out?????

This doesn't happen. The version installed on the FC doesn't need to generally be updated. The manufacturer will use a version that works in whichever prototype they built. You should be able to happily use the version that comes with it, which is likely already setup. Only update firmware if you have a really good reason for wanting the latest version, like a function which is not in the version it came with. Or if you are a power user and understand the risks of running bleeding edge and beta software, like the death of hardware (look at the AT32 thread for what can happen when you continually install beta software or the ICM issue from 4.3.0 that killed gyros on FC's, to understand the possible consequences of running the absolute latest firmware).

Yes Betaflight Configurator might moan but it should still work. Mine continually moans that it is out of date and yes it isn't the latest configurator or firmware, but I need neither of those currently so won't update until i do.

Ok, let me back up.

First, I have always worked on the assumption that you have a  functional 
computer (PC) with the Betaflight configurator successfully installed and 
operational. Plus, you have a good USB cable that you know works. These 
two things are mandatory. At least in my book. So, this is first. If I recall 
correctly, I did have to run each of those little utilities when I did the initial 
installation. No big deal, just do it. 

Of course, I would not use a "work" or "company" computer without approval 
and maybe even assistance. Being a retired IT professional, staff were not 
authorized to use company issued computers for personal use. 

Having a functional computer with Betaflight configurator installed is paramount. 

I don't use a phone app as the screen is too small to be functional for me. Besides,
I like having the files on the computer. 

You also need a good, functional, USB Data cable, NOT a phone charger cable.     

I have bought plenty of FCs. They ALL come with Betaflight and a basic configuration. 
I have never needed to flash any of them. Ever. If the FC will not work with what ever
version of Betaflight comes with it, then I would have an issue. Everyone of them works
with the Betaflight version and configuration that it has from the factory.  

When I get a new FC (be it an AIO or Stack), the very first thing that I do is remove it 
from the box, plug it into my computer with a USB cable (you do NOT need a main battery),  
open Betaflight configurator, check everything and back it up. I do this BEFORE anything 
is attached or connected. The board will fire up with the USB connector. I am talking a New,
raw FC board here; Not touched by anything, no soldering, no mounting, nothing. Just the 
board. So far, there have been NO issues with any board that I have bought. 
They all work fine. They all had a basic tune on them. I back them up in this state.

The second thing to do is to connect the Rx receiver. If the FC has a 4V5 pad, that is a 5V
pad connected to the USB rail so it will power on with the USB cable. Bind the receiver to 
the transmitter, and check it in Betaflight. At this point, I have one thing connected to the FC, 
the Rx receiver. I make sure that it is bound correctly. I also check the switches and make 
sure that the MODES are set up. All of the controls are configured with only the receiver 
connected. Yep, I take another backup. 

At this point, you know that you have a functional FC and that  you can control it with 
your transmitter. A basic flight control system. 

Since the Video system needs power, I will connect the main battery power leads and the
capacitor. Now, I connect the video system and check to ensure it all works. Yes, everything 
is still on the bench where I can get to it and check everything. At this point, we have been
connected to Betaflight several times.

If all is good, then I solder the motor connector pigtails to the FC or ESC. Sometimes, I do 
go ahead and connect the motors and test them. So now, I know that everything works and 
the configuration has been backed up at several points.

You do NOT need to upgrade any ESC firmware; Not BLHeli, Not BlueJay, Not whatever.
If the ESCs don't work with what the factory installs and sets, then there is a problem and
upgrading firmware will very likely NOT fix it. 

If you don't have an operational system at this point, then there is no reason to put it into
a frame since there is still more work to be done just to get things functional.

Now that I know everything works, I put it all in the frame. 

Once assembled, we are into testing. First some hover tests and then some short LOS flights.

This method works every time and ensures that any issue is discovered and resolved as 
we go. Yes, NONE of my gear has had firmware upgrades, they are also running on the
stock factory tune, and the ESC firmware has NOT be messed with. They just work. 

If you can't connect to Betaflight with a USB Data Cable connected to a computer, then 
there is an issue with the computer or the data cable. Fix this first.

Ok, I got a new HP laptop with Windows 11 on it about a year ago. Since I haven't been actively
building, I am just getting around to installing the Betaflight Configurator on it. So, as follows:

I downloaded and installed Betaflight Configurator 10.9.0 as it was the last official release.
No problems, no issues, it installed smooth as butter and worked right out of the box. NO,
I didn't have to install any other drivers; at all. The software downloaded, installed, and just 
works. So, the version of Windows on my laptop had NO issues with it. The only issue is that
the Betaflight windows display everything HUGE. Now, this is a software development thing,
not a work on Windows thing.

So today (2023-03-24), I downloaded, installed, and ran the very latest Betaflight Configuator
10.10.0 - RC3. It installed fine and ran fine. However, the information in the window is still
HUGE. Yes, I know how to adjust Windows settings and did, but it made no difference. Why?
Because this is something that the developers have done and they provided no method to 
adjust it.

In conclusion, there is absolutely nothing wrong with running the Betaflight Configurator on
a Windows computer. Well, assuming it is not 20 years old or something and never been 
updated. Well, then, maybe. Still, that is not a Windows issue. That is just having antique
hardware and not keeping it updated properly. Betaflight Configurator works fine on a 
Windows computer and didn't need any extra drivers.

====================================================

Yes, I use the same process every time and it works every time. Plus, I am able to 
catch any issues before they become problems.

When I get a new FC board (yeah, mine are mostly AIO boards) or stack, my
procedure is as follows:

1) Remove the FC from the box or packaging. Immediately, plug in a USB data cable,
    plug it into my computer, and open Betaflight Configurator. At this point, the only
    thing connected to the board is the USB cable. If everything is working, the FC
    will be connected to Betaflight. All is good. I know that it will connect.

2) Once connected, I backup everything, forty ways from Sunday. Yeah, some might
    consider it overkill, but I can always bring back any FC to the original configuration.
    This is just cheap insurance. Plus, I will know precisely what version of Betaflight is
    on the board. I check everything and take some additional screen shots of some of
    the more important (to me) stuff. I also do some basic OSD configuration since I 
    know what I want. Now, backup everything, again.

3) Since I use connectors for just about everything, soldering on the connector pigtails
    is the next step. Specifically, I need a connector for the receiver (mine are XM+, SBUS),
    a connector for the VTX, motor connectors, the battery lead wires, and the capacitor.
 
4) With the connectors attached, I plug the USB cable into the computer, fire up
    Betaflight configurator, and check everything. Of course, I DO use a smoke stopper,
    then plug in the main battery. At this point, I know if there are any shorts. Normally,
    there are not. Now, I bind the receiver and make sure that it all works correctly. With
    the receiver fired up and working, I now have an operational flight control system.

5) The video system is next to be connected. Yep, plug in the Camera and VTX, then
     the main battery, then check to see if I get video in the goggles. If I do, then done.
     If not, then I debug the video subsystem. Normally, everything just works.

6) Now, I plug in the motors, plug the USB cable into the computer, plug the main battery
    into the quad, fire up Betaflight Configurator, and check the motor direction. Adjust if
    needed. At this point, I have a fully functional electronics and propulsion package. Basically,
    I have a fully operational quad, it just isn't in the frame yet. Yes, I will take another set of 
    Backups. 

     Yes, I do all of my soldering work on the bench and NOT in the quad. For me, that
     just makes things harder to work on and lends a higher possibility for mishaps. Why
     would I want to make things more challenging than they need to be. I don't.

7) Ok, I install the complete and tested electronics and propulsion package onto (or into) the
    frame. There are no surprises here since I already know that everything works and have
    been bench tested. 

8) Once assembled, I do some simple (in the house normally) hover tests; Nice and easy,
    about 3 to 6 feet (1 to 2 meters) off the ground and check that the quad responds to 
    the transmitter sticks. Yes, I do this in ANGLE mode as I don't need any runaway or
    tricky behavior in the house; just simple up, down, left, right, yaw, forward, and reverse.
    This is about testing the basic functionality, not about trying some stunts and stuff. IF 
    this all goes well, then I know that I have a fully functional quad that responds appropriately
    to the transmitter stick commands. Yeah, it will, in fact, fly.

9)  Outside, I will start with some easy and close it, LOS flights, just checking the flight 
     characteristics. After some LOS test flights, then I will move on to FPV flights. We are
     now, totally and fully operational. 

     NOTE:  Nothing is upgraded as it is NOT necessary. None of the ESC firmware configuration
                has been changed as that, also, is NOT necessary. Yep, absolutely NO tuning. If I
                notice something during the FPV flights, then I will look into tuning out that issue.

This methodology works first time, last time, every time. Plus, any potential issues or problems
are caught, diagnosed, and fixed right up front. 

======================================================

As for the OP, we don't get enough of a breakdown to see wherein the problem lies.

I would have thought that the second stack would have been fine. So, I am at a loss.


Later, iFly  

(21-Mar-2024, 04:38 AM)Coleon Wrote: OKAY.........



Recieve the new stack
Hook it up to power, and then proceed to set-up BF..
Right????

NO, the first thing is to connect a USB cable, plug it into a computer and the
fire up Betaflight Configurator. At this point, you do NOT need nor want the
main battery plugged in.

So you hook it up to power.....  << USB only, NOT the main battery.
You then open BF
then if the stack is connected to BF  << this should be automatic or at least click "Connect"

And your options are to use Com3, Com4, or the Experimental feature...
Say you chose com3, and could'ny connect...
Then you try Com4...... Same result...

You shouldn't have to select a Com port, it should automatically select the one
that it can use.  I have never had to select the com port. Betaflight Configurator
just figures out which one it needs and uses it. IF it doesn't connect, then there
might be an issue with the board.

Is that bc your suppose to use the Virtual Mode/ Experimental mode.  << NO
And in that mode, you are suppose to set up your UARTS.. << Again, this is automatic.
And that being said, you then are SUPPOSE to do a firmware update????? << NO, NOT necessarily

The very first thing that you need to do is backup the configuration. NEVER update the
firmware without first having a known good configuration backup. 

and once you finally update the firmware to the latest release, you then can connect normally using com3 or com4???

If the board is not connecting to Betaflight Configurator before any upgrading, then upgrading
is likely not the problem and will NOT fix it. 

And then continue as normal????

I feel like when recieving a new stack, your then suppose to do:

WHAT?????

Do you always have to do a firmware update in order to use BF? 

NO, You should NEVER "Have to" do a firmware update. If the board does not
connect to the Betaflight Configurator, then there is likely a problem with the board.

(is that the issue Im facing, I cant connect because the FC isnt sending data back to the BF software..  Yeah, probably. 

Hence the error I get that states, Serial port connected successfully, but "NO CONFIGURATION RECIEVED WITHIN 10 SECONDS, COMMUNICATION FAILED?????

Look Brother........

You get this error...
And then WHAT????

What your next "Go-To"......

Explain that error.......

Is that bc BF dosent see any info on that FC? and thats why it closes the serial port......

Im NOT trying to be a smart ass, Im just trying to understand the errors Im getting from BF, that are preventing me from getting into the program, and configuring my set-up????


Like:

yes these stack sit on a shelf for a some certain duration of time before getting shipped into the hands of the users. And in such the revisions that are put out, continue to be put out, which result in the level of patched continuing tyo go... 

10.0
10.2
10.3
10.4
etc etc etc.....

And the software that came on my FC is too old to be used or recognized by BF due to newer versions being put out????? NOPE. 

I have Betaflight firmware on the quads going back to version 4.0.2. Yep the new
Betaflight Configurator opens it just fine. I might even have an older Betaflight version
on one of my quads. If anyone says that the FC will not connect to the Betaflight configurator
due to being too old of a version, I don't believe them. That is just not accurate. 

I very much so apprechiete your input and thank you for taking the time to read and respond to my post...
I just hope you understand where im coming from and my frustrations

Thanks, John

Can you connect to BF, without having to update the firmware on the new stack? YES, Absolutely.

If a stack will not connect to Betaflight Configurator, the issue is much larger than versioning.
Something may have damaged the Betaflight that is on the stack or the stack itself might be
damaged. Now, this is two. Maybe try a different stack or FC. Do you have any other quads?
IF so, plug one of them into the computer with the USB cable and see if Betaflight Configurator
will connect.

You'd choose what?????

Seriously,

I do not know what is going on, but most of the suggestions will likely NOT resolve the issue.
Although it could be your computer, I really doubt it. To me, it looks like the firmware on the
FC is trashed. IF so, you could try flashing Betaflight, but this may or may not work. If there
is memory damage on the board, trying to flash firmware onto it will probably not work.

Since we don't have a precise and accurate listing of all of the steps that you have taken
and what resulted with each step, it will be challenging to determine what went wrong and
where. Although not impossible, it just seems odd that you would get two defective stacks.
IF that is the case, it does not bode well for SpeedyBee. I was considering a SpeedyBee
20x20 stack, but now, this is a bit concerning. 

If you don't have another quad, can you find someone who does and would let you connect
it to your computer and Betaflight Configurator?  You need to rule out the PC as being the
problem. Maybe it is, maybe it isn't, but you still need to know. By the way, if it is the PC,
then flashing would likely be useless as it probably wouldn't transfer correctly.

Later, iFly  

Only time I had weird problems like the OP described was when Windows Update mangled the STM drivers. Removing and reinstalling them fixed the problem, but I also made some choice permission changes to the registry and file system and stopped it from happening again. But for me it seems every time a newer version of windows comes out they find newer and more unusual ways to break everything.

(24-Mar-2024, 09:42 PM)Pathfinder075 Wrote: Only time I had weird problems like the OP described was when Windows Update mangled the STM drivers.  Removing and reinstalling them fixed the problem, but I also made some choice permission changes to the registry and file system and stopped it from happening again.  But for me it seems every time a newer version of windows comes out they find newer and more unusual ways to break everything.

Hi Pathfinder,

Very interesting. Maybe you just have old gear. What, you still running Windows XP?

I have been working with, providing tech support for, and programming for the Windows 
environment for over 3 decades in both government and private companies. In all this time, 
we just didn't have the issues that you mentioned. One thing, the users did NOT have administrator 
authority and were NOT allowed to install spurious applications. What causes issues is software that 
does not adhere to and work within the Windows API. I have personally run nothing but Windows 
computers. In fact, I currently have two operational Windows Laptops. The first computer that I 
installed the Betaflight configurator on, I did have to install the STM drivers...only once. None of the 
Windows updates have had any adverse effects. NO, I have never had to reinstall them. With this 
new Windows 11 computer, I did not need to install the drivers. Everything just worked. Yes, I have
automatic updates turned on. 

If software doesn't run correctly on Windows, then the programmer didn't do his job which is to
program for the environment, NOT try to program around it. 

Fortunately, most of these rogue programmers seem to have disappeared. That, and most of the 
goof balls have moved on to the phone as a tinker toy. Yes, our son has had apps trash his phone 
more than once. The phone is the new environment for those who think they can program.

Later, iFly  

The worst one was trying to get CUDA to run on Windows 10, every time Update ran, it overwrote the Nvidia driver and torched the CUDA install, which is a bit of a PITA when you are doing massive distributed computing on high end hardware. In the end I worked out a way to run what I needed using Linux and removed Windows from the equation.

About a year back an update went through and torched my dads desktop, he was on Win 10 and it did something to a samba mount and torched all the files on it. The issue was highlighted on a few tech sites at the time, but even when Microsoft rolled it back, he didn't get his files back, he no longer uses Windows either.

On Linux it just works, no need for drivers, just a couple of udev rules and add the user to two groups (instructions on the BF website). After that all configurators work without any messing. But Linux is not for everyone. Unless you are at least Windows Power User in experience, don't even bother. IT Pro's won't struggle either. Not going on a rant tonight.