Installing TUSB3410 driver files on customer PCs

We currently have a product that uses the TUSB3410 to provide USB connectivity. We have modified the INF file to have our VID, PID, and description. This works, at least on XP, but it requires more user interaction that we would like.

When installing our software we copy the driver files to C:\Program Files\(OurFolder)\Drivers. When the user connects the device, they have to browse to (OurFolder)\Drivers and the correct sub-folder underneath that. This causes no end of confusion.

The first thing I did is to get the latest driver, 6.7.2 (we had been using 6.5.9017).
This file contains an exe, when when run installs a bunch of files to
C:\Program Files (x86)/Texas Instruments Inc/TI_WDF_USBUART_SINGLE_DRIVER_V6.7.2_WHQL/
Inside that folder is another setup.exe file, which when run copies files to C:\Windows\tiinst. Neither of these places is searched by windows when looking for a driver.

1) Am I supposed to run one or both of those exe files on the customer machine? Or should my installer copy some or all of the extracted files to the customer machine? If so, which files and where should they be placed? (I realize that I have to replace the INF file with my edited version that has the correct VID and PID numbers.) What can I do so that windows will automatically find the appropriate driver files when the device is plugged in.

Why are these files distributed as installers rather than a zipped folder? Does either one of the installers do something else that I must do in my own installer? Or that requires me to run your installer on the customer machine?

2) Will this driver work for Win 8 and 8.1? There is a November forum post that points to a 6.7.1 driver specifically made for Win8 -- is that post obsolete?

3) The current drivers won't install on some Win7 machines -- windows doesn't want to install the unsigned driver. From browsing the net, it appears that this is related to either Secure boot or Win7-64 or both. How can we get the drivers installed on these machines?

Thanks for your help,

  • Hello Martin,

      The first .exe file (the one that you download form is just a wrapper that contains the installer files. When you run it, it on ly extract those files and place them on C:\Program Files (x86)/Texas Instruments Inc/TI_WDF_USBUART_SINGLE_DRIVER_V6.7.2_WHQL/ .The second .exe file is the driver installer.

      All that you have to do is replace the INF file with the one that contains your VID/PID before to excecute the installer (the second .exe file).

      The distributed driver v6.7.2.0 is signed for Win XP, Win7, Vista and Win8. We always recommend to use the latest driver version as they have important updates and bug fixes.

      Please note that if you modify the INF file the signature will be lost as it is linked to a specific INF file and it’ll cause that you require to run the windows using the “Disable driver signature enforcement” mode.





  • In reply to Roberto Diaz:

    Thank you for your help.

    The second exe (the driver installer) appears to do nothing more than copy the appropriate files (32-bit or 64-bit) to C:\Windows\tiinst\TUSB3410. Is this true, or does it have additional functionality?

    Can I replace this installer with my own installer? This would allow me to provide additional funcionality. For example, I could pre-install the driver so the user does not have to navigate to C:\Windows\tiinst\TUSB3410 during the new hardware wizard.

    Regarding driver signatures, I have done some research on the problems resulting from changing the INF file. Using "Disable driver signature enforcement" is not a viable solution for end users. It looks like under Windows 8 we really have to get our own signature or WHQL certification. From other posts on this forum it looks like you will certify us as a driver reseller so that we can get our own WHQL certification using a "Driver Update Acceptable" submission. We will pursue this further with you via email.

    Since you are bound to get more questions about this as Win 8 becomes more predominant, may I suggest  that you (or someone at TI) write up an App Note that discusses this issue and the possible solutions. These could include:

    a) using the TI VID and PID in my product. Do you permit this? If not, describe it anyway and say you don't permit it, because it's going to be a common question.
    b) Self signing
    c) WHQL Driver Update Acceptable submission.
    d) Forcing use of TI driver with our own VID and PID during the new hardware wizard. A pain to do and probably not acceptable for end users.
    e) Disable driver signature enforcement (not acceptable for end users)

    Details about the process of getting a signature from Verisign and WHQL certification would also be useful.

  • In reply to Don Martin:

    Hello Martin,

                     The second exe copy the appropriate files for the specific OS and also execute a co-installer that is in charge of pre-install and install the driver. You are free to generate your own installer in order to fulfill your customers requirements.

                     In order to obtain the WHQL signature for your modified INF file we can provide you reseller right for this driver version and you’ll be able to go through the DUA (Driver Update Acceptable) submission, please provide me your Microsoft account details to my e-mail ( ). Please note that the DUA submission only accept small changes to the INF file (as you are only including your VID/PID there should not be problem).



  • In reply to Roberto Diaz:

    > also execute a co-installer that is in charge of pre-install and install the driver.

    Can you explain what this means?

    When I run your installer it does not appear to copy the driver to the driver store (Win7) or copy the inf file to C:\WIndows\Inf (XP). That's what I would expect "pre-install" to do, so that when you connect a device the system associates the correct driver without user intervention. Do you mean something different?

    I cannot replace your installer with my own unless I know exactly what your installer is doing. Do I need to run the coinstaller? How, with what parameters, etc. Are there any registry settings changed?

    Is there a way to run your installer silently, so that my application install and the driver install appear to be one action? This might be another approach.


  • In reply to Don Martin:

    I was wrong about the pre-install -- my test setup had bugs. Sorry...

    Running your driver installer does pre-install the driver. After running the installer, when you connect a device with the correct VID and PID, the system finds the driver and installs it for that device. Under Windows 7 this happens without user interaction. Under XP, the user gets the new hardware wizard, but they can select "Install the software automatically" and it will find the driver without further interaction (you do not have to browse to a particular folder).

    This simplifies things, so we will probably elect to use your installer. If it is possible to run your installer silently that would be very useful to know about.


  • In reply to Don Martin:

    Hello Martin, 

                    That’s good to hear that the installation process is clear now.

                     In order to run the installer on silent mode you only have to ad a “–s” when you execute the setup.exe file. i.e: Setup.exe –s



  • In reply to Roberto Diaz:

    That works perfectly. Thanks!

  • In reply to Don Martin:

    As a follow up for anyone else trying to run the TI driver installer from their own installer.

    If the driver is already installed, running the installer again brings up a message box that says "This version of TUSB3410 is already installed. Click OK to uninstall the version of (sic) your computer or Cancel to cancel this wizard". This can be confusing to users if you are spawning the TI driver installer from your own installer, and the user clicks OK they uninstall the driver which is not what you want them to do.

    You can check whether the TI driver is already installed by checking the registry keys at HKLM/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall/TUSB3410. If the driver is not installed this key will not be present. If the driver is installed, the DisplayVersion  value will contain the version number as a string (for example "").

    Exactly how you check this registry key depends on what installer software you are using, of course.

  • In reply to Don Martin:

    Hello there,

    Don is right on target with his suggestion regarding the need for an App Note that includes all of his bullet items. My company would like to have their product support Win8, so I am learning about these driver issues that we were not previously concerned about.

    I have the question he listed in "a)". That is, do you permit customers to use the TI VID and PID in their products?

    If this is possiblem, are there any fees involved?

    Another question: Is there a fee for getting "reseller rights" from TI?


    Gary Wagner


  • In reply to GARY WAGNER:

    Hello Gary,

                     Please find attached a history review of the driver, here you will find the problems that has been solved for the driver on the past releases.

                     The answer for “a)” is: Yes, the customer are able to use the same VID/PID if they are using the generic TUSB3410, if they are planning to use any other specific driver/firmware we recommend them to use their own VID/PID.

                     If you want to obtain reseller rights for the latest TUSB3410, you only have to send me your Microsoft company account name and we will be able to provided it.