All devices operating in MTP mode are supported. Note: The MTPdrive is not a replacement for the device's factory (or Windows default) device driver. You must be able to connect your device to the computer and have it visible in the Windows Explorer, before it can be mapped as a drive letter using the MTPdrive. From desktop to critical infrastructure, Tripp Lite products and solutions power and connect the computers, networking equipment and electronic devices that form the foundation of our digital world. Headquartered in Chicago since 1922, Tripp Lite has offices and partners worldwide. Drivers & Software Updates Search. Do you have the latest drivers for your device? Our engineering team is constantly adding, updating and improving our drivers to ensure optimal performance.
Dec 21, 2020 • Filed to: USB Recovery • Proven solutions
Have you ever had difficulty connecting your devices to your computer using a Prolific USB to Serial adapter? If yes you are lucky to find this page, it will give you all the information need to fix an unresponsive Serial driver adapter. You may have noticed a yellow exclamation mark hovering over or beside the USB to Serial Driver when searching your Device Manager and if you have we can all agree that it signifies a prevailing problem.
Overview of the Error
If you are not able to connect your device to your PC using a USB to Serial adapter it may be that
- The USB driver is outdated
- The USB Driver is missing
- Or even a corrupted driver
While you can't be so sure what the exact problem is there are solutions you can adopt to fix the issue once and for all. Read on to find quick fixes to resolve the problem.
1# Fix Prolific USB to Serial Driver not Working
Solution: Roll your Prolific USB to Serial Driver back to an older version
Updating your drivers often work wonders for your system because it makes sure that it runs on the latest features that guarantee maximum functionality. Unfortunately updating your drivers can cause this kind of error especially if your latest update does not work too well with your hardware. Once you upgrade your PC to the latest Windows version your Prolific USB to Serial Driver also updates to the latest driver software and if the driver is not compatible with your Hardware issues may arise. To correct the error, you will have to download the driver again by following these steps.
- Right-click on your PC Start button and open Device Manager
- Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver
- For driver software click My computer
- From My computer select 'Let me pick from a list of drivers available'
- Choose an older version from the list then click Next
- The driver you selected will be installed automatically
- Once it has been downloaded reconnect the driver to see if it works.
2# Fix Prolific USB to Serial Driver 'Coder 10'
Driver issues reveal themselves in so many ways or through messages such as
- This device will not start (Code 10)
- There is no driver installed in this device
- The driver was not successfully installed
A code 10 error may arise because the chip you are using is not an original one. If you are using a fake, the manufacturer has a way of disabling it due to copy write infringement and the copy write takes effect once you download a recent update. To protect your PC from getting this code, you will have to make sure that your Windows 10 never updates a driver without approval. Updates come in the form of 64 bit and 32-bit drivers. Below we will show you how to work your way around the problem.
Window 64 bit Fix
To fix Windows 64 bit OS including Prolific USB to Serial Adapter, follow through these steps.
- Download 'PL2303_64bit_Installer.exe and Save
- Remove every USB to Serial adapter from your PC and double click the 'PL2303_64bit_installer.exe
- Follow the prompt by plugging in one USB to Serial adapter the click on Continue
- Reboot your PC to get Windows up and running
If you have followed these process through and you still see the same error go to your device manager
- Open the control panel and navigate to Device Manager
- From your control panel navigate to the System category and click the Hardware tab
- Scroll to the LPT/COM port and double click Prolific USB to Serial Comm Port
- Click Drivers in the Properties section
- The Driver you choose should read '3.3.2.102 with an appropriate date attached
- If the date is wrong then it means the wrong driver was installed
- Unplug the Serial adapter and run the steps again to install the correct driver
Sdt Usb Devices Driver Download For Windows 10 64-bit
Window 32-bit
For Windows 32-bit OS systems follow these steps
Sdt Usb Devices Driver Download For Windows 10 Pro
- You will have to download the 'PL-2303_Driver_Installer.exe and save from Microsoft download link
- Run the program and eradicate the driver if you can
- Run the installer once more to install a correct driver
To Troubleshoot for error if your device still does not work
- Go to Control panel, enter System to access your Device Manager
- Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port
- Click Driver in the Windows Properties section
- The driver must be numbered as '2.0.2.8' and dates accordingly
If the driver was not installed, remove the Serial adapter then run 'PL2303_Driver_Installer.exe' again. Follow directions in Device Manager to download the correct driver
The three solutions listed in this article have proven to be quite helpful in fixing a Prolific USB to Serial driver not working on Windows 10. They may appear confusing at first but if you follow each step in detail you can resolve the issue.
Sdt Usb Devices Driver Download For Windows 10 Windows 7
Video Tutorial on How to Fix USB Device Not Recognized
Dec 21, 2020 • Filed to: USB Recovery • Proven solutions
Have you ever had difficulty connecting your devices to your computer using a Prolific USB to Serial adapter? If yes you are lucky to find this page, it will give you all the information need to fix an unresponsive Serial driver adapter. You may have noticed a yellow exclamation mark hovering over or beside the USB to Serial Driver when searching your Device Manager and if you have we can all agree that it signifies a prevailing problem.
Overview of the Error
If you are not able to connect your device to your PC using a USB to Serial adapter it may be that
- The USB driver is outdated
- The USB Driver is missing
- Or even a corrupted driver
While you can't be so sure what the exact problem is there are solutions you can adopt to fix the issue once and for all. Read on to find quick fixes to resolve the problem.
1# Fix Prolific USB to Serial Driver not Working
Solution: Roll your Prolific USB to Serial Driver back to an older version
Updating your drivers often work wonders for your system because it makes sure that it runs on the latest features that guarantee maximum functionality. Unfortunately updating your drivers can cause this kind of error especially if your latest update does not work too well with your hardware. Once you upgrade your PC to the latest Windows version your Prolific USB to Serial Driver also updates to the latest driver software and if the driver is not compatible with your Hardware issues may arise. To correct the error, you will have to download the driver again by following these steps.
- Right-click on your PC Start button and open Device Manager
- Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver
- For driver software click My computer
- From My computer select 'Let me pick from a list of drivers available'
- Choose an older version from the list then click Next
- The driver you selected will be installed automatically
- Once it has been downloaded reconnect the driver to see if it works.
2# Fix Prolific USB to Serial Driver 'Coder 10'
Driver issues reveal themselves in so many ways or through messages such as
- This device will not start (Code 10)
- There is no driver installed in this device
- The driver was not successfully installed
A code 10 error may arise because the chip you are using is not an original one. If you are using a fake, the manufacturer has a way of disabling it due to copy write infringement and the copy write takes effect once you download a recent update. To protect your PC from getting this code, you will have to make sure that your Windows 10 never updates a driver without approval. Updates come in the form of 64 bit and 32-bit drivers. Below we will show you how to work your way around the problem.
Window 64 bit Fix
To fix Windows 64 bit OS including Prolific USB to Serial Adapter, follow through these steps.
- Download 'PL2303_64bit_Installer.exe and Save
- Remove every USB to Serial adapter from your PC and double click the 'PL2303_64bit_installer.exe
- Follow the prompt by plugging in one USB to Serial adapter the click on Continue
- Reboot your PC to get Windows up and running
If you have followed these process through and you still see the same error go to your device manager
- Open the control panel and navigate to Device Manager
- From your control panel navigate to the System category and click the Hardware tab
- Scroll to the LPT/COM port and double click Prolific USB to Serial Comm Port
- Click Drivers in the Properties section
- The Driver you choose should read '3.3.2.102 with an appropriate date attached
- If the date is wrong then it means the wrong driver was installed
- Unplug the Serial adapter and run the steps again to install the correct driver
Sdt Usb Devices Driver Download For Windows 10 64-bit
Window 32-bit
For Windows 32-bit OS systems follow these steps
Sdt Usb Devices Driver Download For Windows 10 Pro
- You will have to download the 'PL-2303_Driver_Installer.exe and save from Microsoft download link
- Run the program and eradicate the driver if you can
- Run the installer once more to install a correct driver
To Troubleshoot for error if your device still does not work
- Go to Control panel, enter System to access your Device Manager
- Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port
- Click Driver in the Windows Properties section
- The driver must be numbered as '2.0.2.8' and dates accordingly
If the driver was not installed, remove the Serial adapter then run 'PL2303_Driver_Installer.exe' again. Follow directions in Device Manager to download the correct driver
The three solutions listed in this article have proven to be quite helpful in fixing a Prolific USB to Serial driver not working on Windows 10. They may appear confusing at first but if you follow each step in detail you can resolve the issue.
Sdt Usb Devices Driver Download For Windows 10 Windows 7
Video Tutorial on How to Fix USB Device Not Recognized
USB Solution
- Recover USB Drive
- Format USB Drive
- Fix/Repair USB Drive
- Know USB Drive
- August 22, 2019 2.9.8
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.8
Released
August 22, 2019
Type
ZIP
Filesize
3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 controller
- Graphics card with 24 or 32 bit
- Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Added several internal interfaces for particular sensors (J003).
- January 25, 2019 2.9.6
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.6
Released
January 25, 2019 Number five software usb devices driver download free.
Type
ZIP
Filesize
3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 controller
- Graphics card with 24 or 32 bit
- Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Added missing Tonemapping Auto property.
- May 4, 2018 2.9.5
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.5
Released
May 4, 2018
Type
ZIP
Filesize
3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 controller
- Graphics card with 24 or 32 bit
- Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.
- November 21, 2017 2.9.4
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.4
Released
November 21, 2017
Type
ZIP
Filesize
3.2MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Repaired not working J003 mono sensor pattern fix on particular video formats.
- This driver version is the last that works in Windows XP.
- January 9, 2017 2.9.3
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.3
Released
January 9, 2017
Type
ZIP
Filesize
3.2MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Added a pattern fix for J003 mono sensors.
- January 9, 2017 2.9.1
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.9.1
Released
January 9, 2017
Type
ZIP
Filesize
3.2MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.
- January 15, 2016 2.8.9
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.8.9
Released
January 15, 2016
Type
ZIP
Filesize
2.3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Changed certificates so that the driver can also be installed in Vista.
- November 9, 2015 2.8.7
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.8.7
Released
November 9, 2015
Type
ZIP
Filesize
2.3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Fixed an error which can appear when using sharpness on older CPUs.
- October 20, 2015 2.8.5
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.8.5
Released
October 20, 2015
Type
ZIP
Filesize
2.3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Fixed a bug which can appear on LivePause call.
- July 15, 2015 2.8.0
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.8.0
Released
July 15, 2015
Type
ZIP
Filesize
2.4MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Support of DFK ECU010-L34 with serial number property.
- Added tone mapping.
- February 17, 2015 2.7.33
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.7.33
Released
February 17, 2015
Type
ZIP
Filesize
2.4MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.
- February 5, 2015 2.7.32
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.7.32
Released
February 5, 2015
Type
ZIP
Filesize
2.4MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.
- January 14, 2015 2.7.31
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.7.31
Released
January 14, 2015
Type
ZIP
Filesize
2.3MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Support for IMX236 based cameras.
- Support for RGB64 color formats.
- Several performance improvements.
- June 6, 2014 2.7.9.1152
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.7.9.1152
Released
June 6, 2014
Type
ZIP
Filesize
2.1MB
Requirements
- Intel Core i3 or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast.
- Added new property: Highlight reduction.
- Added new property: White balance temperature controls.
- Pixelfix for Y16 cameras now works as expected.
- VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.
- January 1, 2014 2.6.5.1014
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.6.5.1014
Released
January 1, 2014
Type
ZIP
Filesize
1.9MB
Requirements
- Intel Pentium IV or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- Fixed missing auto-gain for DFK AFU130.
- Fixed focus when start value is out of auto_focus_range.
- Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong.
- Fixed auto focus ROI not working for 21*UC cameras.
- Fixed crash on load/connect with certain cameras 22/72xUC.
- Fixed previous exposure settings not being loaded on reconnect.
- Complete reworking of internal property system.
- Fixed Windows XP driver load crash.
- Fixed drop counter to be accessible from DirectShow.
- Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible).
- Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.
- February 26, 2013 2.4.14.851
Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
Version
2.4.14.851
Released
February 26, 2013
Type
ZIP
Filesize
1.9MB
Requirements
- Intel Pentium IV or similar, 2 GB RAM
- USB 3.0 or USB 2.0 controller (depends upon camera model)
- Graphics card with 24 or 32 bit
- Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit)
- DirectX 9.0c or higher
Changelog
- WHQL certification.