can't install MTP driver.. have tried the usual solutions

Hi folks, I’ve been looking for a solution for the last day or two to this problem. New Fuze, works fine on one computer, but on another with xp+sp3 and windows media player 11 installed, the MTP device cannot be installed, I get this error when connecting and trying to install the MTP device driver automatically:

"Cannot Install this Hardware.

There was a problem installing this hardware: MTP Device

An error occurred during the installation of the device.

The filename, directory name, or volume label syntax is incorrect."

I’ve tried installing the MTP Porting Kit that has been suggested by some. Also changed the USB setting in the Fuze to MTP instead of Auto. I use Rhapsody, so I need to use the MTP mode to manage my licenses.  I removed WMP and reinstalled it (it was already version 11).  The OS is not a hacked copy, but an actual one I purchased.

Have you already Installed Rhapsody? If so, Uninstall WMP 11 then reinstal the MTP porting deal from Microsoft. See what happens. It could be the 3 things are conflicting.

I removed WMP11, rebooted, then removed the mtp porting kit, rebooted.  Then installed the mtp porting kit, and yes, rebooted.  Same thing, XP can’t get around the bad filename/volume label/ or whatever.

Message Edited by goldbars on 02-19-2009 07:20 PM

bump – surely someone else has encountered this?

I guess I’ll submit a support request

I know you have tryed a few of these solutions,.   Maybe on this page there is something you haven’t tryed yet.  

http://kb.sandisk.com/cgi-bin/sandisk_en.cfg/php/enduser/std_adp.php?p_faqid=42&p_created=1221328944&p_sid=BtncpYqj&p_brand=sansa

There are a few that deal with windows permissions and uninstalling the usb port drivers under windows, maybe something along that line will help.

Good luck,

Thanks, I’ll doublecheck the permissions of my user when I get home, but I am pretty sure I made it administrator.  I don’t use logging on for XP for my home machine, but it is also not set to automatically log on as Administrator.  If that doesn’t work, I guess I’ll just give up and use my work laptop (until I get laid off and/or install vista or build a new computer – I really shouldn’t rely on a music service that may or may not be around in the future anyway).

Message Edited by goldbars on 02-20-2009 08:55 AM

Be sure to look at that link, it has all the nice graphics and screen captures:    The permissions Solution looked like this:

SOLUTION 7 - Set user restrictions.

Some computers have user right restrictions that are set to disable access to new hardware.

STEP 1 - Log-in as an Administrator

STEP 2 - Edit restriction

NOTE: Disconnect the Sansa player if connected.

  1. Click Start  then Run ,
  2. Type cmd , then the press Enter.
    3. After the prompt, type Net localgroup Administrators local service /add then press Enter.

STEP 3 - Reconnect your device

Hello,

I had the same problem.

->

There was a problem installing this hardware: MTP Device

An error occurred during the installation of the device.

The filename, directory name, or volume label syntax is incorrect."
<-

I tried a load of different things to try and resolve, Reverting to WMP10, Copying the MTP driver from a working PC etc etc etc to no avail.

The solution, I finally discovered was to do with the UMDF (User Mode Driver Framework) service. It comes with WMP11, and installs during the setup.

Looking at the UDMF installation logs (c:\windows\Wudf01000Inst.log) - I found that there were errors during installation - I figured that re-installing UMDF might fix the problem. (and it did!) Unfortunatly, as it is not in add/remove programs, I ran into problems trying to remove it. If you un-install WMP11, it does not remove the UMDF dll’s. If the dll’s exist, then the UMDF installer will skip during the re-install of WMP11.

I managed to manually re-install UMDF using the method below.

To find the installer files for UMDF, you need to get them out of the WMP11 Installer.

How to find the installer for UMDF

  1. Run the WMP11 Setup file “wmp11-windowsxp-x86-enu”
    (It will extract the installer files into your %TEMP% folder)

  2. Click Start -> Run -> %temp%

  3. Press F3 and search for “umdf.exe”

  4. Copy this file to your Desktop

  5. Cancel the WMP11 Setup.

