Device enumeration problems (but not what you think)

[Ted Yo!]

This thread and attached files are for WMP10 ONLY!
Do not run the attached script if you are using WMP11.

Before reading any further, unless you are opposed to it, install WMP11. Two of the problems you will read about below are fixed. Go... do it now... I'll wait... If it doesn't fix you come back and finish reading this thread.

If you don't want to read any of this, or if you aren't comfortable doing it yourself, I've attached a zip file that will do most of it for you. This is a shotgun approach to just "fix everything you know about". Of course running this, or any script, means that you completely trust the source (in this case me) not to do anything harmful to your PC.

{fix.zip}

Purpose: Informative. I have now collected the information I was after, so this is purely provided as a guide to help you resolve your problems. The information provided here won’t work in 100% of the cases (especially when it comes to power issues) but walking through the appropriate section will fix most users.

Below are a couple of work arounds that I know of for different classes of problems. Before you start make sure you have WMP10, XP SP1 or higher. If you do not have XP SP1 or higher you can no longer get it from Windows Update, so you must either order a CD or use the following link:
http://www.microsoft.com/downloads/d...displaylang=en

Note that you will likely have to re-install WMP10 after installing SP2.

The behavior you are seeing is the first step in determining your problem. If the behavior listed doesn’t match what you are seeing you can safely skip the corresponding section.

1) The player shows the USB connected screen and Windows shows that the device installed correctly. Device manager shows no problems with the device, but you can not access it though WMP or My Computer.
----This can either be the registry permissions problem or the software registration problem. See #1 and #4 below.

2) The player shows the USB connected screen but Windows is unable to find a driver for the device. The device shows up as unknown in device manager.
----This can either be the OS descriptor problem or a software registration problem. See #2 and #4 below. This same behavior can occur if you are having the power problem although the setupapi.log will usually list the device as a “Bad Device” in this case. You may also need to go through #3 below.

3) The player does not show the USB connected screen or your device does not show in device manager (even as an unknown device).
----This is likely the power problem. See #3 below.

WARNING: Editing your computer’s registry should not be taken lightly. Always make a backup before making any changes. See the following link for details:
http://support.microsoft.com/default...b;en-us;322756

1) Permissions Problems:

Quick and dirty:
Try running the tool from the following link:
http://support.microsoft.com/default...b;en-us;810509

Note that after downloading it, you have to run it with a -l switch from the run line or the command line (like "Pnpreg –l") you can't just double click it.

If the tool fails, the manual steps are:

Open regedit and navigate to HKEY_LOCAL_MACHINE\S YSTEM\CurrentControl Set\Enum
Right click on this key and choose Permissions…
Verify that “Everyone” is allowed “Read” access.
If you don’t see this, add “Everyone” giving them “Read” access.

Do the same thing with:
HKEY_LOCAL_MACHINE\S YSTEM\CurrentControl Set\Enum\USB
(This key should be set to inherit from the Enum key, but that may not always be the case.)

2) OS Descriptor Problems:

In device manager, double click on the Unknown device and go to the Details tab.
In the drop down list select Hardware Ids.
(If the hardware ID says USB\Vid_0000&Pid_000 0 this is not your problem, instead see #3 below.)

Take the first line and strip out all the letters and symbols (so all you have left is a number). For iRiver devices it should start with 4102.

Navigate to HKEY_LOCAL_MACHINE\S YSTEM\CurrentControl Set\Control\UsbFlags
Look for a key name that matches the number you wrote down.

Delete this key.

When you connect your device again, Windows will now interrogate the descriptor (which it normally only does once).

3) USB Power Problems:
Behavior: Device does not show up in Device manager (or anywhere else).

This can be caused by several things but they all boil down to the device not getting enough power, try the following:

First, try connecting with a fully charged player and leave the AC plugged in when you connect. (Thanks to VitalSpark for this tip.)

Power off your PC. Unplug the power cord for 4-5 seconds to give all the capacitors enough time to discharge. Boot back up and try your device. (Possible charge on the USB bus.)

Plug the device into the rear USB port rather than the front port.

Plug the device directly into the USB port (no hub or extension cable).

Try using a powered USB hub. (Note that some will not work, so if you can, borrow one before buying one.)

If you are overclocking, don't. It can change the amperage to the USB bus. (If you don't know what this means, you aren't doing it.)

Even if you aren't overclocking there is a possibility that some of your cmos/bios settings have been changed. Try resetting the BIOS back to its defaults. If you aren’t using a USB keyboard try disabling legacy USB support. (Thanks to ghostskate for pointing this out.)

Try updating your chipset drivers. (IE: VIA, nVidia ect.)

Last resort: Try buying a new USB 2.0 controller card. (If you only have USB 1.x on your system you might consider this option earlier on. You will be amazed at how much faster your songs will transfer over 2.0 then they do over 1.x.)

