Windows 7 WDS Deployment - USB 3.0 Driver Package Won't Install

[thatley]

Hi all,

 

I'm hoping someone else has had this problem and can advise on best course of action.

 

Yesterday I needed to deploy my standard Windows 7 Pro x86 Image to a new set of Stone Laptops (Model NB-1103). I added all the drivers for the Stone Laptops in a separated driver packages node as I normally do, then deployed my image.

 

Everything installed perfectly except the 'USB 3.0 eXtensible Host Controller' which renders the USB 3.0 ports useless! As a test on the laptop after deployment I went into device manager and selected 'update driver' and pointed it to the location where I backed up all the Stone Laptop drivers, and it installed perfectly from the USB folder!!

 

Things I've tried:

 

Latest USB 3.0 driver from Stone Computers (Re-imaged - FAILED!)

Latest USB 3.0 driver from Intel (Re-imaged - FAILED!)

 

I've looked around on the web and a few people have had this on Lenovo and Dell laptops, but there's been no answers apart from they're saying it's a bug with Intel and Windows 7.

 

My standard Windows 7 image has never failed using WDS and adding driver packages up until now, and if new machines are being delivered to our schools with USB 3.0 ports - it's going to become a huge issue.

 

My workaround was to deploy my standard image to the new Stone Laptop (driver package used), but stop it from joining the domain. Install the USB 3.0 driver manually then sysprep and capture a new image so I can then deploy that to the rest of the new Stones. A real pain in the backside JUST for one driver!!!

 

Any suggestions?

 

Many thanks in advance.

[plexer]

Does it have an installer that you can run as an executable from the task sequence?

 

Ben

[Oaktech]

can you create a "check-and-run-if-not-present" VBS to install them on start up from a GPO? We've had to do that with some dell sound drivers that fail in the image.

[thatley]

Hi Plexer - I use WDS not MDT so I don't have the option of Task Sequences. I may have to get my head around using MDT 2012 if it gives greater flexibility with driver packages ?

 

Hi Oaktech - the driver does have a setup.exe which can run silently. I tested this manually on one of the laptops and it worked fine. It's just so annoying that you have to set a GPO to add one driver add-hoc. If that's the only solution, then I guess I'll have to set that up. Do you have any 'Check-and-run-if-not-present" scripts? My scripting is not great!

 

Also, my 'Standard' Windows 7 Image caters for about 6 different types of machine around the school, so if I use a VB Script - it needs to avoid trying to install to the other machines.

 

Thanks for your quick responses

Edited August 8, 2012 by thatley

[Oaktech]

When the driver installs from the setup, does it create any folders or does it just copy files, because you will need to modify the script to check for exactly what gets installed...

 

  @echo off
IF EXIST PathToTheProgramOrFile (
echo Installing Your Program..
yourprogram.exe /qb norestart
) Else (
echo Installing Your Program..
YourProgram.exe /qb /norestart
echo Installing Your Program..
yourprogram.exe /qb norestart
)

 

I would consider creating an OU for this particular laptop to allow you to target the driver specifically at these machines

Edited August 8, 2012 by Oaktech

[thatley]

It just copies files, no folders get created.

 

Excellent, thanks I'll give that a go

[thatley]

For information, I've found a much better way of getting these USB 3.0 drivers deployed automatically (and any other problematic drivers that won't install via WDS). I used the DISM GUI 3.1.1 Tool from Mike Celone (search on google for this), which is fantastic for injecting drivers into your offline image. I added all the relevant USB 3.0 drivers and they were installed as a PNP device automatically - Job Done!

 

Thanks for all your help

[Duke5A]

I just ran into this today with a Dell Latitude E5530. I install the drivers by hand on a test rig before adding them to the WDS console and I think I know why this fails. The USB3 driver actually has two separate drivers that need to install, but prior to installing the first driver Windows only sees one device missing a driver. After this gets installed is when the second device will show up in Device Manager. So yeah, adding these to the offline image is pretty much the only way to get around this. Absolutely weird....

