Re: How to reinstall Android driver on WinXP?

[Paul]

pamela wrote:
> How can I re-install an Android driver on WinXP?
>
> In the past, I've attached my Kit Kat tablet (Hudl 2) to XP without
> any problem. The tablet shows up as an extra drive in XP and basic
> file transfer can be done.
>
> Recently, I attached the tablet and this time XP tried to reinstall
> the driver. XP correctly detected an Android device was attached and
> that an MTP driver was needed. but the re-installation failed with
> the message: "Cannot Install This Hardware ... A service installation
> section in this INF is invalid". Now in Device Manager there's now
> a yellow question mark over the Android driver and the driver details
> say: "No driver files are required or have been loaded for this
> device".
>
> I guess the driver is still on the XP system somewhere. How can I
> re-assign it to the Android entry in Device Manager?
>
> Is there a way I can get the old driver assigned to Android in XP's
> device manager without installing some mega pack of Microsoft drivers
> such as something I found on the web called "MTP Porting Kit Setup".
> Whatever that it. My XP is heavily customised over 10 years and can
> be a bit fragile when applying packs like this.

I don't have any MTP devices here to experiment with.
So all I can point at, is "materials".

The purpose of posts like this, is to give you "search terms"
or "breadcrumbs". As without a device to experiment with,
it might be difficult to identify any extra steps needed.

The drivers are actually in Windows Media Player installer kit.
The MTP Porting Kit (I have three copies on disk here), on
one of them I added the word "useless" to the file name. And
an examination today confirms this. I can't see a damn thing
of interest in there. Maybe some earlier version of the Kit
actually had a driver. I don't see a driver in the version
I've got. WMP11 should be a good source. (Note - WMP itself
likes to validate that the OS is genuine, so expect some
blow-back from using this. When doing "experiments" on
your computer, you should have a recent backup of C:
at your disposal!!!)

*******

I happen to have this on disk already as well.

wmp11-windowsxp-x86-enu.exe Date Published: 2010-06-22
File Size: 25,740,256 bytes

https://www.microsoft.com/en-ca/download/windows-media-player-details.aspx?751be11f-ede8-5a0c-058c-2ee190a24fa6=True&a03ffa40-ca8b-4f73-0358-c191d75a7468=True

Using 7ZIP (7-zip.org), I can see wmfdist11.exe inside it.
Which could be extracted, or by using "Open inside" you
can get the stuff out of the inside of it.

An interesting file in there is wpdmtp.inf . Unlike a lot of
files of INF type that Microsoft writes, it doesn't have the name
of the file inside the header of the file. Which implies the
file does not get renamed in C:\Windows\INF when installed.
It should still have that name. You probably already have that
file in your INF (hidden) folder. You can adjust the File Explorer
viewing properties, to make the folder visible.

If the Android in Device Manager with the yellow mark is still
there, you could "Update driver" and point it at wpdmtp.inf perhaps.

;
;Device is identified by Microsoft OS descriptor
;If your device does not support it, use specific VID & PID for identification <---
;
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP

