Adding Hyper-V Integration Components to WinPE using MDT 2008 – Updated for Hyper-V RTM.

Mike Sterling recently posted and excellent blog on Using the Hyper-V Integration Components in WinPE on his MSDN blog. 

Wouldn’t it be nice if we could add the Integration Components to the WinPE Images created by MDT 2008?

The procedure assumes you want to import both the x86 and x64 integration components.  You will need the MSU files that contain the Integration Components.  These can be found on the VMGuest.ISO.  The easiest way to get them is to mount the VMGuest iso in a VM and just copy them.  Mike’s blog lists several other tools that can also be used to extract the MSU files. 

Place the MSU files in a empty folder and use the following batch file to extract the drivers that we will import into MDT.  This batch file produces a folder called OutOfBoxDrivers in the same folder where the MSU files are.

expand  Windows6.0-KB951634-x86.msu -F:*.CAB MSU

MD Files
expand  MSU\ -F:* Files

MD OutOfBoxDrivers
for /d %%I in (files\*_none_*) do xcopy %%I OutOfBoxDrivers\%%~nI\ /e
rd /s /q MSU
rd /s /q Files

After batch file completes, start the MDT 2008 console and right click on Out-Of-Box-Drivers and choose new.

 Untitled picture

I normally put drivers that are only going to be used in WinPE in a separate group, this is optional, but i would recommend it.

Note that since the x86 and x64 filenames are the same and they use the same inf files, you cannot add both x86 and x64 drivers unless you put them in separate groups and check Import drivers even if they are a duplicates of an existing drivers. You will then have to create the x86 and x64 WinPe images in separate steps

This post was contributed by David Hornbaker, a Senior Consultant with Microsoft Services - U.S. East Region.

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use

Comments (6)
  1. DeploymentGuys says:


    Unfortunately, none of us Deployment Guys can repackage parts of a Microsoft product and then distribute it on the web.  This would be a violation of the End User License Agreement (EULA) for the product and a violation of Microsoft company policy.  Only the teams that develop and market the product can do that.

    We can feed back this suggestion to the Hyper-V team as a request for the next service pack or major release.

    Michael Murgolo

  2. Ankit Oberoi says:

    I think we have a typo in following command

    For /d %%I in (files*_none_*) do xcopy %%I OutOfBoxDrivers-x86%%~nI /e

    It should be

    or /d %I in (files*_none_*) do xcopy %I OutOfBoxDrivers-x86%%~nI /e  

  3. Jeff Wade says:

    Here’s a thought.  Rather than giving us a recipe for building the Hyper-V integration drivers, can’t someone just please post them in neat little download package.  Good Lord…I don’t want to grow the ingredients for a cake, I want to BUY one already made.

  4. Michael Niehaus' Windows and Office deployment ramblings says:

    There have been some blog postings talking about how to add the Hyper-V integration components into Windows

  5. Kevin says:

    HyperV Integration Components

    MD MSU

    expand  Windows6.0-KB951634-x86.msu -F:*.CAB MSU

    MD Files

    expand -F:* Files

    MD OutOfBoxDrivers-x86

    for /d %I in (files*_none_*) do xcopy %I OutOfBoxDrivers-x86%%~nI /e

    rd /s /q MSU

    rd /s /q Files

    do the same for x64

  6. Richard Klemme says:

    Found out the hard way that Vista SP2 wouldnt work easily with the existing Integration Components i.e. HyperV RTM.

    The existing WinPE drivers were OK, however we couldnt post-install the Integration Services CD.

    I then upgraded an existing Win2008 HyperV server to SP2 and noticed the Integration Components CD and files within had been upgraded.

    I then extracted these and voila it all works now..its in the same place c:windowssystem32vmguest.iso as before

    Have tried builds on HyperV on original Win2008 SP1 (RTM version) and SP2 successfully.

    There must be a be a dependency on Vista SP2 with the updated drivers in Win2008 HyperV SP2 here.

Comments are closed.

Skip to main content