Jump to content











Photo
- - - - -

No USB detected/can't install drivers


  • This topic is locked This topic is locked
5 replies to this topic

#1 sixstorm1

sixstorm1
  • Members
  • 7 posts
  •  
    Canada

Posted 13 May 2009 - 04:20 AM

Hi everyone,

I got some problems with drivers and VistaPE:
When I boot on some computers, VistaPE doesn't detect my USB devices as it is supposed to do. On some computers it does, on some other it doesn't (most don't). I absolutely need my USB stick to work. It's the same thing for most of the peripherals. If i try to install the driver manually, I always get a message saying "driver package installation failed: the system cannot find the path specified.". It does this when I try to install ANY driver (including USB.inf and USBSTOR.inf) from "X:\Windows\inf" or "C:\Windows\inf" and also tried "C:\Windows\system32\driverstore", but always the same error message. I looked inside the INF file and I cannot find any kind of paths (which path would be invalid?). And on some computer the USB keyboard doesn't even work. I am using VistaPE 12 RC1 and a normal ISO build. VistaPE is useless for me if USB is not working on half of the computers.

UPDATE:

I just checked the PnPUtil log (setupapi.deb.log) and on every driver install attempt it shows the following error: Could not create temporary directory for driver package.

Log:
>>> [SetupCopyOEMInf - X:\windows\inf\usbstor.inf]
>>> Section start 2009/05/12 23:36:28.421
cmd: X:\windows\system32\PnPutil.exe -i -a X:\windows\inf\usbstor.inf
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
dvi: {Staging Package To Driver Store - phase 1}
sto: Inf Path = X:\windows\inf\usbstor.inf
sto: Flags = 0
sto: Processor Architecture = 0
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
!!! sto: Could not create temporary directory for driver package.
sto: {Staging Package To Driver Store - phase 1 exit(80070003)}
! inf: Add to Driver Store unsuccessful
! inf: Error 3: The system cannot find the path specified
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2009/05/12 23:36:29.265
<<< [Exit status: FAILURE(0x00000003)]

This problem happens for every driver, and even vpeldr.exe is not able to install drivers when it boots. But what I don't get at all is how come this error is thrown on some computers (like vmware), and on other these drivers install just fine. I don't know how a directory create error could be hardware related. Are the VistaPE developpers aware of this problem? Any solutions?

#2 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 13 May 2009 - 04:52 AM

Look at this thread,
try this and this modifications

Edit:
When you want load driver in the running PE via the command line using e.g.
'drvload.exe inf_path'
or
'pnputil.exe -i -a inf_path'
then all needed driver files (.inf .sys etc.) should reside in the same folder,

in VistaPE at the scripts: Drivers > 'Drivers - Lan' or 'Drivers - SATA/RAID/SCSI'
for this reason I prefer to set 'Drivers mode: External'

Edited by dera, 13 May 2009 - 06:21 AM.


#3 sixstorm1

sixstorm1
  • Members
  • 7 posts
  •  
    Canada

Posted 13 May 2009 - 07:44 AM

UPDATE:

I just checked the PnPUtil log (setupapi.deb.log) and on every driver install attempt it shows the following error: Could not create temporary directory for driver package.

Log:
>>> [SetupCopyOEMInf - X:\windows\inf\usbstor.inf]
>>> Section start 2009/05/12 23:36:28.421
cmd: X:\windows\system32\PnPutil.exe -i -a X:\windows\inf\usbstor.inf
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
dvi: {Staging Package To Driver Store - phase 1}
sto: Inf Path = X:\windows\inf\usbstor.inf
sto: Flags = 0
sto: Processor Architecture = 0
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
inf: Opened INF: 'X:\windows\inf\usbstor.inf' ([strings.0409] <src = normal>)
!!! sto: Could not create temporary directory for driver package.
sto: {Staging Package To Driver Store - phase 1 exit(80070003)}
! inf: Add to Driver Store unsuccessful
! inf: Error 3: The system cannot find the path specified
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2009/05/12 23:36:29.265
<<< [Exit status: FAILURE(0x00000003)]

This problem happens for every driver, and even vpeldr.exe is not able to install drivers when it boots. But what I don't get at all is how come this error is thrown on some computers (like vmware), and on other these drivers install just fine. I don't know how a directory create error could be hardware related. Are the VistaPE developpers aware of this problem? Any solutions?

#4 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 13 May 2009 - 04:45 PM

maybe the problem is that
VistaPE does not build the folder '\Windows\System32\DriverStore' and the 'FileRepository'

try this,
open a command window and type:
mkdir X:\a
copy X:\WINDOWS\inf\disk.inf X:\a
copy X:\WINDOWS\inf\volume.inf X:\a
copy X:\WINDOWS\inf\usbstor.inf X:\a
copy X:\WINDOWS\System32\Drivers\disk.sys X:\a
copy X:\WINDOWS\System32\Drivers\volsnap.sys X:\a
copy X:\WINDOWS\System32\Drivers\usbstor.sys X:\a
pnputil.exe -i -a "X:\a\disk.inf"
pnputil.exe -i -a "X:\a\volume.inf"
pnputil.exe -i -a "X:\a\usbstor.inf"

in this case at me all the pnputil command returns with success

#5 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 13 May 2009 - 05:09 PM

Any solutions?

Once more:
try what ctmag suggested at the post #23 here

OK, i tried some things and this should work:

add the following lines at the end of the [Process] section of 04-additional.script

DirCopy,&#34;%BootSRC%\Windows\inf&#34;,&#34;%TargetDir%\Windows&#34;

 DirCopy,&#34;%BootSRC%\Windows\system32\drivers&#34;,&#34;%TargetDir%\Windows\system32&#34;

 DirCopy,&#34;%BootSRC%\Windows\system32\driverstore&#34;,&#34;%TargetDir%\Windows\system32&#34;

 FileDelete,&#34;%TargetDir%\Windows\inf\*.pnf&#34;

 DirDelete,&#34;%TargetDir%\Windows\inf\BITS&#34;

 DirDelete,&#34;%TargetDir%\Windows\inf\RemoteAccess&#34;

it will need some more space on the disc and also in RAM, but it fixes the USB Mouse/Keyboard issue and it also fixes a bug where when you booted from an USB drive the USB drive was not visible (only the X drive was visisble..)

Please report if it works for you...thanks !

Edit: Added info to make clearer


plus also try his modified vpeldr.exe
attached in post #1 here

#6 sixstorm1

sixstorm1
  • Members
  • 7 posts
  •  
    Canada

Posted 14 May 2009 - 12:57 PM

Problem Solved:
I used ProcessMonitor to look at which file it didn't find and I found that pnputil was searching for the .sys files in the same directory as the inf files (C:\Windows\inf). why it returned an error. Just moved all the .sys file to the inf directory and now everything's working.
  • Herpis likes this




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users