[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP

You can see someone editing that file, in order to get
their device working properly. (Strictly speaking, it's
dumb to do this. Real manufacturers have their INF simply
"include" the Microsoft one.) Modern devices should
be using that PNP identifier. For devices that don't,
you have to craft VID & PID detection.

http://forum.xda-developers.com/showthread.php?t=1291293

Now, an example of a service installation section
in the file, would be this. I think this might be a
kernel USB filter driver. Something MTP specific
rides on top of this, possibly in userspace. So
this could actually be the stanza causing the
error message.

; =================== WPDUSB ===================

[MTP.WpdUsb.AddService]
DisplayName = %WpdUsb.SvcDesc%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\wpdusb.sys
LoadOrderGroup = Base

*******

As another example, I have "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0".

In 25_escape\ssudmtp.inf is an example of how a company that does not use
the right DeviceDesc does it. They match on VID and PID, and their
INF simply "calls" the Microsoft driver.

;*********************************** Begin ssudmtp.inf ****************************************
;
; Name : ssudmtp.inf
;
; Function : Install SAMSUNG Escape USB Media Transfer Protodol driver
;
; Copyright (c) DEVGURU Co., Ltd. (www.devguru.co.kr)
;
;***********************************************************************************************

[Version]
Signature="$Windows NT$"
Class=WPD
ClassGUID={EEC5AD98-8080-425f-922A-DABF3DE3F69A}
Provider = %Provider%
DriverVer=06/10/2014,2.11.10.0
CatalogFile=ssudmtp.cat

[ControlFlags]
ExcludeFromSelect=*

[Manufacturer]
%ssud% = ssud, NTx86.5.1, NTamd64.5.1, NTx86.6.0, NTamd64.6.0

[SSUD.NTx86.6.0]

[SSUD.NTamd64.6.0]

[SSUD.NTx86.5.1]
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_685C
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_6860&MI_00
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_6862&MI_02
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_686A&MI_00

[SSUD.NTamd64.5.1]
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_685C
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_6860&MI_00
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_6862&MI_02
%USB\SAMSUNG_MOBILE&MTP.Desc% = ssud.Install, USB\VID_04E8&PID_686A&MI_00

[ssud.Install]
Include = wpdmtp.inf, WINUSB.INF
Needs = WPD.MTP, WINUSB.NT

[ssud.Install.hw]
Include = wpdmtp.inf
Needs = WPD.MTP.Registration

[ssud.Install.Services]
Include = wpdmtp.inf
Needs = WPD.MTP.Services

[ssud.Install.CoInstallers]
Include = wpdmtp.inf
Needs = WPD.MTP.CoInstallers

[ssud.Install.Wdf]
Include = wpdmtp.inf
Needs = WPD.MTP.Wdf
UmdfServiceOrder=WpdMtpDriver

; no sys copyfiles - the sys files are already in place

[Strings]
ssud = "SAMSUNG Electronics Co., Ltd. "
Provider="SAMSUNG Electronics Co., Ltd. "
USB\SAMSUNG_MOBILE&MTP.Desc="SAMSUNG Mobile MTP Device"

;*********************************** End ssudmtp.inf ****************************************

So while the Samsung package is 16,007,072 bytes in size, it
still manages to have a dependency on outside resources (wpdmtp.inf).
For that part at least, it's a kind of "stub installer". The folder
also has a ton of other stuff, so the package solves more
than just an MTP issue.

And this is the info Microsoft provides to developers.

"The MTP Setup Information (.inf) File"

https://msdn.microsoft.com/en-us/library/windows/hardware/ff597687(v=vs.85).aspx

By searching for the specific Android device you've got,
perhaps you can determine any device specific things
that need to be done.

I haven't a clue how the AddService thing could be
throwing an error. There isn't likely to be a typo
in there.

Also, to see how the driver install process is going,
on WinXP you are lucky to have "setupapi.log" to inspect.
The newest entries are at the end of the file. Each
entry has a date stamp, like

[2016/08/25 10:45:02 980.11 Driver Install]

and using that, you can see what "noise" was generated
in recent days. For example, on Aug25, I plugged in a
USB flash stick :-) That's the time stamp for it.

C:\WINDOWS\setupapi.log

Paul

[J. P. Gilliver (John)]

In message <nquab9$687$1...@dont-email.me>, Paul <nos...@needed.invalid>
writes:

>pamela wrote:
>> How can I re-install an Android driver on WinXP?
>> In the past, I've attached my Kit Kat tablet (Hudl 2) to XP without
>>any problem. The tablet shows up as an extra drive in XP and basic
>>file transfer can be done.
>> Recently, I attached the tablet and this time XP tried to reinstall

[tale of woe snipped]

>>Whatever that it. My XP is heavily customised over 10 years and can
>>be a bit fragile when applying packs like this.