[ShadowPeo]

Same issues with Dell Latitude E6430s and Dell Optiplex 9010 All in One. I can confirm what Duke states though about it installing one driver, then the the second one (the USB root hub to be precise) showing up, it is just wierd as this has happened with other devices I have used in the past and it worked fine, just not with this USB root hub

[old_n07]

Just had this with the 9010 AIO as well, used the DISM GUI app to update the WIM to fix the issue as suggested by Thatley

[thatley]

Hi all,

 

I've come across a number of chipset drivers that won't install with WDS too. So I use the DISM Gui app every time now - works perfectly. Shame we have to do it, but it takes no time at all.

 

Glad this has helped some of you

[LolekUK]

Just found this post couple of days ago, DISM Gui worked like a charm. USB 3.0 drivers installed. Thanks!

[free780]

Do these drivers require .net/c++ runtimes? Do you push out anything through gpo that would yave put these pre reqs in place when you install it. MDT is great and a lot easier than wds. WDS is really a tool for pxe and multicast. MDT adds drivers on the fly using dism provided pre reqs are in the images.

[fuzz]

I found this thread looking for an answer to the USB 3.0 via WDS problem. Using DISM Gui didn't really fit in with what I was trying to do. It made the process of updating my golden image kind of clumsy as I would've had to export the wim from WDS then inject the drivers and then import back again and do this every time the image needed updating.

So I found an alternative solution on another site. I thought I would post it here in case anyone else is looking for a solution to the issue.

 

I simply created a new driver group in WDS and set it to install all drivers in the group. Then I created a filter to target only the machines that required this driver and then added the USB 3 drivers to that group, removing them from my plug and play group. I did this using manufacturer name and bios version. The help file in wds contains the relevant wmic commands to extract this information.

 

The good thing about this solution is that you can continue to update the image without worrying about having to inject the drivers again later. Also 7 series chipsets require version 1 of the driver and 8 series require version 2, if you create two driver groups you can target these machines seperately.

[Cormang]

I found this thread looking for an answer to the USB 3.0 via WDS problem. Using DISM Gui didn't really fit in with what I was trying to do. It made the process of updating my golden image kind of clumsy as I would've had to export the wim from WDS then inject the drivers and then import back again and do this every time the image needed updating.

So I found an alternative solution on another site. I thought I would post it here in case anyone else is looking for a solution to the issue.

 

I simply created a new driver group in WDS and set it to install all drivers in the group. Then I created a filter to target only the machines that required this driver and then added the USB 3 drivers to that group, removing them from my plug and play group. I did this using manufacturer name and bios version. The help file in wds contains the relevant wmic commands to extract this information.

 

The good thing about this solution is that you can continue to update the image without worrying about having to inject the drivers again later. Also 7 series chipsets require version 1 of the driver and 8 series require version 2, if you create two driver groups you can target these machines seperately.

 

That's a good idea. I was using DISM to inject the USB3 drivers but all of a sudden it no longer works. I inject the drivers successfully but the OS is not installing them. Even after the OS boots it tries to install one of the drivers but then never installs the second. I have to manually install the driver from the device manager's Update Driver option. I can't figure it out. I've even started from scratch. The only difference is the new image has the latest Windows Updates.

 

I'm going to put my USB 3 drivers into a new driver group and select the option to apply them all. I'll filter it by manufacturer as we only have Lenovo laptops.

[free780]

Do the drivers require c++ runtimes?

[jvennes]

I have the Optiplex 9010's and 9020's. If I inject the USB3 drivers into the image, they will BSOD after installing the drivers.

 

Solution: I have my image Unattend file run a script which copies the 2 folders (9010-USB3 & 9020-USB3) and the setupcomplete.cmd to the C:\Windows\Setup\Scripts folder.

 