3.5) Problems with ‘E’ firmware:

I’m putting this as a new “3.5” because I suspect that the problem people are having with the ‘E’ firmware is that it is slightly more sensitive to the power problem then the US firmware is. TimD found that putting the US firmware on his player resolved his issues. You can see his thread here:
My UK bought H10 5g is US firmware? this seems to resolve the problems!!!!


4) Software Registration Problems and Missing Files:
Behavior: Device shows up correctly in Device manager and possibly My Computer, but not in WMP.

Re-install the latest WMF redist from:
http://support.microsoft.com/default...b;en-us;891122

(Optional): Install a DRM performance fix for subscription content from:
http://support.microsoft.com/default...b;en-us;902344

(Optional): Install a sync fix for large files from:
http://support.microsoft.com/default...b;en-us;895316

You will likely need to play all your DRM content in WMP to re-indiv and reacquire licenses if necessary before syncing it to your device.

If the above didn’t fix you, you can also try re-installing WMP10 itself form:
http://www.microsoft.com/windows/windowsmedia/mp10/

How to get help from me:
Take the following files from your system and put them in a zip archive:
C:\windows\setupapi. log
C:\windows\wmsetup.l og
C:\windows\debug\wpd \wpdtrace.log

Mail me the zip along with a detailed description of your problem.

[KendallJ]

Ok, I'm game.

0) Yes
1) Yes
2) No
3) No

1) Did this - No change
2) did this - device reinterrogated - No Change
3) Did this - No change (did not install the Optional link)

Interested in running diagnostics for you if you have them.

[Ted Yo!]

I should have included this in my original post:

Verify that the Windows User Mode Driver Framework service is running. You can do this from the command line with 'sc query umwdf' or through the services mmc snap-in.

[Ted Yo!]

KendallJ's problem was actually one level deaper in the registry than 'most' at:
HKEY_LOCAL_MACHINE\S YSTEM\CurrentControl Set\Enum\USB

The take away here is to verify that this key is set to inherit after verifying that the Enum key allows everyone read access.

[matthewbarry]

Thanks a lot for your advice. I have been going crazy getting my t30 to work on my desktop pc, but I have had no problems getting it to work on my laptop. What finally seemed to help was what you suggested below. When I looked, there was no "Everyone" group present:


Do the same thing with:
HKEY_LOCAL_MACHINE\S YSTEM\CurrentControl Set\Enum\USB
(This key should be set to inherit from the Enum key, but that may not always be the case.)
[/Edit]

Thanks,

Matthew Barry

[Ted Yo!]

Thank Kendall, not me. If he wasn't so patient with me and sent me all sorts of logs I would have never known that this key could be messed up as well.

If you are willing, I would like to know what USB devices you have plugged into your system as well as any software you may have that enumerates USB devices.

[topcar2000]

0) Is your device connecting in MTP mode?
yea
1) Does your device show up in Device Manager?
not as the device. shows up as "UNKOWN DEVICE"
2) Does your device show up in My Computer?
nope
3) Does your device show up in WMP?
nope

[Ted Yo!]

Can you check to make sure you have wpd10.inf and wpdmtp.inf in your c:\windows\inf directory. Would you be willing to send me your setupapi.log?

If so PM me and I'll give you my e-mail address.

[Ted Yo!]

I played around with the following download a little bit to see if it would be an easier fix for people. Of the problems I've seen so far it should fix ~75%.

Of course, if you run this and it fixes you I don't get to know exactly which problem you were hitting and I am still trying to gather data... but if you really want to take the easy way out and don't like editing your registry manually:

http://support.microsoft.com/default...b;en-us;810509

Note that after downloading it, you have to run it with a -l switch (like "Pnpreg –l" you can't just double click it).

Disclaimer: I profiled this tool and it looks like it itterates over every single key under "enum" and resets them to default permissions provided you yourself have access to do so. While this is still targeted at the exact problems people are seeing, it's more of a shotgun approach then a targeted change.

[-Neil-]

Hi there, first post and it's not a good one to start with :/

I've got a H10 20Gb.

0) Is your device connecting in MTP mode? Yes
1) Does your device show up in Device Manager? Yes and no
2) Does your device show up in My Computer? No
3) Does your device show up in WMP? No

When I go to 'Settings' in the menu, it states at the bottom I've got 'Firmware v.1.02E MTP'

If I connect the H10 to the USB cable, 'USB Connected' will appear on screen and this appears in my taskbar:



Then on the H10 itself it goes to a iRiver screen with 'Boot 1.20 MTP Intialize', then back to the 'USB Connected' and so on, a continuous loop :/

Any help would be highly appreciated, thanks.

Neil.

[-Neil-]

I've plugged it in to 4 computers in total:

Mine: Windows XP Pro SP2
My Bros: Windows XP Pro SP2
My Fathers: Windows XP Pro SP2
My Friends: Windows XP Pro SP2