I know just what you mean (-:!
[excellent as usual, but in this case long! Paul bit snipped]
> Paul
>
As a less stressful, though more fiddly if you want to do file transfers
_often_, alternative: can your tablet use memory cards, and transfer
(using its own software) files to those? (Or even simpler, USB memory
sticks?)

(I haven't really played with tablets, but for digital cameras, I've
always found it much simpler just to take the card out of the camera and
put it into the PC, than to connect the camera to the PC and deal with
whatever pops up when I do, and having to get the camera into a certain
"mode", and sometimes running down the camera charge.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

A leader who keeps his ear to the ground allows his rear end to become a
target. - Angie Papadakis

[Rob Morley]

On Sat, 10 Sep 2016 11:37:00 +0100
pamela <inv...@nospam.com> wrote:

> I tried updating the Android driver using "wpdmtf.inf" from my
> hard drive.
>
> However, XP says that my INF file doesn't list my hardware and
> refuses to proceed.
>
You shouldn't need a specific "Android driver" just to manage files -
the phone should be treated as a standard USB mass storage device, for
which the driver is built in to Windows. The special drivers are for
stuff that usually only programmers need.

[Paul]

pamela wrote:

>> [SNIP INF FILE CONTENTS]

>> ****************************************
>>
>> So while the Samsung package is 16,007,072 bytes in size, it
>> still manages to have a dependency on outside resources
>> (wpdmtp.inf). For that part at least, it's a kind of "stub
>> installer". The folder also has a ton of other stuff, so the
>> package solves more than just an MTP issue.
>>
>> And this is the info Microsoft provides to developers.
>>
>> "The MTP Setup Information (.inf) File"
>>
>> https://msdn.microsoft.com/en-
>> us/library/windows/hardware/ff59768
>> 7(v=vs.85).aspx
>>
>> By searching for the specific Android device you've got,
>> perhaps you can determine any device specific things
>> that need to be done.
>>
>> I haven't a clue how the AddService thing could be
>> throwing an error. There isn't likely to be a typo
>> in there.
>>

>> [SNIP LOG]
>>
>> Paul

>
> I tried updating the Android driver using "wpdmtf.inf" from my
> hard drive.
>
> However, XP says that my INF file doesn't list my hardware and
> refuses to proceed.
>

> Do I need a more up to date "wpdmtf.inf"? I tried to get it here
> but the link doesn't provide the file.
>
> http://www.infdump.com/download-inf-
> files_new.php/inffiles/W/wpdmtp
> .inf/5.2.0.0/download.html
>
> I don't want to install MTP Porting Kits or Windows Media Player
> tools which some people refer to.

In this example, you can see someone hack their wpdmtp.inf file
and add an identity string to get their mobile device to be detected.

http://forum.xda-developers.com/showthread.php?t=1291293

c:\windows\inf\wpdmtp.inf

;Device is identified by Microsoft OS descriptor
;If your device does not support it, use specific VID & PID for identification

;
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_413C&PID_B10B&MI_00 <--- hacked added line
;
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_413C&PID_B10B&MI_00 <--- hacked added line

You can use USBTreeView, to get more information about the
Android device, and get values for VID and PID. They are
four character hex strings.

http://www.uwe-sieber.de/usbtreeview_e.html

In the sample picture here, you can see the "Device ID" field
is rich in numbers for the purpose.

http://www.uwe-sieber.de/gif/usbtreeview_1.png

Using the field you find in USBTreeView that
looks like this - "VID_413C&PID_B10B" , you may be
able to do a Google search and see someone else hacking
their wpdmtp.inf for the purpose. If you're worried
about the exact syntax.

Paul

[Mike Tomlinson]

En el artículo <XnsA67E589...@8.17.249.104>, pamela
<inv...@nospam.com> escribió:

>In the past, I've attached my Kit Kat tablet (Hudl 2) to XP without
>any problem. The tablet shows up as an extra drive in XP and basic
>file transfer can be done.

I'm an iOS user, but I seem to remember that on Android you can set the
way the phone storage is seen in the phone settings - MTP mode (which
needs a driver) or mass-storage mode.

Since you say it used to work, maybe the problem's the phone settings
having been changed and not the WinXP machine?

--
(\_/)
(='.'=) Bunny says: Windows 10? Nein danke!
(")_(")

[Paul]

Mike Tomlinson wrote:
> En el artículo <XnsA67E589...@8.17.249.104>, pamela
> <inv...@nospam.com> escribió:
>
>> In the past, I've attached my Kit Kat tablet (Hudl 2) to XP without
>> any problem. The tablet shows up as an extra drive in XP and basic
>> file transfer can be done.
>
> I'm an iOS user, but I seem to remember that on Android you can set the
> way the phone storage is seen in the phone settings - MTP mode (which
> needs a driver) or mass-storage mode.
>
> Since you say it used to work, maybe the problem's the phone settings
> having been changed and not the WinXP machine?
>

They mention the notification drawer can be set for ADB or MTP.

http://athena.outer-reaches.com/wp/index.php/archives/1170

The driver on that page, consists of HudlMTP.inf, with the
magic lines...

;

;Device is identified by Microsoft OS descriptor
;If your device does not support it, use specific VID & PID for identification
;
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP

%GenericMTP.DeviceDesc%=MTP, USB\VID_0E79&PID_5009&MI_00 <--- ID for the HUDL ?

[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_0E79&PID_5009&MI_00

The Hudl 2 is likely to have a different ID. But the concept
should be the same.

So far, I'm not seeing any mention of USB Mass Storage as
a setting for the notification drawer.

Paul

[Robin]

On 09/09/2016 08:42, pamela wrote:
> How can I re-install an Android driver on WinXP?
>

> In the past, I've attached my Kit Kat tablet (Hudl 2) to XP without
> any problem. The tablet shows up as an extra drive in XP and basic
> file transfer can be done.
>

> Recently, I attached the tablet and this time XP tried to reinstall
> the driver. XP correctly detected an Android device was attached and
> that an MTP driver was needed. but the re-installation failed with
> the message: "Cannot Install This Hardware ... A service installation
> section in this INF is invalid". Now in Device Manager there's now
> a yellow question mark over the Android driver and the driver details
> say: "No driver files are required or have been loaded for this
> device".
>
> I guess the driver is still on the XP system somewhere. How can I
> re-assign it to the Android entry in Device Manager?
>
> Is there a way I can get the old driver assigned to Android in XP's
> device manager without installing some mega pack of Microsoft drivers
> such as something I found on the web called "MTP Porting Kit Setup".
> Whatever that it. My XP is heavily customised over 10 years and can
> be a bit fragile when applying packs like this.
>

Have you checked that the Hudl2 is still in MTP mode? In KitKat I think
that's

Settings
Storage
Settings (the 3 dots top right)
USB Connection

and select MTP

--
Robin
reply-to address is (intended to be) valid

[Daniel James]

In article <BmdTNgNK...@jasper.org.uk>, Mike Tomlinson wrote:
> I'm an iOS user, but I seem to remember that on Android you can set
> the way the phone storage is seen in the phone settings - MTP mode
> (which needs a driver) or mass-storage mode.

It depends very much on the phone and on the Android version.

Older Android versions supported only mounting as a USB Mass Storage
Device, but newer versions support MTP and/or PTP connections. My
current phone (a Sony running Android 5.1 Lollipop) allows me to choose
between MTP and Mass Storage, but not all do.

> Since you say it used to work, maybe the problem's the phone settings
> having been changed and not the WinXP machine?

It may be more than settings if the OP has upgraded the Android system
on his device.

It's been a while, but I'm pretty sure my old Samsung phone was
originally USB MSD but changed to MTP-only with an upgrade (to KitKat?).

--
Cheers,
Daniel.

[Paul]

pamela wrote:

>
> I downloaded USBtreeview and saw an exclamation mark on one of the
> ports in the tree on the left side.
>
> Below is the text of what USBtreeview reports for that port. I
> notice there are one or two parts which say "error". In particular
> it says for DriverKeyName: ERROR_FILE_NOT_FOUND
>
> Seems a pretty substantial error. But what to do?
>
>
> ##################### START ###########################
> =================== USB Device =======================
>
> DriverKeyName : ERROR_FILE_NOT_FOUND <=== Don't panic just yet
>
> Connection Status : 0x01 (DeviceConnected) <=== Good!
> Device Bus Speed : 0x02 (High-Speed)
>
> idVendor : 0x1D4D (Pegatron Corporation) <=== This is "Asus OEM company"
> idProduct : 0x504A
> bcdDevice : 0xFFFF
> Language 0x0409 : "MTP" <=== You put HUDL2 in MTP mode?
Verify that is so.

> --- MSFT String Descriptor 0xEE --

> qwSignature Lang 0x0409 : "MSFT100" <=== Possibly "MSFT 1.0 extension"
> bMS_VendorCode : 0x01 (MSFT = Stock Ticker symbol for Microsoft)
> bPad : 0x00
>

For the DriverKeyName, frequently the file name of the file
used, is inside the file itself. The Wpdmtp.inf file does
*not* have its name inside the file. If USBTreeView is
scanning all the INF text files for that string, that
could account for a failure to find it.

I have a theory that whatever you're using, that INF
file has an "INCLUDE" statement in it. Which is not
getting loaded, and is causing the Service Definition
problem. If the file used "INCLUDEs" another file, that
file must be available for the resulting file to be
fully defined.

Initially I thought that maybe the HUDL2 had "lost its identity"
and was claiming to be something else. But one other poster
has a HUDL2 with the same VID and PID. The Asus corporation
has the Pegatron operation, which makes OEM computers for
the likes of Tesco. It's not a surprise that Tesco hasn't
purchased a membership with USB.org and registered its
own unique VID. Nothing is harmed by riding Pegatron coattails.

%GenericMTP.DeviceDesc%=MTP, USB\VID_1D4D&PID_504A&MI_00

Unfortunately, nothing in the USBTreeView can help us
with the USB\MS_COMP_MTP part.

Since you hacked the file but used the wrong ID string,
right now it must be matching on the USB\MS_COMP_MTP part.

So something about the INF file itself is deficient. Either
it's trying to INCLUDE something that does not exist, or
it's the wrong INF file that is getting used. And something
you did recently, has installed yet another INF file similar
in nature to the OS one.

Remember, there are

1) wpdmtp.inf is provided by Windows Media Player 11 installation.
Windows XP users were expected to install Windows Media Player 11 or
better, to get that EXE file I was showing you in a previous post.

2) <vendor_specific_file>.inf if your HUDL2 comes with its
own Windows installation package. <vendor_specific_file>.inf
would INCLUDE wpdmtp.inf. A vendor specific file won't work,
unless the Microsoft material in (1) is present. The purpose
of a vendor specific file, is if USB\MS_COMP_MTP is not
being presented to the Plug and Play the OS uses. And it cannot
"see" the device properly. Your evidence is the device is seen,
but during load of the INF, some INCLUDE material is missing.

Otherwise, the device has formed an endpoint and is connected.
It is presenting the MTP string. I have no MTP devices here
to verify what that should look like. But I suspect all is
well on that end. It doesn't say PTP for picture protocol
or ADB for Android Debug Bus, or use a standard class identifier
that equates to USB_Mass_Storage. So I'm guessing at this point,
it's not the device end that's a problem.

You are going to need to look at the INF files that are
associated with MTP in your INF folder.

You also need to examine the setupapi.log file, as I instructed
you to do, in case there are any breadcrumbs that amplify on
the "service definition" problem. The very end of the setupapi.log
may have error messages. It's worth a check.

*******

The INF file presented here, I can't tell what OS this is for.
It's yet another example of what is supposed to be loading
an MTP device in Windows.

http://answers.microsoft.com/en-us/mobiledevices/forum/mdnokian/mtp-device-driver-installation-failure-gt-solution/aaf31792-2f28-4a43-a585-17fa2f0a08c6?auth=1

Paul

[Paul]

pamela wrote:

> I checked this and, yes, the Hudl2 is still in MTP mode.
>
> I briefly tried the alternative (PTP mode) but it gave access to
> only two folders (DCIM and PICTURES) as if the Hudl2 is a digital
> camera.

That's an excellent result, proving the plumbing all works.

It's just the specifics of what's in your WinXP OS that is
a problem. Like somehow an INF is screwed up, or some of the
DLLs or .sys or whatever materials, is missing.

Don't forget the availability of this for WinXP. You don't have
to use it right away. But if you use 7ZIP to examine this file,
you can see wmfdist11.exe inside there. Which has a copy of the
standard INF for MTP inside it.

wmp11-windowsxp-x86-enu.exe Date Published: 2010-06-22
File Size: 25,740,256 bytes

https://www.microsoft.com/en-ca/download/windows-media-player-details.aspx?751be11f-ede8-5a0c-058c-2ee190a24fa6=True&a03ffa40-ca8b-4f73-0358-c191d75a7468=True

PTP protocol predates MTP, and it's possible WinXP came with
support for that as a built-in, and a person does not need
to use wmp11 installation to get it to work. Only MTP is
cursed with that requirement. It was an attempt to only
allow "genuine" WinXP users to get a copy of the MTP driver.
As otherwise, they could have hosted wmfdist11.exe as
a separate download file.

*******

This may be part of getting MTP to work, but my recollection is,
this stuff came in through Windows Update, after SP3. At least,
I was seeing references to it after that point. I can't see this
being missing.

https://en.wikipedia.org/wiki/Windows_Driver_Foundation

Paul

[Paul]

pamela wrote:

>
> I looked for setupapi.log on my XP system but can't find it anywhere
> on my hard drive. Google suggests it is in C:\windows\inf\ but there
> is no .log files there at all.
>

C:\WINDOWS\setupapi.log

Open Notepad and navigate there.
Or you can try this from Command Prompt.

notepad C:\WINDOWS\setupapi.log

The entry on the end of mine looks like this. I only copied
this to show you the date stamp is the first line of a stanza.

[2016/08/25 10:45:02 980.11 Driver Install] <=== Beginning of a stanza

#-019 Searching for hardware ID(s): storage\volume
#-018 Searching for compatible ID(s): storage\volume
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "STORAGE\Volume" in C:\WINDOWS\inf\volume.inf; Device: "Generic volume"; Driver: "Generic volume"; Provider: "Microsoft"; Mfg: "Microsoft"; Section name: "volume_install".
#I023 Actual install section: [volume_install]. Rank: 0x00000000. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [volume_install] in "c:\windows\inf\volume.inf".
#I320 Class GUID of device remains: {71A27CDD-812A-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "STORAGE\REMOVABLEMEDIA\7&36B31021&0&RM".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [volume_install.Interfaces] from "c:\windows\inf\volume.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "STORAGE\REMOVABLEMEDIA\7&36B31021&0&RM".
#I121 Device install of "STORAGE\REMOVABLEMEDIA\7&36B31021&0&RM" finished successfully.

You will notice that it made a reference to an INF file.
The INF files are stored in C:\WINDOWS\inf and are
text files. For example "oem23.inf" is a renamed file
that might be used to install my network chip. In the case
of the MTP problem you're working on, apparently no rename
is involved, since "wpdmtp.inf" is a system file. Just as
"usbport.inf" is for a USB port. The USB now uses generic
Microsoft "class" drivers. Microsoft wrote those drivers
(with help from manufacturers on "quirks"). Third part drivers
are renamed systematically to "oemXX.inf" to prevent
name collisions by bad name choices of the manufacturer.
Microsoft knows the names of the INF files it wrote,
so they will not collide and don't need renaming.

Using the correct setting for File Explorer and the View Options,
allows looking in "hidden" folders, allows seeing system files
and so on. The default File Explorer settings are pretty
useless, and one of the first things a user has to fix.
Like, fixing it so you can see the file extension,
is very important...

Paul

[Paul]

pamela wrote:

>
> I have WMP 10. I'm not keen to install WMP 11 just for Android
> file browsing to work. My old XP is too creaky and heavily
> customised to feel comfortable with installing WMP 11.

The wmp11-windowsxp-x86-enu.exe file (25,740,256 bytes) has wmfdist11.exe inside it.

https://www.microsoft.com/en-ca/download/windows-media-player-details.aspx?751be11f-ede8-5a0c-058c-2ee190a24fa6=True&a03ffa40-ca8b-4f73-0358-c191d75a7468=True

Inside wmfdist11.exe is wpdmtp.inf . So that tells me the associated folder
can function as an MTP driver. You would do a driver update in Device Manager,
and point Device Manager to the folder with the freshly unpacked files.

Installing 7ZIP and using the right-click context menu, allows "opening" the EXE
as if it was a ZIP file. Extracting the content means *not* having
to actually install WMP11, to gain access to the MTP driver included.
I do this all the time, extract a portion of an archive and use it
for a specific purpose. The 7-ZIP program is one of the *first* programs
I install in a new OS installation, it is that useful...

http://7-zip.org/

And as I indicated before, I have nothing here with MTP, so
I cannot simulate anything. I can't test that the driver works
as expected, or anything. But I can tell you, by inspection,
it's an MTP driver. It's an MTP driver that will work instantly,
as long as the external device declares itself properly. If
the external device does not end up declared properly,
then hacking the VID&PID values into the INF would be required.
Your symptoms suggest this won't be necessary, as the install
action is being triggered without the correct discrete VID&PID
values anyway. It tried to install, which means the device
is being detected with the nice generic string...

%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP

Paul

[Arno Welzel]

Nope - most Android devices don't use mass storage mode but need support
for the media transfer protocol (MTP).

That's whay XP wants to install the MTP driver.

Maybe this helps:

<https://www.microsoft.com/en-in/download/details.aspx?id=19153>


--
Arno Welzel
https://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[Arno Welzel]

pamela schrieb am 2016-09-09 um 09:42:

> Recently, I attached the tablet and this time XP tried to reinstall
> the driver. XP correctly detected an Android device was attached and
> that an MTP driver was needed. but the re-installation failed with
> the message: "Cannot Install This Hardware ... A service installation
> section in this INF is invalid". Now in Device Manager there's now
> a yellow question mark over the Android driver and the driver details
> say: "No driver files are required or have been loaded for this
> device".

You dont't need an "Android" driver, you need support for MTP (media
transfer protocol).

