Maybe you're using Windows 10?
If so, perhaps the name you're seeing comes from C:\Windows\INF\USBSER.INF (which is a hidden folder, so you have to do something special to access this INF folder within the Windows system directory). If the configuration from an INF is determining the name, then it doesn't matter what name the USB descriptors give. Microsoft loves their INFs and Registry and will almost always use those when they give info.
Trouble is, even though that file is just plain text, it also has a cryptographic signature. If you edit the file, the signature check will fail and Windows will consider it to be unsigned.
You can create your own INF. There are lots of sites with info about how to do this. For Windows 10, you'd probably start by just copying Microsoft's USBSER.INF. You can probably leave almost everything the same, but of course you'd want to change some or all of these lines near the end:
Code:
[Strings]
; localizable
MSFT = "Microsoft"
UsbSerial.DeviceDesc = "USB Serial Device"
UsbSerial.DriverDesc = "Microsoft USB Serial Driver"
To get your custom INF to override the one Microsoft provides, you'd need to do 2 things.
First, it needs to use a Hardware-Id match against the specific VID & PID. If you do this, please change the vendor ID. Don't use the same ID numbers as we use for Teensy. Either buy a number from the USB-IF (for $5000) or
buy one from MCS Electronics (for €15) or make one up that's unlikely to conflict with anyone else. Google can give you lots of sites talking about which VID numbers to use "unofficially". Just please do not use the same IDs as us or anyone else actually distributing a product if you're making your own INF.
These are the Compatible-Id match lines you need to replace with Hardware-Id matching:
Code:
[Standard.NTamd64]
%UsbSerial.DeviceDesc% = UsbSerial_Install, USB\Class_02&SubClass_02&Prot_01
%UsbSerial.DeviceDesc% = UsbSerial_Install, USB\Class_02&SubClass_02
Again, there are lots of sites with specific details about these lines (but surprisingly few who will tell you the whole process like in this message) so just search for INF Vendor & Product ID matching and I'm sure you'll find this detail and lots of examples.
Second, you must sign your INF. Or maybe there's still some way to reboot Windows into a special mode where this isn't required. But in the normal mode Windows runs, hardware ID matching overrides compatible ID matching, but no matter the matching used, signed drivers always take precedence over unsigned. So you really *must* sign your driver for it to have any effect on Windows 10, because Windows 10 will never use it if it sees the signed one in that hidden INF system folder.
Software-wise, you need 2 command line utilities: INF2CAT and SIGNTOOL. Both of these are free from Microsoft, as part of their enormous WDK download. Even if you never intend to write a driver, as far as I know you still need to download WDK just to get those 2 little utilities.
However, SIGNTOOL absolutely does require you to have a code signing certificate, which isn't free. Shop around. Lots of no-name sites resell the Comodo cert, for a lot less. Expect to pay about $75 to $100 for 1 year. After you go through the verification process, you'll end up the certificate. Hopefully it will comes as a .P12 file. If not, you'll need to convert it to .P12 or some other format CERTMGR can import. Then just run INF2CAT to get the .CAT file for your .INF (you can do this step before spending any money) and then run SIGNTOOL to add the signature info to the .CAT file.
When you run SIGNTOOL, make sure to give it the /TR flag with the URL of a trusted time server. Again, knowing this is an issue, google can turn up the details. SIGNTOOL also has some help info with /?, like most of Microsoft's command line utils. The timestamp from the time service will make your signature permanent, rather than only valid for the time period you paid the certificate authority (or their discount reseller).
All you have to do is put the .INF and .CAT into the same folder. Whenever Windows installs a INF, it will notice if a corresponding CAT file is in the same folder, and it will check if the CAT file contains a valid signature that matches the INF.
Once you've installed the INF, you might still see the old name if using the same PC, because Microsoft loves getting stale info from the Windows Registry even when you've installed new stuff. Usually incrementing the BCD version number in the USB descriptors is the easiest way to get Windows to recognize it's a newer version and needs to do the matching against INF files again.
That's all if you're using Windows. Things are much simpler for Macintosh and Linux.