• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

MTP USB Device failed to installed (event log inside)


K33k00

New Member
Posts
5
#1
Hi, i am having trouble connecting my camera to my PC. It works perfectly on another PC running windows 8.1 pro the same as mine. I open device manager and my device is listed under other devices as canon digital camera, though it has an exclamation mark on it.

In the properties under the general tab I see this

"The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver."

I have tried un-installing the device, rebooting my machine and downloading the drivers from canon (it's an 1100D).

i have tired copying the files that show in the events tab on the other pc and manually install them but I get the following message "Windows encountered a Problem installing the driver for you device, MTP USB Device". Now something that seems weird to me is that my phone has also stopped working as an MTP device though there is no obvious driver issues with it.

Below is an event log from my pc relating to the problem

Code:
Log Name:      Microsoft-Windows-Kernel-PnP/ConfigurationSource:        Microsoft-Windows-Kernel-PnP
Date:          26/03/2014 20:51:34
Event ID:      400
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      YT-1300
Description:
Device USB\VID_04A9&PID_3217\5&15c311e1&0&5 was configured.


Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date: 
Driver Version: 
Driver Provider: 
Driver Section: 
Driver Rank: 0x0
Matching Device Id: 
Outranked Drivers: 
Device Updated: false
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>400</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-26T20:51:34.170444600Z" />
    <EventRecordID>593</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="5048" />
    <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
    <Computer>YT-1300</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DeviceInstanceId">USB\VID_04A9&amp;PID_3217\5&amp;15c311e1&amp;0&amp;5</Data>
    <Data Name="DriverName">null</Data>
    <Data Name="ClassGuid">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="DriverDate">
    </Data>
    <Data Name="DriverVersion">
    </Data>
    <Data Name="DriverProvider">
    </Data>
    <Data Name="DriverInbox">false</Data>
    <Data Name="DriverSection">
    </Data>
    <Data Name="DriverRank">0x0</Data>
    <Data Name="MatchingDeviceId">
    </Data>
    <Data Name="OutrankedDrivers">
    </Data>
    <Data Name="DeviceUpdated">false</Data>
    <Data Name="Status">0x0</Data>
  </EventData>
</Event>
I un-installed the camera from the other pc and plugged it back in. it installed successfully and the following are the event logs

Code:
Log Name:      SystemSource:        Microsoft-Windows-UserPnp
Date:          26/03/2014 21:35:52
Event ID:      20001
Task Category: (7005)
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      Kieran-PC
Description:
Driver Management concluded the process to install driver wpdmtp.inf_amd64_5c9850dbde92cf4e\wpdmtp.inf for Device Instance ID USB\VID_04A9&PID_3217\6&273E5B66&0&3 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="2014-03-26T21:35:52.043025100Z" />
    <EventRecordID>21806</EventRecordID>
    <Correlation />
    <Execution ProcessID="4528" ThreadID="2744" />
    <Channel>System</Channel>
    <Computer>Kieran-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
      <DriverName>wpdmtp.inf_amd64_5c9850dbde92cf4e\wpdmtp.inf</DriverName>
      <DriverVersion>6.3.9600.16384</DriverVersion>
      <DriverProvider>Microsoft</DriverProvider>
      <DeviceInstanceID>USB\VID_04A9&amp;PID_3217\6&amp;273E5B66&amp;0&amp;3</DeviceInstanceID>
      <SetupClass>{EEC5AD98-8080-425F-922A-DABF3DE3F69A}</SetupClass>
      <RebootOption>false</RebootOption>
      <UpgradeDevice>false</UpgradeDevice>
      <IsDriverOEM>false</IsDriverOEM>
      <InstallStatus>0x0</InstallStatus>
      <DriverDescription>MTP USB Device</DriverDescription>
    </InstallDeviceID>
  </UserData>
</Event>


Log Name:      System
Source:        Microsoft-Windows-UserPnp
Date:          26/03/2014 21:35:51
Event ID:      20003
Task Category: (7005)
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      Kieran-PC
Description:
Driver Management has concluded the process to add Service WinUsb for Device Instance ID USB\VID_04A9&PID_3217\6&273E5B66&0&3 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="2014-03-26T21:35:51.660933900Z" />
    <EventRecordID>21805</EventRecordID>
    <Correlation />
    <Execution ProcessID="4528" ThreadID="2744" />
    <Channel>System</Channel>
    <Computer>Kieran-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
      <ServiceName>WinUsb</ServiceName>
      <DriverFileName>\SystemRoot\system32\DRIVERS\WinUsb.sys</DriverFileName>
      <DeviceInstanceID>USB\VID_04A9&amp;PID_3217\6&amp;273E5B66&amp;0&amp;3</DeviceInstanceID>
      <PrimaryService>false</PrimaryService>
      <UpdateService>true</UpdateService>
      <AddServiceStatus>0</AddServiceStatus>
    </AddServiceID>
  </UserData>
</Event>


Log Name:      System
Source:        Microsoft-Windows-UserPnp
Date:          26/03/2014 21:35:51
Event ID:      20003
Task Category: (7005)
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      Kieran-PC
Description:
Driver Management has concluded the process to add Service WUDFWpdMtp for Device Instance ID USB\VID_04A9&PID_3217\6&273E5B66&0&3 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="2014-03-26T21:35:51.660933900Z" />
    <EventRecordID>21804</EventRecordID>
    <Correlation />
    <Execution ProcessID="4528" ThreadID="2744" />
    <Channel>System</Channel>
    <Computer>Kieran-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
      <ServiceName>WUDFWpdMtp</ServiceName>
      <DriverFileName>\SystemRoot\system32\DRIVERS\WUDFRd.sys</DriverFileName>
      <DeviceInstanceID>USB\VID_04A9&amp;PID_3217\6&amp;273E5B66&amp;0&amp;3</DeviceInstanceID>
      <PrimaryService>true</PrimaryService>
      <UpdateService>true</UpdateService>
      <AddServiceStatus>0</AddServiceStatus>
    </AddServiceID>
  </UserData>
</Event>
Has anyone come across this before or have any ideas on what i should do.

edit : I have also tried SFC /scannow and drive error checking
edit 2 : i should add these used to work on this PC not so long ago so im confident its not hardware
 
Last edited:

My Computer

System One

  • OS
    K33k00

haroldg

Member
Member
Posts
50
#2
also have this problem.. is there a solution here sir?
 

My Computer

System One

  • OS
    windows 8
    Computer type
    Laptop
    System Manufacturer/Model Number
    ASUS x202e
    CPU
    intel celeron
    Memory
    500
    Graphics Card(s)
    4g ddr
    Browser
    iE, chrome
    Antivirus
    avast

brooksndun

New Member
Posts
884
#3
I'm not on the top of expertise here, but I'll take a stab...


go to the computer that does work with your camera and look for the details like so..

then copy those files into the correct place on the "bad" computer and try hitting "update driver shown in picture 2.. and try to select the "have disk" and the correct file you copied from the "good" computer?

just a try-out situation.. it probably won't work..

driverhelp.JPG



updatedriver.JPG
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    Laptop
    System Manufacturer/Model Number
    Lenovo g750
    CPU
    i5
    Motherboard
    Some Chinese Crap..
    Memory
    8
    Graphics Card(s)
    Nvidia 755
    Antivirus
    Windows Defender
Posts
50
#4
I'm not on the top of expertise here, but I'll take a stab...


go to the computer that does work with your camera and look for the details like so..

then copy those files into the correct place on the "bad" computer and try hitting "update driver shown in picture 2.. and try to select the "have disk" and the correct file you copied from the "good" computer?

just a try-out situation.. it probably won't work..

View attachment 67317



View attachment 67318
@brooksndun

IMHO A warning: I believe that approach won't work. Even worse, it can break a different and totally unrelated driver

The files you see listed in Driver File Details doesn't show you the .cat ("security catalog") file that contains the driver's digital signature. Without the .cat file you'de be trying to install an unsigned driver - and that's problematic.

Re: breaking a different driver in the process.
Windows creates those oemnn.inf files for 3rd party drivers at the time they're installed. The digits assigned the oem file has nothing to do with the driver itself. Rather, the digits are simply the next set of digits available to in assignment sequence. So oem14.inf on one machine will very most likely be for a completely different driver then the oem14.inf file on another machine. IMHO Don't copy and, most certainly, NEVER overwrite an oemnn.inf file unless you know what you're doing.

You will sometimes see copying non oemnn.inf driver files from one machine to another for the case of a driver is installed but just individual driver files are corrupt.
 

My Computer

System One

  • OS
    windows 8.1

brooksndun

New Member
Posts
884
#5
Right, well thanks for the warning, Notice I do say this below - but maybe it wasn't stressed enough..

I'm not on the top of expertise here, but I'll take a stab...
and

just a try-out situation.. it probably won't work..

Usually I tell everyone to use Macrium and make a backup first.. however in this case, I'm at fault for not playing it safe. I do however believe that if something had gone terribly wrong, I have a feeling it's nothing a windows Refresh couldn't fix..
- I also realized this person has at-least 2 computers as they mention in their first post.

But thanks for the heads up and info for the future.
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    Laptop
    System Manufacturer/Model Number
    Lenovo g750
    CPU
    i5
    Motherboard
    Some Chinese Crap..
    Memory
    8
    Graphics Card(s)
    Nvidia 755
    Antivirus
    Windows Defender
Posts
50
#6
also have this problem.. is there a solution here sir?
@haroldg
Don't know if I can help but will have a look at your situation.

What device hardware are you trying to install that gives this error???? Now we're going to recreate the problem and I'll look at the log file
> Delete C:\Windows\inf\setupapi.dev.log
> Plug the device in and wait for the error to occur again
> In device manager, find the device (it will have a yellow icon).Right click select Update Driver. It will probably fail again
> Zip the new file Windows created C:\Windows\inf\setupapi.dev.log and attach to next post
 

My Computer

System One

  • OS
    windows 8.1