LabVIEW
USB CDC Device Communication issues
USB\VID_A0A0 is not an officially registered USB vendor ID, so someone has been indeed hacking.
Do NOT try to use NI-VISA USB Raw. Aside from the problem that you encountered that Windows 10 requires you to have signed drivers and a NI VISA INF file is only signed if you can sign it yourself, which requires you to have a valid signing certificate, you also do NOT want to communicate on USB Raw level even if that device is fully and completely implementing an official USB class such as the USB CDC ACM. That is simply insane. Such a device does not work like a normal serial port where you can simply write a command to and read the response, but you have yourself also to bother about setting up the correct USB endpoints first and handling possible interrupt bus transfers as well.
On the other hand does Windows not just blindly install a device driver for a device only because it claims in its USB identification descriptor to be a certain device class but it also wants to understand what sort of device that is and uses for that the VID and PID. But your device has not an officially recognized VID and PID. What you would need is a Windows INF style file for your device that tells Windows that this VID and PID is indeed a device that the standard usbser.sys driver can handle if it can, or provides its own custom kernel device driver that can do that.
I'm not familiar with Termite but it looks to me as if it is doing some low level access of serial ports or something. Hard to tell however. Fact is that VISA and Putty simply access the Windows COMM API and do not deal with serial ports themselves beyond what that API allows.
It means that these applications only can access serial ports that are installed under windows as such and that it can't do anything beyond what the Windows API exposes, which is not the full capability of many underlying device driver. There is an option to do some IO passthrough to access driver specific extensions but that is only an option if you do exactly know the driver in question. NI uses that for instance for their own serial port drivers for their hardware which support additional things such as software selectable IO direction (for RS-485 operation or electrical isolation state). And the only software that supports that is NI VISA as the according IO Control codes aren't really documented.
So there is a lot of if's and when's here and the fact that one application seems to work with your device tells very little as we have no idea about what exact API it uses and from a quick look at the Termite website, they do give some information and even allow some plugin development for their tool, but nothing that I would see about the low level interface to the serial ports.
My guess is that your device is a non-standard device that does a few things not quite as it should despite you claiming that it is a full USB CDC class device (but why would someone going through the trouble of writing a full specification class CDC driver not take the little extra effort to apply for an official USB Vendor ID?) and Termite somehow either actively works around such misbehaviour or maybe simply ignores certain errors and happily churns on even after them. The application was developed by someone to use in the field with their own hardware so it could very well be that it simply ignores certain errors categorically or specifically and doesn't abort communication on them.