In SetupComplete.cmd, I use wmic computersystem get model to determine which drivers to install. pushd to the appropriate folder, and run setup -s (silent install).

 

Now the drivers for the USB3 are installed just before the installation is complete.

 

Hope this helps

[moakes]

I have the Optiplex 9010's and 9020's. If I inject the USB3 drivers into the image, they will BSOD after installing the drivers.

 

Solution: I have my image Unattend file run a script which copies the 2 folders (9010-USB3 & 9020-USB3) and the setupcomplete.cmd to the C:\Windows\Setup\Scripts folder.

 

In SetupComplete.cmd, I use wmic computersystem get model to determine which drivers to install. pushd to the appropriate folder, and run setup -s (silent install).

 

Now the drivers for the USB3 are installed just before the installation is complete.

 

Hope this helps

Any way you could possibly send me a copy of your files so I could use them as an example? I get BSODs on my hardware and would like to use the SetupComplete method to finish things up.

[jvennes]

namechange.cmd is called by the image unattend.xml in WDS.

 

@[u][url="http://www.edugeek.net/member.php?u=16971"]echo[/url][/u] off
pushd %~dp0

:: This script is called by unattend.xml

:: Copy setupcomplete.cmd, and the 2 usb drivers to local computer for install completion.
if not exist %WINDIR%\Setup\Scripts md %WINDIR%\Setup\Scripts
xcopy /e /y /i /q /c . %WINDIR%\Setup\Scripts\

:: Rename the computer to its registered DNS name, then reboot.
wsname /N:$DNS /reboot

popd

 

Here is my setupcomplete.cmd:

 

 @[u][url="http://www.edugeek.net/member.php?u=16971"]echo[/url][/u] off
title %0
pushd %~dp0
setlocal enableextensions

:: ==================================================================================================
:: This script is the last script that runs after the Windows setup is complete.
:: This is where we do the final cleanup, activate MS office, and finally,
:: join the computer to the domain and delete this file! (Modified 03/07/2014 -JFV)         
:: ==================================================================================================

:: Activate MS Office 2013 products
%WINDIR%\System32\cscript.exe "%PROGRAMFILES%\Microsoft Office\Office15\ospp.vbs" /act
:: ==================================================================================================

:: Delete the sysprep folder created by GHOST (if it exists)
if exist %SYSTEMDRIVE%\sysprep rd /s /q %SYSTEMDRIVE%\sysprep
:: ==================================================================================================

:: Delete the unattend.xml files (may contain passwords).
if exist %WINDIR%\System32\sysprep\unattend.xml del /Q /F %WINDIR%\System32\sysprep\unattend.xml
if exist %WINDIR%\Panther\unattend.xml del /Q /F %WINDIR%\Panther\unattend.xml
:: ==================================================================================================

:: Check to see if this is an Optiplex 9010/9020 and install USB3 drivers
wmic computersystem get model | findstr /i /c:"Optiplex 9010"
if not errorlevel 1 set target=Optiplex_9010-USB3
wmic computersystem get model | findstr /i /c:"OptiPlex 9020"
if not errorlevel 1 set target=Optiplex_9020-USB3
if defined target (
   pushd %target% 
       setup -s
   popd
)
:: ==================================================================================================

:: Join the domain
netdom join %COMPUTERNAME% /domain:engr /UserD:accountop /PasswordD:xxxxxxxx /REB:5
:: ==================================================================================================

:: Delete this script (because it contains a password).
rd /s /q %windir%\Setup\Scripts
:: ==================================================================================================

 

Hope this helps

Edited March 14, 2014 by jvennes

[moakes]

Thanks for this.

 

So do you place the .exe of the USB driver/software directly in %windir%\setup\scripts folder? "Optiplex_9010-USB3" <-- or is that a subfolder containing .inf files?

[jvennes]

So do you place the .exe of the USB driver/software directly in %windir%\setup\scripts folder? "Optiplex_9010-USB3" <-- or is that a subfolder containing .inf files?

 