All result in the above posts problem, this is puzzling to say the least and I'm rather miffed to pay £180 for something that doesn't work

Is this a problem with the H10 itself or Windows installed on each of the 4 pc's?

Thanks in advance,

Neil.

[Ted Yo!]

This sounds like an actual hardware/firmware problem. I'd return it for a new one. If you are out of warranty you could try putting the latest firmware on it to see if it helps.

[-Neil-]

Thanks for the reply

I actually bought the device yesterday and recieved it today, shame as it's a nice piece of kit.

Is there anything else I could do to help the situation or does it definitely sound like a hardware/firmware problem?

When I go to the 'Setting' menu it displays ''Firmware v.1.02E MTP'', is this an old firmware I take it?

I don't think I'd be able to put a new firmware on as the device isn't recognised by windows and appears and dissapears from Device Manager in time with the looping problem described above.

Any other steps to prove to the online store it's faulty? I've already sent something (Akasa fan controller) back to them and it's taking almost 2 weeks so far and no new fan controller :/

Neil.

[Ted Yo!]

There is newer firmware and you can probably get it on since that type of connection (UMS) is completely different. However, I personally wouldn't do anything that would cause them to claim you messed it up when it's clearly defective (in the state you received it).

If you want to try updating the firmware anyway:
Grab the latest from http://iriver.com/html/support/downl...ew.asp?idx=739
Hit the reset button on the device with a paper clip.
Plug it into your computer.
Hold down the O button while turning it on.

Provided it connects this way, upgrade the firmware using the "Manual" option.

Best of luck.

[-Neil-]

Thanks, I tried to update the firmware but the updating software couldn't see the H10

It went no further than this:



Seems I'm out of luck of late, and to think this was a birthday present from my mum :/

Neil.

[Prevail]

Don't want to throw another help request at you, but I figured if you had a chance to look at mine you might find some mutual core of Neil's problem and my own.

0) Yes
1) No
2) No
3) No

I have the 5GB H10 US version with radio. When I attempt to connect it into a tested and correctly functioning USB port and in its default mode (MTS), the computer is completely unresponsive and the H10 does NOT show a "USB Connected" screen.

I installed the version of WMP 10 found on the installation CD, had no luck, installed the new WMP 10 from Microsoft, had no luck, performed each of the tasks instructed in your first post (set permissions in registry, looked for USB flags to match, and installed the media format patch), and tried again. No luck.

I verify that the 'umwdf' service is running as "wdfmgr.exe" under task manager.

The computer all of this was attempted on is running XP Home SP2 and is a custom-built computer. I also attempted plugging it in on a system with nearly identical specifications, except running XP Professional, and got the same results.

I should mention that the device DOES work when I use the "UMS trick" to turn it on. "USB Connected" is displayed on the H10 and the H10 pops up as drive F:. I also tried to update MTS firmware from 2.01 to 2.51 while in UMS mode and failed. However after redoing it manually, the firmware under Settings on the device now reads as "PFD 2.51".

Thanks; let me know if there is anything else you want to know. I can't imagine the effort you have to put into these.

[Ted Yo!]

Send me an e-mail with the following and I'll try to figure out what is going wrong:

c:\windows\setupapi. log
c:\WINDOWS\Debug\WPD \wpdtrace.log

Can you also give a little more detail about the computer being completly unresponsive?

[Prevail]

By completely unresponsive, I meant that when I plug the USB into the computer, absolutely nothing happens: nothing shows up in device manager when I scan for changes, it doesn't show up under my computer, it doesn't show up in WMP, and I see no blips or pop-ups and don't hear any noises.

[TDIPower]

OK this is what I know
iRiver H10 20gb
Firmware V1.00 MTP
Boot 1.01 MTP Initilized (comes on screen when disconect USB)
Its Blue

When I plug into my laptop I can load music on/off via explorer or WMP10
Laptop displays could work fast (only has USB1 ports XP reports this with USB2 devices)

SO to speed up things connected to my main PC
Abit IS7-E mobo P4 2.6ghz, MSI/nvidia FX5600 ultra, 512 DDR , 120gb SATA drive.

Plug in and I get the USB bubble saying device not recognised etc.. lists as unknown device. H10 displays as USB connected.

As my system had been playing up a bit I formated C and did a clean install of XP, all the updates for Mobo from Abit, graphics from MSI, Active Sync 3.8 for my XDA2i PDA, Drivers for Trust web cam. Basicly Set the system up from scratch clean.

H10 Still is an unknown device.

Ive never reg edited but have know problems doing it if I have distructions to follow. Im fine updating the H10 but again need to know what I need to update with. Im not sure as there are a lot of version things on the iriver site to follow.

Many thanks if you can get me connected to my main PC at USB2 ratherthan having to Laptop at USB1

Pete