A crash in the background radio scan now reports properly. FoxSDR looks for radios in a separate background process so that a faulty driver cannot take the app down. When a driver crashed there on two threads at once, the crash handler mistook the second thread for a fault inside itself and ended the process before its report was written. It now waits for the first report to finish, needs no memory from Windows while writing it, and tells FoxSDR which driver it was in. Your radio was never affected: FoxSDR carried on either way.
USRPs are only searched for when one can be there. FoxSDR now asks the USRP driver for devices only when a USRP is plugged in by USB or your saved radio is a USRP. If you use a network USRP (N2xx or X3xx), tick the new Look for network USRPs option beside Refresh in Source once; a note there says when network USRPs were not searched.
Not yet tried on the hardware. The crash was reproduced and fixed with staged faults in a test harness; no network USRP was available here. If something behaves differently on yours, REPORT A BUG / DISLIKE reaches us directly.
SHA-256 of foxsdr-setup-0.99.39.exe:
93ea1e3736b8917eb635febd394da9b8d6f94a4351b9f6689d64616be14a2cb5
SHA-256 of FoxSDR-0.99.39-x86_64.AppImage:
87f3d1b42661ffb72ad78c70e39a75901f139654095672ac9ec3b8d20b0428fd
SHA-256 of foxsdr-0.99.39-linux-x64.tar.gz:
5319dd448d56bf5e46d669eb33cf2e09ef176301092a0288cbcad33cae750172