Microtech USB Devices Driver Download



  • Microtek Scanner Driver for the ArtixScan Series. This driver offers support for most of the ArtixScan scanners.
    • July 22, 2014
    • Windows (all)
    • 55.1 MB
  • Microtek Scanner Driver for the Bio Series. This driver offers support for most of the Bio Series scanners.
    • July 22, 2014
    • Windows (all)
    • 21.3 MB
  • Microtek Scanner Driver for the ScanMaker Series. This driver offers support for most of the ScanMaker scanners.
    • July 22, 2014
    • Windows (all)
    • 77.5 MB
  • Direct download for the latest driver belonging to the flatbed scanner Microtek SlimScan C6.
    • October 29, 2003
    • Windows 2000/XP
    • 3.7 MB
  • ScanWizard DI version 3.
    • July 27, 2009
    • Windows XP/Vista/7
    • 20.1 MB
  • ScanWizard DI version 3.
    • July 27, 2009
    • Windows XP/Vista/7
    • 20.1 MB
  • ScanWizard DI version 3.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.5 MB
  • ScanWizard DI version 3.
    • July 27, 2009
    • Windows XP/Vista/7
    • 20.7 MB
  • ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista/7
    • 12.6 MB
  • ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista/7
    • 12.6 MB
  • ScanWizard Pro version 6.
    • July 27, 2009
    • Mac OS 9.x
    • 23.5 MB
  • ScanWizard Pro version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 15.0 MB
  • ScanWizard Pro TX version 7.
    • July 27, 2009
    • Windows 2000/XP
    • 8.7 MB
  • ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista
    • 12.6 MB
  • ScanWizard Pro TX version 6.
    • July 27, 2009
    • Windows XP/Vista
    • 14.9 MB
  • ScanWizard Pro version 7.
    • July 27, 2009
    • Windows 2000/XP
    • 10.1 MB
  • ScanWizard Pro version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 14.1 MB
  • ScanWizard Pro version 7.
    • July 27, 2009
    • Windows 2000/XP
    • 12.6 MB
  • ScanWizard Pro TX version 7.
    • July 27, 2009
    • Windows 2000/XP
    • 8.7 MB
  • Microtek ScanWizard Pro version 7.
    • July 27, 2009
    • Windows 2000/XP
    • 11.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 12.6 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.9 MB
    • July 27, 2009
    • Windows XP/Vista/7
    • 12.6 MB
  • Microtek ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista/7
    • 45.9 MB
  • Microtek ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista
    • 11.8 MB
  • Microtek ScanWizard Pro version 3.
    • July 27, 2009
    • Windows 2000/XP
    • 9.3 MB
  • Microtek ScanWizard Pro version 7.
    • July 27, 2009
    • Windows XP/Vista
    • 11.8 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard Pro version 3.
    • July 27, 2009
    • Windows XP/Vista/7
    • 8.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows XP/Vista/7
    • 18.9 MB
    • July 27, 2009
    • Windows 2000/XP
    • 18.9 MB
    • July 27, 2009
    • Windows Vista / 7
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.9 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB
  • Microtek ScanWizard Pro version 3.
    • July 27, 2009
    • Windows 2000/XP
    • 9.1 MB
  • Microtek ScanWizard 5 version 6.
    • July 27, 2009
    • Windows 2000/XP
    • 18.1 MB

Microtech Usb Devices Driver Download Windows 8

-->

Versions supported

  • Windows 10
  • Windows 8.1

Microsoft has a tool specifically designed for fixing problems with USB 3.0 devices and drivers. Download it from the official support website, then run the program as you would any other. It will attempt to diagnose your USB 3.0 problem. If one is discovered, allow it to continue with an attempted fix. Hi, I was advised by a Dell technician a while ago that it is recommended to download the latest device drivers from the Dell Support site to a USB stick before doing a clean installation of Windows 8.1. Should I download the drivers to my hard drive (c: drive) and then copy and paste them over to the USB flash drive. Drivers Usb free download - Drivers For Free, CopyTrans Drivers Installer, Adaptec ASPI Drivers, and many more programs.

MICROTECH LAPTOP SOFTWARE The MicroTech v4.1 software is compatible with all MicroTech laptop tune-able ECU’s & Windows based software up to Windows 10. (If you have a previous version MicroTech Laptop software, you’ll need to uninstall it first.) The USB driver must be downloaded to enable the USB Laptop Adapter to work (not required. Usb-robot is couple of programs that allow you to send commands to usb devices. The usbsnoopy replay feature does not currently work with the ScanMaker 3600, but the 'usb-robot-slave' program works and usb-robot provides an example of how to use libusb. The FTP site for Microtek SCSI command sets. Jonathan Buzzard's Linux USB Scanner page.

Applies to

  • Device manufacturers of CDC Control devices
Driver

Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.

  • Improved PnP and power management by the driver (such as, handling surprise removal).
  • Added power management features such as USB Selective Suspend.

In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.

Usbser.sys installation

Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

Note

If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.

Windows 10

In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.

USBClass_02

USBClass_02&SubClass_02

  • If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
  • If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
  • If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.

Note

Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.

Windows 8.1 and earlier versions

In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.

The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.

For more information, see this KB article.

Configure selective suspend for Usbser.sys

Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:

Devices

Microtech USB Devices Driver Download

To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:

Devices
  • '0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.

  • '0x00000000': Enters selective suspend only when there are no open handles to the device.

That entry can be added in one of two ways:

  • Write an INF that references the install INF and add the registry entry in the HW.AddReg section.

  • Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.

    For more information, see Microsoft OS Descriptors.

Develop Windows applications for a USB CDC device

Microtech Usb Devices Driver Downloads

If you install Usbser.sys for the USB CDC device, here are the application programming model options:

  • Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.

  • In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:

    Win32 programming model:

    • .NET framework programming model:

Microtech Usb Devices Driver Download Windows 10

Related topics