Now, you need to fool windows into thinking that UMDF is not installed on your computer, by renaming some files. Copy & Paste the following into a Command Prompt.

rename C:\WINDOWS\system32\drivers\wudfrd.sys den_wudfrd.sys
rename C:\WINDOWS\system32\drivers\wudfpf.sys den_wudfpf.sys
rename C:\WINDOWS\system32\wudfhost.exe den_wudfhost.exe
rename C:\WINDOWS\system32\wudfsvc.dll den_wudfsvc.dll
rename C:\WINDOWS\system32\wudfx.dll den_wudfx.dll
rename C:\WINDOWS\system32\wudfplatform.dll den_wudfplatform.dll
rename C:\WINDOWS\system32\wudfcoinstaller.dll den_wudfcoinstaller.dll

Now run the umdf.exe and re-install.

Spent hours trying to fix this, and finally managed to get it working.

Hope it works out for ya, if it does, let me know!

Denis

Now that’s a serious fix. I’m giving it a bump.

Had the same problem as you described,spent hours on the net looking for solutions trying different things tried your solution and it worked perfectly.Does anyone know a way of of spreading this solution around? With the amount of posts and questions about this problem on the internet it seems to be quite a common problem, yet Microsoft doesnt even have a solution! Took a member of the public to fix a gliche in their software. Anyway thanks very much and Merry Christmas from Downunder. 

Denis,

I am having similar issues in that my computer doesn’t recognize my Fuze in MTP mode.  I have tried all the solutions and found yours and tried it.  It didn’t fix my problem.  I’m not sure it worked as there are still errors and failed attempts in the Wudf01000Inst.log.  I tried to do it all over again and it displays the following Wudf01000 Setup Error “An equivalent or newer version of UMDF is already installed on this system”. After I did this and rebootedWindows had several updates it wanted to do some of which had to do with WMP 11.  I was really hoping your fix was going to correct my problem.  If you have any other ideas I would appreciate help you could give me.

Thanks - Jerry

Denis,

I deleted the files that were renamed and then was able to run the umdf.exe file again.  Looking at the log file there are still errors and failures showing up but I don’t know what they mean.  If I manually try and install the MTP device it displays the following: “This device cannot start (code 10)”.  I’m at a loss on what to do now.  I really wish I could get this Fuze to be recognized.  Not sure if I told you but I connected it to my work laptop and my brothers desktop and it was recognized immediately on both so the device does work in MTP mode.

Jerry

Can you post the log, then I can take a look for ya!

Here is the latest log.  I am limited on how much I can paste.  Hope you can find something.