[Paul]

Arno Welzel wrote:
> Rob Morley schrieb am 2016-09-10 um 15:33:
>
>> On Sat, 10 Sep 2016 11:37:00 +0100
>> pamela <inv...@nospam.com> wrote:
>>
>>> I tried updating the Android driver using "wpdmtf.inf" from my
>>> hard drive.
>>>
>>> However, XP says that my INF file doesn't list my hardware and
>>> refuses to proceed.
>>>
>> You shouldn't need a specific "Android driver" just to manage files -
>> the phone should be treated as a standard USB mass storage device, for
>> which the driver is built in to Windows. The special drivers are for
>> stuff that usually only programmers need.
>
> Nope - most Android devices don't use mass storage mode but need support
> for the media transfer protocol (MTP).
>
> That's whay XP wants to install the MTP driver.
>
> Maybe this helps:
>
> <https://www.microsoft.com/en-in/download/details.aspx?id=19153>

https://en.wikipedia.org/wiki/Media_Transfer_Protocol

"Windows XP requires Windows Media Player 10 or higher;

later Windows versions have built-in support.

Microsoft has also made available an MTP Porting Kit
for older versions of Windows back to Windows 98.
"

That suggests the MTP Porting Kit should not be
installing a driver in WinXP, leaving the driver
install to the WMP11 delivery vehicle. The wmfdist11.exe file
inside this download, has the MTP driver files in it.

