MTP problem

[shloomberg]

I bought the Sansa E270 one week ago. I've been desperately trying to transfer a playlist in MSC mode without success. I tried using MTP mode, but my computer won't recognize the device in this mode. The device appears as not recognized in Device Manager, and when I try to reinstall it I get an error like this: "Bad INF file, cannot complete installation."

I've tried just about anything to resolve it, but nothing worked. I couldn't find a message here with a solution for this problem. Can anyone please help me?

Thanks,
shir

[CrowdAds]

[Lifter59]

What OS are you using on your PC and what version of WMP do you have installed?

[shloomberg]

XP SP2, WMP 11
I have installed the Hebrew firmware, could it be related?

[Enigmatic_Mark]

-If the player is set to Auto Detect, but Windows sees it as a MSC device, here’s what to do: open Device Manager, find the USB Mass Storage Device for the player, right-click on it and choose Update Driver. After that, check if it shows up as an MTP device.

-Try to add the device manually. Plug the player in while it’s set to MTP mode. Open Device Manager, and Add Hardware. Tell it that you have already connected the hardware. In the list, choose “Add a new hardware device” at the bottom. Choose “Install the hardware that I manually select from a list.” Choose Portable Devices, then MTP device.

-Try the instructions at the following link (registry hack):
http://support.microsoft.com/kb/911091/EN-US

-Format using Windows Media Player (only works if MTP mode is already showing up, but songs won’t transfer):
Version 10: go to the Sync tab, click on the “format storage media” button.
Version 11: click the down arrow below the Sync tab, Device options, Format

[RichardS-UK]

Originally Posted by shloomberg

The device appears as not recognized in Device Manager, and when I try to reinstall it I get an error like this: "Bad INF file, cannot complete installation."

I've posted about .inf files before but this solution is not always successful.

For some reason the Sansa in MTP mode is sometimes not automatically recognised by XP which cannot then find the correct .inf file and therefore cannot load the two MTP drivers, wpdusb.sys and wudfrd.sys, both of which should be present in the windows\system32 folder if XP SP2 and WMP10 or WMP11 have installed correctly.

The primary .inf file needed to load the MTP drivers is called wpdmtphw.inf (I assume this stands for Windows Portable Device MTP Hardware). This .inf file actually calls another .inf file - wpdmtp.inf - which actually loads the drivers.

I have attached a zipped wpdmtphw.inf to this post in which I have manually added the Sansa hardware id. You can open this .inf file in Notepad if you wish to view it.

Find your original wpdmtphw.inf in c:\windows\inf and rename it wpdmtphw.original or something similar so you can always go back to it. Unzip the attached .inf file and copy it to c:\windows\inf and let Windows try to install the Sansa again. This time it should find the .inf file and install the drivers automatically but you can also browse to c:\windows\inf if prompted to do so. After connecting the Sansa give Windows plenty of time to install it - 10 or 15 minutes if necessary!

Trying this should not harm your system (provided you know what you are doing) and will not affect MSC mode which is usually recognised without a problem. However, on one of my PCs, although the MTP drivers now load with the modified .inf file, the MTP Sansa shows in Device Manager with a yellow exclamation mark so I suspect that XP's failure to recognise the hardware id in this case is symptomatic of a more fundamental problem than the .inf file issue. However, you have nothing to lose and it may work for you!

Richard

[shloomberg]

Didn't work. =\

But I did manage to make a playlist after I removed the Hebrew firmware, so for now it's good enough.

Thanks though!

[wizard1]

The files wpdusb.sys and wudfrd.sys are not in my windows\system32 folder for some reason I don't know.Could you upload them as well so that I can put them into my system 32 folder?
Thanks..

[RichardS-UK]

Originally Posted by wizard1

The files wpdusb.sys and wudfrd.sys are not in my windows\system32 folder for some reason I don't know.Could you upload them as well so that I can put them into my system 32 folder?
Thanks..

Sorry - I should have put the full path to the MTP drivers in case you didn't do a search. The full path is c:\windows\system32\drivers so you probably will have the drivers in there if you have WMP installed. Just in case I've attached them both to this post anyway.

Good luck

[shloomberg]

After looking around a bit I found out that the "wudfrd.sys" file was missing, so I added it to the right folder.
The error message is now changed to something like this: "Windows cannot load the driver for this hardware. The driver may be missing or corrupt. (code 39)"
Also, the error message keeps repeating itself endlessly, unlike the last message.

[wizard1]

Ok thanks, I'll try to see if that works

[RichardS-UK]

Originally Posted by shloomberg

After looking around a bit I found out that the "wudfrd.sys" file was missing, so I added it to the right folder.
The error message is now changed to something like this: "Windows cannot load the driver for this hardware. The driver may be missing or corrupt. (code 39)"
Also, the error message keeps repeating itself endlessly, unlike the last message.

Unfortunately it seems to be the case that even after applying all the "fixes" to be found on this forum and many others on the web, some PCs will simply not recognise an MTP device. I think that this is a hardware/BIOS issue connected with the User Mode Driver Framework and even a reinstall of XP will not fix it although I would be pleased if someone has tried this and wishes to confirm/deny?

If you have worked your way through all the "fixes" and are using the modified wpdmtphw.inf file, have SP2 and WMP10 or 11 installed, and have the two MTP drivers in the correct folder and MTP still doesn't work then I have come to the conclusion that, until Microsoft provides a fix of some kind, you are going to have to use MSC mode.

schloolmberg - if you have both the drivers in the system32\drivers folder and have the modified .inf file in the windows\inf folder there should be a good chance that the drivers will load although I suspect that your e200 will still have the dreaded yellow exclamation mark in Device Manager.