0.156: ================================================================================
0.156: 2010/01/03 10:22:23.453 (local)
0.156: c:\e8509804af9e913830\update\update.exe (version 6.3.3.0)
0.187: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.187: Hotfix started with following command line: /quiet /norestart /er
0.218: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.218: WUDFCustom: Entering callback BeginInstallation.
0.218: WUDFCustom: installing version (1,0,0,5716.32).
0.218: WUDFCustom: Checking for presence of previous UMDF installation.
0.218: WUDFCustom: File C:\WINDOWS\system32\drivers\wudfrd.sys not found.
0.218: WUDFCustom: UMDF file %WINDIR%\system32\drivers\wudfrd.sys not found.
0.218: WUDFCustom: File C:\WINDOWS\system32\drivers\wudfpf.sys not found.
0.218: WUDFCustom: UMDF file %WINDIR%\system32\drivers\wudfpf.sys not found.
0.218: WUDFCustom: File C:\WINDOWS\system32\wudfhost.exe not found.
0.218: WUDFCustom: UMDF file %WINDIR%\system32\wudfhost.exe not found.
0.218: WUDFCustom: File C:\WINDOWS\system32\wudfsvc.dll not found.
0.218: WUDFCustom: UMDF file %WINDIR%\system32\wudfsvc.dll not found.
0.218: WUDFCustom: File C:\WINDOWS\system32\wudfx.dll not found.
0.218: WUDFCustom: UMDF file %WINDIR%\system32\wudfx.dll not found.
0.234: WUDFCustom: File C:\WINDOWS\system32\wudfplatform.dll not found.
0.234: WUDFCustom: UMDF file %WINDIR%\system32\wudfplatform.dll not found.
0.234: WUDFCustom: File C:\WINDOWS\system32\wudfcoinstaller.dll not found.
0.234: WUDFCustom: UMDF file %WINDIR%\system32\wudfcoinstaller.dll not found.
0.234: WUDFCustom: UMDF installation not found.
1.203: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed with error 0x2
1.203: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed with error 0x2
1.203: DoInstallation: CleanPFR failed: 0x2
1.203: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
1.203: SetProductTypes: InfProductBuildType=BuildType.IP
1.218: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.375: DoInstallation: FetchSourceURL for c:\e8509804af9e913830\update\update.inf failed
1.375: CreateUninstall = 0,Directory = C:\WINDOWS$NtUninstallWudf01000$
1.375: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
1.375: BuildCabinetManifest: update.url absent
1.390: Starting AnalyzeComponents
1.390: AnalyzePhaseZero used 0 ticks
1.390: No c:\windows\INF\updtblk.inf file.
1.390: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
1.390: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
5.453: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem19.CAT trusts inf c:\windows\inf\oem19.inf of device DOT4PRT\VID_03F0&PID_7211&MI_02&DOT4&PRINT_HPZ\9&2082E2B0&0&1
13.312: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.CAT trusts inf c:\windows\inf\oem6.inf of device PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02\3&11583659&0&00
13.734: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.CAT trusts inf c:\windows\inf\oem6.inf of device PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&11583659&0&08
14.171: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem8.CAT trusts inf c:\windows\inf\oem8.inf of device PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&11583659&0&F8
14.734: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT trusts inf c:\windows\inf\oem9.inf of device PCI\VEN_8086&DEV_27C0&SUBSYS_26011043&REV_01\3&11583659&0&FA
15.171: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT trusts inf c:\windows\inf\oem10.inf of device PCI\VEN_8086&DEV_27C8&SUBSYS_81791043&REV_01\3&11583659&0&E8
15.375: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT trusts inf c:\windows\inf\oem10.inf of device PCI\VEN_8086&DEV_27C9&SUBSYS_81791043&REV_01\3&11583659&0&E9
15.562: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT trusts inf c:\windows\inf\oem10.inf of device PCI\VEN_8086&DEV_27CA&SUBSYS_81791043&REV_01\3&11583659&0&EA
15.765: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT trusts inf c:\windows\inf\oem10.inf of device PCI\VEN_8086&DEV_27CB&SUBSYS_81791043&REV_01\3&11583659&0&EB
16.093: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT trusts inf c:\windows\inf\oem10.inf of device PCI\VEN_8086&DEV_27CC&SUBSYS_81791043&REV_01\3&11583659&0&EF
16.468: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem8.CAT trusts inf c:\windows\inf\oem8.inf of device PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&11583659&0&E0
16.828: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem8.CAT trusts inf c:\windows\inf\oem8.inf of device PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&11583659&0&E1
17.171: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem8.CAT trusts inf c:\windows\inf\oem8.inf of device PCI\VEN_8086&DEV_27DA&SUBSYS_81791043&REV_01\3&11583659&0&FB
17.578: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT trusts inf c:\windows\inf\oem9.inf of device PCI\VEN_8086&DEV_27DF&SUBSYS_81791043&REV_01\3&11583659&0&F9
30.656: OEM file scan used 29266 ticks
30.656: AnalyzePhaseOne: used 29266 ticks
30.656: AnalyzeComponents: Hotpatch analysis disabled; skipping.
30.656: AnalyzeComponents: Hotpatching is disabled.
30.656: AnalyzePhaseTwo used 0 ticks
30.656: AnalyzePhaseThree used 0 ticks
30.656: AnalyzePhaseFive used 0 ticks
30.656: AnalyzePhaseSix used 0 ticks
30.656: AnalyzeComponents used 29266 ticks
30.656: Downloading 0 files
30.656: bPatchMode = FALSE
30.656: Inventory complete: ReturnStatus=0, 29281 ticks
30.656: Num Ticks for invent : 29281
30.656: Allocation size of drive C: is 4096 bytes, free space = 115288338432 bytes
30.656: Drive C: free 109947MB req: 8MB w/uninstall 0MB
30.656: CabinetBuild complete
30.656: Num Ticks for Cabinet build : 0
30.656: WUDFCustom: Entering callback BeforeInstallOps.
30.656: DynamicStrings section not defined or empty.
30.656: FileInUse:: Added to Filelist: c:\windows\wudf01000.cat
30.656: FileInUse:: Added to Filelist: c:\windows\system32\wudfx.dll
30.656: FileInUse:: Added to Filelist: c:\windows\system32\wudfsvc.dll
30.656: FileInUse:: Added to Filelist: c:\windows\system32\drivers\wudfrd.sys
30.656: FileInUse:: Added to Filelist: c:\windows\system32\wudfplatform.dll
30.656: FileInUse:: Added to Filelist: c:\windows\system32\drivers\wudfpf.sys
30.656: FileInUse:: Added to Filelist: c:\windows\system32\wudfhost.exe
30.656: FileInUse:: Added to Filelist: c:\windows\system32\wudfcoinstaller.dll
30.953: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\wudf01000.cat
31.078: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\wudfx.dll
31.093: FileInUse:: Add to list - Service Name: WudfSvc ImageName: svchost.exe
31.312: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\drivers\wudfrd.sys
31.546: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\drivers\wudfpf.sys
31.671: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\wudfhost.exe
31.781: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\wudfcoinstaller.dll
31.781: In order to successfully complete this installation, the following services will automatically be stopped and restarted.
31.781: Windows Driver Foundation - User-mode Driver Framework.
31.781: MyStopService: ControlService failed :0x41c
31.781: GLE = 1052
32.796: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
32.859: System Restore Point set.
32.875: PFE2: Not avoiding Per File Exceptions.
32.921: GetCatVersion:  Failed to retrieve version information from C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Wudf01000.cat with error 0x80092004
32.921: GetCatVersion:  Failed to retrieve version information from C:\WINDOWS\Wudf01000.cat with error 0x80092004
33.140: Copied file:  C:\WINDOWS\System32\WUDFCoinstaller.dll
33.171: Copied file:  C:\WINDOWS\System32\WudfHost.exe
33.265: Copied file:  C:\WINDOWS\System32\WudfPlatform.dll
33.281: Copied file:  C:\WINDOWS\System32\WudfSvc.dll
33.296: Copied file:  C:\WINDOWS\System32\WUDFx.dll
33.343: Copied file:  C:\WINDOWS\system32\DRIVERS\WudfPf.sys
33.359: Copied file:  C:\WINDOWS\system32\DRIVERS\WudfRd.sys
33.406: DoInstallation: Installing assemblies with source root path: c:\e8509804af9e913830\
33.406: WUDFCustom: Entering callback CopyingComplete.
33.406: WUDFCustom: Installing using INF c:\e8509804af9e913830\wudf_update.inf.
33.796: WUDFCustom: C:\WINDOWS\system32\LogFiles directory already exists.
33.796: WUDFCustom: C:\WINDOWS\system32\LogFiles\WUDF directory already exists.
33.812: WUDFCustom: Security on directory C:\WINDOWS\system32\LogFiles\WUDF is:
33.812: WUDFCustom:
33.812: WUDFCustom: C:\WINDOWS\system32\drivers directory already exists.
33.812: WUDFCustom: C:\WINDOWS\system32\drivers\UMDF directory already exists.
33.812: Num Ticks for Copying files : 3156
33.812: Num Ticks for Reg update and deleting 0 size files : 0   
33.828: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
33.828: WUDFCustom: Entering callback SuccessInstallation.
33.937: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
0.219: ================================================================================
0.234: 2010/01/03 10:54:29.890 (local)
0.234: c:\7283595f0d6d1a48549aeb\update\update.exe (version 6.3.3.0)
0.609: Hotfix started with following command line: /quiet /norestart /er
0.656: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.781: WUDFCustom: Entering callback BeginInstallation.
0.781: WUDFCustom: installing version (1,0,0,5716.32).
0.781: WUDFCustom: Checking for presence of previous UMDF installation.
0.781: WUDFCustom: Found binary %WINDIR%\system32\drivers\wudfrd.sys version (1.0.0.5716.32)
0.844: WUDFCustom: Found binary %WINDIR%\system32\drivers\wudfpf.sys version (1.0.0.5716.32)
0.844: WUDFCustom: Found binary %WINDIR%\system32\wudfhost.exe version (1.0.0.5716.32)
0.891: WUDFCustom: Found binary %WINDIR%\system32\wudfsvc.dll version (1.0.0.5716.32)
0.906: WUDFCustom: Found binary %WINDIR%\system32\wudfx.dll version (1.0.0.5716.32)
0.922: WUDFCustom: Found binary %WINDIR%\system32\wudfplatform.dll version (1.0.0.5716.32)
0.922: WUDFCustom: Found binary %WINDIR%\system32\wudfcoinstaller.dll version (1.0.0.5716.32)
0.922: WUDFCustom: UMDF installation is same as update.
0.922: DoInstallation: CustomizeCall Failed: 0xf901
0.922: WUDFCustom: Entering callback EndInstallation.
0.922: WUDFCustom: Entering callback FailedInstallation.
0.969: An equivalent or newer version of UMDF is already installed on this system.
0.969: Update.exe extended error code = 0xf901