https://www.microsoft.com/en-ca/download/windows-media-player-details.aspx?751be11f-ede8-5a0c-058c-2ee190a24fa6=True&a03ffa40-ca8b-4f73-0358-c191d75a7468=True

Paul

[Gene Malvern]

In article <XnsA67E589...@8.17.249.104>,
inv...@nospam.com says...

> How can I re-install an Android driver on WinXP?
>

> Is there a way I can get the old driver assigned to Android in XP's
> device manager without installing some mega pack of Microsoft drivers
> such as something I found on the web called "MTP Porting Kit Setup".
> Whatever that it. My XP is heavily customised over 10 years and can
> be a bit fragile when applying packs like this.
>

Windows XP won't see the Android files using MTP
unless you install Windows Media Player 11. The
Media Player 11 download contains the the necessary
MTP connection files. There's no other way to do
it.

[Gene Malvern]

In article <XnsA6C99CB...@81.171.118.178>,
inv...@nospam.com says...

> I have WMP 10 on Windows XP because I'm using from a restored
> backed up. However I am reasonably sure this was the setup when I
> was using MTP but then one day it didn't work. However, to make
> sure everything on the drive is sufficently up to date I just
> installed WMP 11 but it hasn't helped.
>
> The Device Manager for "Android" shows a yellow circle and the
> error message says:
>
> "The drivers for this device are not installed. (Code 28).
> To reinstall the drivers for this device, click Reinstall
> Driver."
>
> This is what I got when I reinstalled MTP Device 5.2.5326.4762
> (from C:\windows\inf\wpdmtp.inf)
>
> "The an error occurred during the installation of the
> device. A service installation section in this INF is
> invalid."
>
> So I'm back to square 1 and WMP 11 hasn't changed anything.
>
> ISTR that an Android tablet contains files which gets transferred
> to Windows when the tablet is first connected. Is there anything
> in my Hudl2's "MTP_USB" folder which I could use to correct the
> faulty INF in Windows?
>
>
Get on the web and look for USB drivers from the
manufacturer of your tablet. I'm not familiar with
your particular tablet but I know that Samsung
smartphones and tablets require Samsung drivers to
be installed on the Windows PC to enable the
Samsungs to connect to that PC. That's probably
true for your tablet as well. Re-installing the
drivers may re-set whatever has been managled or
modified.