However, I just noticed that there is another User Mode Framework driver in system32\drivers called wudfpf.sys. This has exactly the same date and version number as wudfrd.sys so it is likely that this driver also has to be present for the MTP User Mode Driver Framework to function even though it is not loaded by the .inf file.

You could also check in Control Panel - Administrative Tools - Services that "Windows Driver Foundation - User-Mode Driver Framework" (WudfSvc) has started. Even if it has started there is no guarantee that your e200 will be recognised. If it hasn't started you could try and start it manually from within the Sevices window.

I've attached another modified .inf file and both the MTP drivers plus the "new" one from a different PC to this post just in case something got corrupted first time around.

Better luck this time!

[shloomberg]

Originally Posted by RichardS-UK

I've attached another modified .inf file and both the MTP drivers plus the "new" one from a different PC to this post just in case something got corrupted first time around.

Better luck this time!

can you reattach? :P

[RichardS-UK]

Originally Posted by shloomberg

can you reattach? :P

Good grief - they were attached yesterday! I'll try again!

[RichardS-UK]

Originally Posted by RichardS-UK

Good grief - they were attached yesterday! I'll try again!

Right - I've downloaded them myself and checked the archive - this time I'm 1000% certain!

[shloomberg]

First of all, thanks a lot for your help!

I think I almost succeeded in installing it with the files you provided.
Of course, there is still a problem: after installing the player, it asks me to reboot in order to complete the installation, but on startup it repeats the very same installation process, asking me to reboot again and again and again...

This problem occurred on my friend's PC with his e270 as well, although one day it suddenly stopped happening, just like that. I hope I'll get the same results as he did...

[RichardS-UK]

Originally Posted by shloomberg

I think I almost succeeded in installing it with the files you provided.
Of course, there is still a problem: after installing the player, it asks me to reboot in order to complete the installation, but on startup it repeats the very same installation process, asking me to reboot again and again and again...

This problem occurred on my friend's PC with his e270 as well, although one day it suddenly stopped happening, just like that. I hope I'll get the same results as he did...

Glad to help a little but this is what my youngest son's PC does and it has never succeeded in fully recognising the player although it's fine in MSC mode. If you look in Device Manager I bet you'll see the yellow exclamation mark. I can't find any solution to this although you've inspired me to have another try! I've updated the BIOS and the motherboard drivers. If somebody out there has the solution they should post it here and then email Bill Gates and ask for a reward!!

[shloomberg]

Originally Posted by RichardS-UK

Glad to help a little but this is what my youngest son's PC does and it has never succeeded in fully recognising the player although it's fine in MSC mode. If you look in Device Manager I bet you'll see the yellow exclamation mark. I can't find any solution to this although you've inspired me to have another try! I've updated the BIOS and the motherboard drivers. If somebody out there has the solution they should post it here and then email Bill Gates and ask for a reward!!

SanDisk's Israeli technical support told us to connect another electricity source (such as a USB hub with power supply) to the computer, but for some reason I don't think that'll do the trick...

I'm really starting to hate Microsoft...

[RichardS-UK]

Originally Posted by RichardS-UK

Glad to help a little but this is what my youngest son's PC does and it has never succeeded in fully recognising the player although it's fine in MSC mode. If you look in Device Manager I bet you'll see the yellow exclamation mark. I can't find any solution to this although you've inspired me to have another try! I've updated the BIOS and the motherboard drivers. If somebody out there has the solution they should post it here and then email Bill Gates and ask for a reward!!

After another trawl through the web it seems that some motherboard USB chipsets do not work properly with MTP devices. My "problem" motherboard is an MSI 6380E with a VIA 8235/8237 USB2 chipset but I have read that some SIS chipsets also have problems.

I tried a different approach and installed a D-Link DU-520 Rev A1 USB2 PCI card which I had lying around. At first I thought that this had solved the problem - the Sansa was now recognised instantly and the correct drivers were found automatically using the original un-modified .inf file. Unfortunately, although the process was very smooth and very quick (unlike when using the VIA USB ports), I still ended up with the dreaded yellow exclamation mark and the new error message "The device cannot start (Code 10)"!

I've tried removing and re-installing the Sansa and the USB drivers as advised by the MS Troubleshooter but cannot get past this error message. It looks like the D-Link USB hardware has the problem as the VIA USB hardware but a little less so!

[norman_himself]

I tried around a bit for myself and I found a solution!
The problem were the .dll files belonging to MTP.
I created an selfextracting archive, which you only have to extract into you "WINDOWS" folder an everything should work allright!
But this only solves the problem with the instal. It detects the player as an MTP-Device but it doesn't recognize it as a Sansa e200, so this prob still has to be fixed, but I think this has something to do with the .inf file. If someone could do that it would be really nice!

Please give me feedback if it works for you.

Norman

[RichardS-UK]

Originally Posted by norman_himself

I tried around a bit for myself and I found a solution!
The problem were the .dll files belonging to MTP.
I created an selfextracting archive, which you only have to extract into you "WINDOWS" folder an everything should work allright!
But this only solves the problem with the instal. It detects the player as an MTP-Device but it doesn't recognize it as a Sansa e200, so this prob still has to be fixed, but I think this has something to do with the .inf file. If someone could do that it would be really nice!

Please give me feedback if it works for you.

Norman

Norman - where did you get the two MTP inf files from? They are very different to the MTP inf files on any of my PCs and look like they came from a German installation. I will try them later tonight and probably change the German to English as words like "Gerät" and "fähiger" in "My Computer" will look a bit odd!

Richard