Message Edited by TomJensen on 05-03-2010 06:52 PM

Screw it, I’m sending it back to Amazon.com.  I’ve spent waaaaaayy too much time on this device.

Thanks for everyone’s help.

Just wanted to say thanks to Denis for this fix.  Although I didnt find the files you mentioned where/ in the same way as you described, it did fix my problems.

Here is what I had to do different for those that cant find the files:

I couldnt find Wudf01000Inst.log at C:\Windows to check for errors (even with “hide system files” unchecked) so I just had to skip this step.

Ran the WMP 11 install and did the %temp% thing and F3 search but it wouldnt find umdf.exe

So I went to the “wmp11-windowsxp-x86-enu” and right clicked the file.  In the drop down there is an option to “extract to…” (if you have winzip or 7zip installed).

The Umdf.exe is listed there.

Then I did the rename files from comand prompt (had to figure out Start/Run/cmd/enter).

ran umdf.exe and let it reinstall files.  Opened up WMP11 , hook up Fuze and the PC and WMP picked it up right away and I’m up and going again.

Awesome fix Denis, thanks again.

and to Tom for linking me here.

Message Edited by markriley on 03-31-2010 04:50 PM

Denis,

Thank you so so sooooo much for the fix you posted here.  After trying a bizzillion things, your fix is the one that fixed my sansa e280v2 so that i could finally remove/add music to the device again.

I guess the mtp driver wasn’t working and your fix got it going… 

i can’t thank you enough

your fix should be stickied to the top of sandisk’s message board here for the e200 series as I’m sure a boatttt load of people would find it useful

thanks again

Denis. I joined this forum just to thank you for figuring out this problem and for posting the solution. I bought this MP3 player for my Dad, who’s in the hospital. I was able to record the music he liked and get it over to him. Thanks again! Best, Glenn

MTP ERRORS