I've been trying to set up my Crazyflie with the Crazyradio on my computer (Windows 10 OS), but for whatever reason I'm unable to get them to connect. I am able to use the bootloader to upload firmware to the Crazyflie, but after I do that I am unable to connect to it. If I click "Scan," in the client (the standalone or the client in a VM) the red LED on the Crazyradio turns on for a while before turning off again. The output for the client (VM and standalone) looks like this (with some variances, but finding devices and the part about the radio are the same):

I have manually updated the firmware on the radio and tried messing around with user permissions and other things in the VM, but all that's succeeded in doing is messing up how the VM interacts with the Crazyflie such that trying to flash firmware to it now guarantees corrupted firmware on the copter. Works fine in the standalone Windows client, though. On that topic, though - the last time I tried flashing firmware to the Flie via the VM I ended up with a problem such that the M2 light turned on when it restarted and it would not turn off until I unplugged the battery. Just out of curiosity, I tried looking at available devices in the Windows client and saw that there was a copter that I could connect to, despite the fact that its firmware was corrupted. After that, I managed to restart it in firmware mode and flashed firmware to it again from the standalone client, which fixed the firmware, but now there's no longer a Crazyflie for me to connect to. Any suggestions?

It sounds like your Crazyflie radio address has changed. To verify the radio address you can connect to the Crazyflie using an USB cable, you will then be able to change radio channel/datarate and address. The client will by default try to connect using the address 0xe7e7e7e7e7.

For your bootloader experience, there might have been lost packets resulting in data corruption during the flashing process. As you discovered the radio CPU is independent to the main CPU which is why you could still connect, and it is alyways possible to try again since the radio bootloader cannot erase itself.