dir of WDS Scripts folder:

Directory of Y:\Scripts

03/14/2014  12:14 PM              .
03/14/2014  12:14 PM              ..
11/14/2013  03:11 PM              Optiplex_9010-USB3
03/05/2014  04:46 PM              Optiplex_9020-USB3
03/14/2014  11:47 AM               400 namechange.cmd
03/07/2014  02:05 PM             4,800 setupcomplete.cmd
              2 File(s)          5,200 bytes

 

It's the complete driver package (which also installs the USB3mon service).

 Directory of Y:\Scripts\Optiplex_9010-USB3

11/14/2013  03:11 PM              .
11/14/2013  03:11 PM              ..
08/13/2013  06:43 PM              apps
08/13/2013  06:43 PM              Drivers
08/13/2013  06:43 PM              Lang
08/13/2013  06:43 PM              x64
11/02/2006  09:21 AM           319,456 DIFxAPI.dll
07/18/2013  02:44 AM             8,104 mup.xml
08/13/2013  06:45 PM            46,134 Readme.txt
07/18/2013  02:44 AM           961,784 Setup.exe
08/09/2012  04:17 PM             5,226 Setup.if2
07/18/2013  02:43 AM            41,984 USB3Ver.dll
              6 File(s)      1,382,688 bytes

[LVOgre]

I found this thread while searching for some answers, and I thought I'd register and share what I've learned so far about this, and other similar problems with WDS and drivers.

 

Update your image - Check out this link -http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it.aspx - The kernel mode driver framework was updated last year, and if your image doesn't have it, it may be causing problems.

 

Create a driver group - ideally you should have driver groups for each model you're imaging. You can also split out stuff like USB3 drivers and force them to install with every image by changing the applicability to "All driver packages in this group" in the group properties.

 

Use driver filters - Driver filters are of limited use on server 2008, but you will have some good options for segregating drivers. I don't recall them all, but you can certainly sort by chassis type and manufacturer. 2012 is MUCH better at this.

 

Use server 2012 for WDS - There have been some improvements, chief among them is driver filtering. If you have 2012 available in your organization, use it. You can now filter based on model. The model filter should be the model listed in WMI for the computer, you can find it by issuing the following command in CMD:

 

WMIC COMPUTERSYSTEM GET MODEL

 

So you can create a driver group for a specific model, specify that all drivers must be installed from the group, and apply that driver group only to the specific model. This makes things MUCH easier when it comes to driver management. This upgrade solved 99% of my driver problems with WDS.

 

 

This might not solve all of your problems, but hopefully it helps.

[rgm34]

I came across this thread earlier today because of a problem I've been having getting my WDS build to install the USB 3.0 Extensible Driver for HP Z230 CMT. I tried the DISM GUI app, no luck.

 

I then followed the suggestion to create a separate driver group. In the past I've been putting all my drivers in a single group per machine type. The driver package was created successfully but the drivers wouldn't load during install.

 

After creating a new driver package I attempted to add the package to the build and wouldn't you know, the new Package I created was not available. Turns out, by default the attribute window does not filter on USB which is the classification for these drivers. After adding the USB attribute filter the drivers appeared, I added the package to the WIM and all is good in the world. There were so many drivers in the original package that I created I didn't notice that the USB drivers were not being added during the Add Package process.

 

Hope this helps someone else.

[nmitguy]

Thanks for this info, I tried the same setup as you and for some reason it doesn't seem to load the USB3 drivers. If I run the setupcomplete.cmd manually then the setupcomplete.cmd runs fine and the usb3 drivers load. I know the setupcomplete.cmd is running after sysprep because the other items in there run. Any ideas?

[DCUK6]

Had this at my last place.

 

Happened only on the laptop usb3. Desktop usb3s installed correctly.

 

Never found the answer but didn't look a great deal. Just called it a extra security feature.