Multitech MT5634ZBA-USB failing to finish installation

Well I finally know which part of the driver stack is no longer functional.  After spending hours reading through the "Hardware Dev Center" details I determined that a log of the device install procedure exists in c:\windows\inf\setupapi.dev.log.  In my case this clearly shows that the problem lies with "usbser.sys":

>>>  [Device Install (Hardware initiated) - USB\VID_06E0&PID_F104\5&711e76&0&5]

>>>  Section start 2019/01/30 16:03:15.745

     dvi: {Build Driver List} 16:03:15.767

     dvi:      Searching for hardware ID(s):

     dvi:           usb\vid_06e0&pid_f104&rev_0100

     dvi:           usb\vid_06e0&pid_f104

     dvi:      Searching for compatible ID(s):

     dvi:           usb\class_ff&subclass_ff&prot_ff

     dvi:           usb\class_ff&subclass_ff

     dvi:           usb\class_ff

     dvi:      Created Driver Node:

     dvi:           HardwareID   - USB\Vid_06e0&Pid_f104

     dvi:           InfName      - C:\WINDOWS\System32\DriverStore\FileRepository\mdmcpq.inf_amd64_81d387a9bb4a4cc8\mdmcpq.inf

     dvi:           DevDesc      - MultiTech MT5634ZBA-USB 56K Modem

     dvi:           Section      - Modem14.NT

     dvi:           Rank         - 0x00ff0001

     dvi:           Signer Score - INBOX

     dvi:           DrvDate      - 03/09/2000

     dvi:           Version      - 10.0.17134.1

     dvi: {Build Driver List - exit(0x00000000)} 16:03:15.785

     dvi: {DIF_SELECTBESTCOMPATDRV} 16:03:15.785

     dvi:      Using exported function 'ClassInstall32' in module 'C:\WINDOWS\system32\mdminst.dll'.

     dvi:      Class installer == mdminst.dll,ClassInstall32

     dvi:      Class installer: Enter 16:03:15.793

     dvi:      Class installer: Exit

     dvi:      Default installer: Enter 16:03:15.794

     dvi:           {Select Best Driver}

     dvi:                Class GUID of device changed to: {4d36e96d-e325-11ce-bfc1-08002be10318}.

     dvi:                {DIF_DESTROYPRIVATEDATA} 16:03:15.795

     dvi:                     Class installer: Enter 16:03:15.795

     dvi:                     Class installer: Exit

     dvi:                {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 16:03:15.796

     dvi:                Selected Driver:

     dvi:                     Description - MultiTech MT5634ZBA-USB 56K Modem

     dvi:                     InfFile     - c:\windows\system32\driverstore\filerepository\mdmcpq.inf_amd64_81d387a9bb4a4cc8\mdmcpq.inf

     dvi:                     Section     - Modem14

     dvi:           {Select Best Driver - exit(0x00000000)}

     dvi:      Default installer: Exit

     dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 16:03:15.798

     dvi: {Core Device Install} 16:03:15.798

     dvi:      {Install Device - USB\VID_06E0&PID_F104\5&711E76&0&5} 16:03:15.800

     dvi:           Device Status: 0x01806400, Problem: 0x1 (0xc0000493)

     dvi:           Parent device: USB\ROOT_HUB30\4&38e6ef67&0&0

     dvi:           {Configure Device - USB\VID_06E0&PID_F104\5&711E76&0&5} 16:03:15.804

     dvi:                Device Status: 0x01806400, Problem: 0x1 (0xc0000493)

     dvi:                Parent device: USB\ROOT_HUB30\4&38e6ef67&0&0

!    dvi:                Device class {4d36e96d-e325-11ce-bfc1-08002be10318} is not configurable.

     dvi:           {Configure Device - exit(0x00000032)} 16:03:15.805

     dvi:           {DIF_ALLOW_INSTALL} 16:03:15.806

     dvi:                Using exported function 'ClassInstall32' in module 'C:\WINDOWS\system32\mdminst.dll'.

     dvi:                Class installer == mdminst.dll,ClassInstall32

     dvi:                Class installer: Enter 16:03:15.807

     dvi:                Class installer: Exit

     dvi:                Default installer: Enter 16:03:15.808

     dvi:                Default installer: Exit

     dvi:           {DIF_ALLOW_INSTALL - exit(0xe000020e)} 16:03:15.808

     dvi:           {DIF_INSTALLDEVICEFILES} 16:03:15.809

     dvi:                Class installer: Enter 16:03:15.810

     dvi:                Class installer: Exit

     dvi:           {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 16:03:15.814

     flq:           File 'C:\WINDOWS\system32\DRIVERS\usbser.sys' pruned from copy.

     dvi:           {DIF_REGISTER_COINSTALLERS} 16:03:15.846

     dvi:                Reset Device: Resetting device configuration. 16:03:15.847

     dvi:                Reset Device: Resetting device configuration completed. 16:03:15.848

     dvi:                Class installer: Enter 16:03:15.848

     dvi:                Class installer: Exit

     dvi:                Default installer: Enter 16:03:15.848

     inf:                     {Install from INF Section - Modem14.NT.CoInstallers} 16:03:15.849

     inf:                          Flags         - 0x001001ee

     inf:                     {Install from INF Section - exit(0x00000000)} 16:03:15.850

     dvi:                Default installer: Exit

     dvi:           {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 16:03:15.851

     dvi:           {DIF_INSTALLINTERFACES} 16:03:15.851

     dvi:                Class installer: Enter 16:03:15.852

     dvi:                Class installer: Exit

     dvi:                Default installer: Enter 16:03:15.852

     dvi:                Default installer: Exit

     dvi:           {DIF_INSTALLINTERFACES - exit(0x00000000)} 16:03:15.853

     dvi:           {DIF_INSTALLDEVICE} 16:03:15.853

     dvi:                Class installer: Enter 16:03:15.854

     dvi:                     {Install DEVICE}

     inf:                          {Install from INF Section - Modem14.NT} 16:03:15.860

     inf:                               Flags         - 0x001005ee

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.958

     inf:                          {Install from INF Section - UsbSerial_ModemFilter_Install} 16:03:15.958

     inf:                               Flags         - 0x001005ee

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.959

     inf:                          {Install from INF Section - Modem14.NT.Hw} 16:03:15.960

     inf:                               Flags         - 0x00100004

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.961

     inf:                          {Install from INF Section - UsbSerial_ModemFilter_Install.Hw} 16:03:15.961

     inf:                               Flags         - 0x00100004

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.962

     dvi:                          {Writing Device Properties}

     dvi:                               Strong Name=mdmcpq.inf:39e4895befabc47d:Modem14:10.0.17134.1:usb\vid_06e0&pid_f104

     dvi:                          {Writing Device Properties - Complete}

     inf:                          AddService=usbser,,UsbSerial_Service_Install,UsbSerial_EventLog_Install  (usbser.inf line 106)

     dvi:                          Add Service: Modified existing service 'usbser'.

     inf:                          {Install from INF Section - UsbSerial_Service_Install} 16:03:15.970

     inf:                               Flags         - 0x00100004

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.970

     inf:                          {Install from INF Section - UsbSerial_EventLog_Install} 16:03:15.971

     inf:                               Flags         - 0x00100004

     inf:                          {Install from INF Section - exit(0x00000000)} 16:03:15.972

     dvi:                     {Install DEVICE exit (0x00000000)}

     dvi:                     Install Device: Configuring device class. 16:03:15.975

     dvi:                     Install Device: Configuring device class completed. 16:03:15.976

     dvi:                     Device Status: 0x01806400, Problem: 0x1 (0xc0000493)

     dvi:                     Install Device: Starting device 'USB\VID_06E0&PID_F104\5&711E76&0&5'. 16:03:15.977

     dvi:                     Install Device: Starting device completed. 16:03:20.459

!!!  dvi:                     Device not started: Device has problem: 0x0a (CM_PROB_FAILED_START), problem status: 0xc000000e.

     dvi:                Class installer: Exit

     dvi:           {DIF_INSTALLDEVICE - exit(0x00000000)} 16:03:20.519

     dvi:           Device Status: 0x01806400, Problem: 0xa

     dvi:           {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 16:03:20.520

     dvi:                Class installer: Enter 16:03:20.521

     dvi:                Class installer: Exit

     dvi:                Default installer: Enter 16:03:20.521

     dvi:                Default installer: Exit

     dvi:           {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 16:03:20.522

     dvi:      {Install Device - exit(0x00000000)} 16:03:20.524

     dvi: {Core Device Install - exit(0x00000000)} 16:03:20.524

     dvi: {DIF_DESTROYPRIVATEDATA} 16:03:20.524

     dvi:      Class installer: Enter 16:03:20.525

     dvi:      Class installer: Exit

     dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 16:03:20.526

<<<  Section end 2019/01/30 16:03:20.535

<<<  [Exit status: SUCCESS]

So the whole installation process succeeds but the driver fails to start the device.  I then found:

https://pete.akeo.ie/2011/03/troubleshooting-usb-device-development.html

Which details what the driver is trying to do:

"CM_PROB_FAILED_START means that your driver loaded, passed through DriverEntry, passed through AddDevice, and then failed during IRP_MN_START_DEVICE.

In layman's terms, this means that the issue occurs during the USB transfers that Windows issues with the device, after the driver has been setup and the device instance has been (re)created."

So it would appear that Windows 10 did a total re-write on "usbser.sys":

• https://technet.microsoft.com/en-us/dn707976(v=vs.90)
• https://blogs.msdn.microsoft.com/usbcoreblog/2015/07/29/what-is-new-with-serial-in-windows-10/

and in the process managed to change the way the device initialisation worked thus breaking loads of USB Communication Device Class (CDC) components.  Clearly whatever the driver is doing now it is not operating in a backward compatible manner and clearly Microsoft have not tested their own "in-box" supplied "INF" files on the devices that are clearly identified by the "Device-IDs" that identify the component.

I managed to find a not very satisfactory workaround for my laptop using a USB to Serial Cable and a really old Multitech MT5600ZDX serial modem, which worked perfectly;  this did at least allow me to get the "Windows Fax and Scan" working.  It would clearly be advantageous if Microsoft drivers actually produced a human readable description of the Hex error codes emitted by the drivers and wrote them to either the "Event Log" or "setupapi.dev.log".  It is anyone's guess what "problem status: 0xc000000e" actually means and why the new driver felt it needed to fail the device when Windows 7 allows the device to start; IMHO this type of behaviour is not progress it is just lack of testing in Windows 10 to ensure that code re-writes don't break things and some form of regression testing is carried out.

Hi Dave,

please check system files by running SFC /scannow command, please tell the result.

And please try to run setup in compatibility mode with Windows 7 or Windows XP.

Hi Igor,

Many thanks for taking the time to respond, the results of the "sfc /scannow" are:

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

There is no "setup" since this is a USB MODEM it is auto-detected in Device Manager using PnP and the INF file selection from the identified Device ID then attempts to install the Microsoft components it identifies, but this is failing.  The only other option that I have also tried was to use:

Action -> Add legacy hardware

If I select "Search for and install the hardware automatically (Recommended)" the driver it chooses is the same components as the PnP, and if I try "Install the hardware that I manually select from a list (Advanced)" using "Don't detect my modem; I will select it from a list" I can select the Manufacturer as "MultiTech Systems", but my modem is not listed I only see:

MultiTech Systems MT5600BA

MultiTech Systems MT5600BA V92

MultiTech Systems MT5600BL

MultiTech Systems MT5600BR

MultiTech Systems MT5600DSVD

MultiTech Systems MT5600DSVD2

MultiTech Systems MT5600ZDX

MultiTech Systems MT5600ZDXV

MultiTech Systems MT5656ZDX

MultiTech Systems MT5656ZDXV

MultiTech Systems Systems Socket Modem

The issue here is what does:

Description: Device USB\VID_06E0&PID_F104\5&711e76&0&5 was not migrated due to partial or ambiguous match.

actually mean in the context of a Microsoft supplied PnP INF file?

Hi Dave,

please check system files by running SFC /scannow command, please tell the result.

And please try to run setup in compatibility mode with Windows 7 or Windows XP.

Seems there are needed not general but specific drivers. Please search the driver by "VID_06E0&PID_F104 driver" search request.

The MultiTech MODEMs only ever used the Windows Drivers no matter which version of the operating system they ran on.  The difference was that in Windows 7 Mutitech provided a specific setup information (.INF) and a security catalogue (.CAT) file that could be used to provide the specific detail.  Very old MODEMs were connected through a serial port and therefore it was only the registry specifics of the MODEM personality and capability that needed to be provided.

In Windows 10 Microsoft provide "mdmcpq.inf" which explicitly matched the Device ID of the MODEM as can be seen from the snippet relating to this device:

; Windows Modem Setup File

; Copyright (c) Microsoft Corporation.  All rights reserved.

; Manufacturers: Compaq, DEC, Multitech, Aztech, GVC. Includes USB (Lucent/Compaq/Multitech/Creative/Abocom) support

[Version]

Signature="$WINDOWS NT$"

Class=Modem

ClassGUID={4D36E96D-E325-11CE-BFC1-08002BE10318}

Provider=%MSFT%

DriverVer = 06/21/2006,10.0.17134.1

[Manufacturer]

..

%Multitech%  = MultiTech,NTamd64

..

[Multitech.NTamd64]

%Modem13% = Modem13, SERENUM\MTS00B0

%Modem14% = Modem14, USB\Vid_06e0&Pid_f104

..

..

[Modem14.NT]

DriverVer=03/09/2000

Include=mdmgl006.inf,usbser.inf

Needs = UsbSerial_ModemFilter_Install

AddReg=All, MfgCompaq, Modem14.AddReg, USB, EXTERNAL, CPQ.Resp,LucentUSB.TerseResp,MDMGL006.56KResponses

..

..

[Strings]

MSFT       = "Microsoft"

GVC        = "GVC"

Compaq     = "Compaq"

AztechLabs = "Aztech"

Diamond    = "Diamond"

Creative   = "Creative"

Abocom      = "Abocom"

Multitech  = "MultiTech Systems"

Metricom = "Metricom"

Bestdata = "Best Data"

Zoom     = "Zoom"

Conexant = "Conexant"

CompanyName = "Conexant"

ProductName = "USB Modem"

..

..

Modem14 = "MultiTech MT5634ZBA-USB 56K Modem"

..

..

[All]

HKR****EnumPropPages"

[MfgCompaq]

HKR**** "AT<cr>"

HKR, Monitor, 1,, "ATS0=0<cr>"

HKR, Monitor, 2,, "None"

HKR, Hangup, 1,, "ATH<cr>"

HKR, Answer, 1,, "ATA<cr>"

HKR,, Reset,, "ATZ<cr>"

HKR, Settings, Prefix,, "AT"

HKR, Settings, Terminator,, "<cr>"

HKR**** "L3"

HKR**** "\Q0"

HKR**** "\N4"

HKR**** "N0"

HKR**** "X3"

HKR, Settings, CallSetupFailTimer,, "S7=<#>"

HKR, Settings, InactivityTimeout,, "S30=<#>"

..

..

[Modem14.AddReg]

HKR**** "AT &F E0 &C1 &D2 V1 S0=0<cr>"

HKR**** "ATHE1<cr>"

HKR,, Reset,, "AT&F<cr>"

HKR**** "\N1"

HKR**** "B1B16"

..

..

etc.

All the base links to the associated drivers to provide the USB to serial interface to the driver are defined in "usbser.inf".

Whilst there are plenty of extremely dubious sites out on the Internet offering to provide device drivers many require installing some potentially dangerous executable to download software.  As many of these sites just spread virus software I stay well clear and only take information from either the manufacturer or Microsoft.

As I mentioned earlier the only available ".INF" and ".CAT" files available from Multitech were for Windows 7 and cannot be used on Windows 10.  I am starting to suspect that there is a bug in one or more of the Microsoft ".INF" files in this installation tree that is causing the error, but the error message is not documented on any Microsoft site I've searched to explain exactly what has failed that causes the error:

Device USB\VID_06E0&PID_F104\5&711e76&0&5 was not migrated due to partial or ambiguous match

I've spent quite some time looking at:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/

but have yet to come up with anything specific.

BTW. There are loads of references on the Internet to this type of message and loads of issues pertaining to MODEMS on Windows 10, just see the following URLs:

• https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/modem-wave-driver-issue/ddae9211-6ffd-45cc-bf03-0b8791bd438c?auth=1
• https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/win-10-ver-1511-breaks-voice-modems/5ad002d5-25b4-4d3f-ae5a-895a45addd51
• https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/56k-modem-missing-unimodem-audio-device-after/7a53af94-21fe-4352-80ec-b27fb3dc5886?page=16
• https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/modem-wave-driver-issue/ddae9211-6ffd-45cc-bf03-0b8791bd438c?auth=1

Seems there are needed not general but specific drivers. Please search the driver by "VID_06E0&PID_F104 driver" search request.