[Bill in Co]

I just did a Google search for Samsung Android USB drivers, and found
several sites, including Samsung's own site, which might be even more
informative.

I think (but I'm not sure) the latest USB driver for several of the Samsung
Tablets is version 1.5.61.0, but I may be mistaken (if so, someone can
please correct me). It's about 10 MB in size.

[Paul]

pamela wrote:

> The following entries taken from the log point to a missing
> WUDFCoinstaller.dll. Where can I get a non-infected copy from?
>
> ------------- START --------
> #E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32
> \WUDFCoinstaller.dll" for driver "MTP Device" will be installed
> (Policy=Ignore). Error 2: The system cannot find the file
> specified.
>
> #E144 Loading module "C:\WINDOWS\system32\WUDFCoinstaller.dll"
> failed. Error 126: The specified module could not be found.
> ------------- END --------

"KMDF Version history"
https://msdn.microsoft.com/en-us/windows/hardware/drivers/wdf/kmdf-version-history

"UMDF Version history"
https://msdn.microsoft.com/en-us/windows/hardware/drivers/wdf/umdf-version-history

Your file WUDFCoinstaller.dll is mentioned here. And
I seem to have a file of that name that might have been
delivered as part of my WinXP SP3 installer disc

https://blogs.msdn.microsoft.com/iliast/2009/06/09/analyzing-the-installation-of-wdf-1-7-and-1-9-drivers/

UMDF is available this way. This is *not* available
on catalog.update.microsoft.com .

"User-Mode Driver Framework version 1.9 update for Windows XP (SP2,SP3),
for Windows Vista, and for Windows Server 2008"

https://support.microsoft.com/en-us/kb/970159

Not strictly required to solve your problem, but a matching KMDF...

https://support.microsoft.com/en-ca/kb/970158

And the WinXP delivery mechanism for MTP, of using
WMP11 installation as the delivery vehicle, is another
way to get it.

http://wiki.robotz.com/index.php/MTP_Device_Driver_Installation_on_Windows_XP

My WUDFCoinstaller.dll file is "September 28, 2006" "6.0.5716.32",
and maybe it pre-dates SP3. So mine is not patched to 1.9
or anything. I also don't have an MTP driver onboard.

*******

You can use "sfc /scannow", but the WinXP version uses local
resources to resolve issues. It looks in the driver cache
perhaps, or in the various patches delivered via Windows
Update. In addition, it will refer to your installer CD.
There are two registry entries sometimes needed, to even
get it to look at the CD. Using it is a total pain. Later
OSes, missing file resolution is handled a bit more smoothly.

The few checks I've done so far, it looks like WinXP
is a "scorched earth" thing. And the "robotz.com" article
is your best bet.

Paul

[Gene Malvern]

In article <WYmdnTfyxrdWkavFnZ2dnUU7-
c_N...@earthlink.com>,
surly_cu...@earthlink.net says...
>I think the latest USB driver for several of
>the Samsung tablets is version 1.5.61.0.

Yup. That's the one I've been using for some time.
The problem is that she doesn't have a Samsumg.
She has an Hudl2.

[Gene Malvern]

In article <XnsA6C99CB...@81.171.118.178>,
inv...@nospam.com says...

Try these drivers from Intel:

https://software.intel.com/en-
us/android/articles/intel-usb-driver-for-android-
devices