Using v3.1.8 and upgraded to Win 10 1909 without any DAX naming issues. The upgrade seemed pretty light, so not sure if there was anything in the upgrade that would have caused the problem. In any event, thanks Flex team for resolving this one!
I'm using the latest 2.x version. On Saturday I sat through the "October" Win update. While holding my breath, I restarted and all seemed OK. I did experience two minor issues. DAX no longer starts automatically. Once I manually activate it, all works just fine. On my dual monitor setup, the two monitors got reversed, and all the program icons moved to the primary monitor. Simple fix moving them. I don't regard either as being caused by Flex software.
I "downgraded" from Win 7 to Win 10. Lots of problems from a formerly stable, reliable system. The 1909 upgrade had downloaded but not installed. When I opened SmartSDR, I got a portcls.sys BSOD. A couple of reboots and 1909 installed. When I opened SmartSDR, all of my CAT entries were gone and I had the default set! The virtual ports are still listed in the Device Manager. So the adventure begins as I try to restore my setup.... A knob radio looks better every day that my $1500 deposit sits in Watsonville waiting for the new year.f
I might be wrong, but wasn't the latest updates supposed to fix problems associated with Windows updates? I am not going to brag, but so far I have not had any of these issues. The only thing that I might be able to attribute this to is that I always shut down all Flex and Flex associated software before allowing any updates. The repair process is not that difficult and enjoying my Flexradio is well worth the occasional PIA.