Developer Forum

I have the following DLLs listed in the INF file which are required to
install WinUSB driver on XP.

[SourceDisksFiles.x86]
WinUSBCoInstaller.dll=1
WdfCoInstaller01007.dll=1
WUDFUpdate_01007.dll=1

It takes a long time to install the driver because it interns does the
microsoft update. Is it normal for taking that long? Is there any way
I can reduce the install time?

thanks.

what do the setup logs say in terms of time for each step?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

It takes 4 mins to complete the install process when I saw the time
taken for total process in the setupapi.log file. It started the
process from
Searching for hardware ID,
finding the ID in the INF file,
start copying the listed(given below) DLLs into windows directory ,
registering the coinstallers
installing interfaces
doing full intsall of the VID/PID of the device
finished successfully

I didn't see the time taken for each step. At the end, it took 4 mins
to update. Is it because of the driver package is un-signed? Or Is
this normal(taking long time) for installing the coinstallers on XP?

I appreciate for your reply and looking forward to know more on this
issue.


On Jan 28, 10:53燼m, "Doron Holan [MSFT]"

>I didn't see the time taken for each step. At the end, it took 4 mins

I think it's due to restore point. Restore points in Vista+ are created using VolSnap, and VolSnap means VSS, and VSS preparations steps to create a snapshot take _really_ long.

--
Maxim S. Shatskih
Windows DDK MVP
XXXX@XXXXX.COM
http://www.yqcomputer.com/

have experienced a similar problem. Vista installation is quite fast but
winusb takes a variable amount of time from 30 seconds to 4 minutes on XP. I
am attaching the winusb_update.log which gives an indication of what caused
the delay.

Can someone help me understand this log? Can I do something to reduce this
time? Maybe this is not a winusb problem but a system restore problem. But I
need some sort of indication of where to look into.

Thanks
Madhan


0.156:
================================================================================
0.156: 2009/04/01 13:43:23.293 (local)
0.156: c:\0fead3f35c496cd92bf5dbe1add33348\update\update.exe (version 6.3.4.0)
0.156: Hotfix started with following command line: /quiet /ER
/log:C:\WINDOWS\temp\winusb_update.log
0.187: In Function GetBuildType, line 1170, RegQueryValueEx failed with
error 0x2
0.641: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed with
error 0x2
0.641: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed with
error 0x2
0.641: DoInstallation: CleanPFR failed: 0x2
0.641: In Function GetBuildType, line 1170, RegQueryValueEx failed with
error 0x2
0.641: SetProductTypes: InfProductBuildType=BuildType.IP
0.641: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.719: DoInstallation: FetchSourceURL for
c:\0fead3f35c496cd92bf5dbe1add33348\update\update_XP.inf failed
0.719: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallwinusb0100$
0.719: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
0.719: BuildCabinetManifest: update.url absent
0.719: Starting AnalyzeComponents
0.719: AnalyzePhaseZero used 0 ticks
0.719: No c:\windows\INF\updtblk.inf file.
0.719: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
0.719: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
4.953:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device ACPI\PNP0103\4&374CCB25&0
19.672: SetupVerifyInfFile failed with error 0x490 for oem87.inf of device
PCI\VEN_1033&DEV_015E&SUBSYS_FFFFFFFF&REV_02\5&2B491BAE&0&0000F0
21.250:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_F3\3&B1BFB68&0&F0
21.672:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem3.CAT
trusts inf c:\windows\inf\oem3.inf of device
PCI\VEN_8086&DEV_2811&SUBSYS_00000000&REV_03\3&B1BFB68&0&F8
22.312:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem7.CAT
trusts inf c:\windows\inf\oem7.inf of device
PCI\VEN_8086&DEV_2828&SUBSYS_20A817AA&REV_03\3&B1BFB68&0&FA
22.984:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem5.CAT
trusts inf c:\windows\inf\oem5.inf of device
PCI\VEN_8086&DEV_2830&SUBSYS_20AA17AA&REV_03\3&B1BFB68&0&E8
23.203:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem5.CAT
trusts inf c:\windows\inf\oem5.inf of device
PCI\VEN_8086&DEV_2831&SUBSYS_20AA17AA&REV_03\3&B1BFB68&0&E9
23.422:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem5.CAT
trusts inf c:\windows\inf\oem5.inf of device
PCI\VEN_8086&DEV_2834&SUBSYS_20AA17AA&REV_03\3&B1BFB68&0&D0
23.641:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem5.CAT
trusts inf c:\windo