D
DaveArdron
Occasionally I need to Fax documents to people who refuse to accept any other form of electronic communication (e.g. US Banks). I therefore tried to install my old MT5634ZBA-USB Fax MODEM onto my Windows 10 (1803 17134.523) laptop.
The Device Manager selects "mdmcpq.inf" as the required installation source and tries to install two Microsoft Windows 10 drivers:
1) c:\Windows\system32\drivers\modem.sys - (10.0.17134.1 - 12/04/2018 00:34)
2) c:\windows\system32\drivers\usbser.sys - (10.0.17134.1 - 12/04/2018 00:33)
The installation correctly recognises the MODEM type from the Vendor ID, but fails with:
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 30/01/2019 16:03:20
Event ID: 20001
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Driver Management concluded the process to install driver mdmcpq.inf_amd64_81d387a9bb4a4cc8 for Device Instance ID USB\VID_06E0&PID_F104\5&711E76&0&5 with the following status: 0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:20.523715400Z" />
<EventRecordID>18869</EventRecordID>
<Correlation />
<Execution ProcessID="4332" ThreadID="1576" />
<Channel>System</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>mdmcpq.inf_amd64_81d387a9bb4a4cc8</DriverName>
<DriverVersion>10.0.17134.1</DriverVersion>
<DriverProvider>Microsoft</DriverProvider>
<DeviceInstanceID>USB\VID_06E0&PID_F104\5&711E76&0&5</DeviceInstanceID>
<SetupClass>{4D36E96D-E325-11CE-BFC1-08002BE10318}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>false</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>MultiTech MT5634ZBA-USB 56K Modem</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 30/01/2019 16:03:15
Event ID: 20003
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Driver Management has concluded the process to add Service usbser for Device Instance ID USB\VID_06E0&PID_F104\5&711E76&0&5 with the following status: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20003</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.974075400Z" />
<EventRecordID>18868</EventRecordID>
<Correlation />
<Execution ProcessID="4332" ThreadID="1576" />
<Channel>System</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<ServiceName>usbser</ServiceName>
<DriverFileName>\SystemRoot\system32\DRIVERS\usbser.sys</DriverFileName>
<DeviceInstanceID>USB\VID_06E0&PID_F104\5&711E76&0&5</DeviceInstanceID>
<PrimaryService>false</PrimaryService>
<UpdateService>true</UpdateService>
<AddServiceStatus>0</AddServiceStatus>
</AddServiceID>
</UserData>
</Event>
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 30/01/2019 16:03:15
Event ID: 442
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Device USB\VID_06E0&PID_F104\5&711e76&0&5 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0781&PID_5571\4C532000021109116010
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(5)
Migration Rank: 0xF000FFFFFFFF0033
Present: false
Status: 0xC0000719
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>442</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.848009000Z" />
<EventRecordID>794</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5800" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_06E0&PID_F104\5&711e76&0&5</Data>
<Data Name="LastDeviceInstanceId">USB\VID_0781&PID_5571\4C532000021109116010</Data>
<Data Name="ClassGuid">{36FC9E60-C465-11CF-8056-444553540000}</Data>
<Data Name="LocationPath">PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(5)</Data>
<Data Name="MigrationRank">0xf000ffffffff0033</Data>
<Data Name="Present">false</Data>
<Data Name="Status">0xc0000719</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 30/01/2019 16:03:15
Event ID: 430
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Device USB\VID_06E0&PID_F104\5&711e76&0&5 requires further installation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>430</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.713090500Z" />
<EventRecordID>793</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="404" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_06E0&PID_F104\5&711e76&0&5</Data>
</EventData>
</Event>
I have used the Windows 10 troubleshooter, which claimed to have fixed the problem, but it failed to correct the issue.
The data from "System Information" shows:
Name MultiTech MT5634ZBA-USB 56K Modem
Description MultiTech MT5634ZBA-USB 56K Modem
Device ID USB\VID_06E0&PID_F104\5&711E76&0&5
Device Type External Modem
Attached To COM5
Answer Mode Not Available
PNP Device ID USB\VID_06E0&PID_F104\5&711E76&0&5
Provider Name Microsoft
Modem INF Path mdmcpq.inf
Modem INF Section Modem14
Blind Off X4
Blind On X3
Compression Off %C0
Compression On %C1
Error Control Forced \N4
Error Control Off \N1
Error Control On \N3
Flow Control Hard &K3
Flow Control Off &K0
Flow Control Soft &K4
DCB 
Default <
Inactivity Timeout 0
Modulation Bell B1B16
Modulation CCITT B0B15
Prefix AT
Pulse P
Reset AT&F<cr>
Responses Key Name MultiTech MT5634ZBA-USB 56K Modem::MultiTech Systems::Microsoft
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L0
Speaker Volume Med L2
String Format Not Available
Terminator <cr>
Tone T
Driver c:\windows\system32\drivers\modem.sys (10.0.17134.1, 41.50 KB (42,496 bytes), 11/04/2018 23:34)
So what is going on here and why won't the core Windows 10 INF files and drivers install properly?
I have also reached out to Multitech, but since all the components in use here are core Windows 10 and Multitech only needed to supply a specific INF file for Windows 7 I'm not hopeful they will help.
Continue reading...
The Device Manager selects "mdmcpq.inf" as the required installation source and tries to install two Microsoft Windows 10 drivers:
1) c:\Windows\system32\drivers\modem.sys - (10.0.17134.1 - 12/04/2018 00:34)
2) c:\windows\system32\drivers\usbser.sys - (10.0.17134.1 - 12/04/2018 00:33)
The installation correctly recognises the MODEM type from the Vendor ID, but fails with:
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 30/01/2019 16:03:20
Event ID: 20001
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Driver Management concluded the process to install driver mdmcpq.inf_amd64_81d387a9bb4a4cc8 for Device Instance ID USB\VID_06E0&PID_F104\5&711E76&0&5 with the following status: 0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:20.523715400Z" />
<EventRecordID>18869</EventRecordID>
<Correlation />
<Execution ProcessID="4332" ThreadID="1576" />
<Channel>System</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>mdmcpq.inf_amd64_81d387a9bb4a4cc8</DriverName>
<DriverVersion>10.0.17134.1</DriverVersion>
<DriverProvider>Microsoft</DriverProvider>
<DeviceInstanceID>USB\VID_06E0&PID_F104\5&711E76&0&5</DeviceInstanceID>
<SetupClass>{4D36E96D-E325-11CE-BFC1-08002BE10318}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>false</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>MultiTech MT5634ZBA-USB 56K Modem</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 30/01/2019 16:03:15
Event ID: 20003
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Driver Management has concluded the process to add Service usbser for Device Instance ID USB\VID_06E0&PID_F104\5&711E76&0&5 with the following status: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20003</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.974075400Z" />
<EventRecordID>18868</EventRecordID>
<Correlation />
<Execution ProcessID="4332" ThreadID="1576" />
<Channel>System</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<ServiceName>usbser</ServiceName>
<DriverFileName>\SystemRoot\system32\DRIVERS\usbser.sys</DriverFileName>
<DeviceInstanceID>USB\VID_06E0&PID_F104\5&711E76&0&5</DeviceInstanceID>
<PrimaryService>false</PrimaryService>
<UpdateService>true</UpdateService>
<AddServiceStatus>0</AddServiceStatus>
</AddServiceID>
</UserData>
</Event>
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 30/01/2019 16:03:15
Event ID: 442
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Device USB\VID_06E0&PID_F104\5&711e76&0&5 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0781&PID_5571\4C532000021109116010
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(5)
Migration Rank: 0xF000FFFFFFFF0033
Present: false
Status: 0xC0000719
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>442</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.848009000Z" />
<EventRecordID>794</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5800" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_06E0&PID_F104\5&711e76&0&5</Data>
<Data Name="LastDeviceInstanceId">USB\VID_0781&PID_5571\4C532000021109116010</Data>
<Data Name="ClassGuid">{36FC9E60-C465-11CF-8056-444553540000}</Data>
<Data Name="LocationPath">PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(5)</Data>
<Data Name="MigrationRank">0xf000ffffffff0033</Data>
<Data Name="Present">false</Data>
<Data Name="Status">0xc0000719</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 30/01/2019 16:03:15
Event ID: 430
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxxxx
Description:
Device USB\VID_06E0&PID_F104\5&711e76&0&5 requires further installation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>430</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-01-30T16:03:15.713090500Z" />
<EventRecordID>793</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="404" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>dardron</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_06E0&PID_F104\5&711e76&0&5</Data>
</EventData>
</Event>
I have used the Windows 10 troubleshooter, which claimed to have fixed the problem, but it failed to correct the issue.
The data from "System Information" shows:
Name MultiTech MT5634ZBA-USB 56K Modem
Description MultiTech MT5634ZBA-USB 56K Modem
Device ID USB\VID_06E0&PID_F104\5&711E76&0&5
Device Type External Modem
Attached To COM5
Answer Mode Not Available
PNP Device ID USB\VID_06E0&PID_F104\5&711E76&0&5
Provider Name Microsoft
Modem INF Path mdmcpq.inf
Modem INF Section Modem14
Blind Off X4
Blind On X3
Compression Off %C0
Compression On %C1
Error Control Forced \N4
Error Control Off \N1
Error Control On \N3
Flow Control Hard &K3
Flow Control Off &K0
Flow Control Soft &K4
DCB 
Default <
Inactivity Timeout 0
Modulation Bell B1B16
Modulation CCITT B0B15
Prefix AT
Pulse P
Reset AT&F<cr>
Responses Key Name MultiTech MT5634ZBA-USB 56K Modem::MultiTech Systems::Microsoft
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L0
Speaker Volume Med L2
String Format Not Available
Terminator <cr>
Tone T
Driver c:\windows\system32\drivers\modem.sys (10.0.17134.1, 41.50 KB (42,496 bytes), 11/04/2018 23:34)
So what is going on here and why won't the core Windows 10 INF files and drivers install properly?
I have also reached out to Multitech, but since all the components in use here are core Windows 10 and Multitech only needed to supply a specific INF file for Windows 7 I'm not hopeful they will help.
Continue reading...