WinPE 3.1 Scripts

WinPE 3.1 Scripts

This latest version was compiled on September 27th, 2012. This is the third update to our WinPE scripts. Please read our tutorial on DISM for using the files below to compile a functioning WinPE 3.1 environment. And also I would recommend reading our tutorial on Making a Bootable Flash Stick as that will save you time over a CD.

WinPE 3.1 Scripts

Added new Windows 7 winpe.bmp wallpaper for WinPE 3.1 Boot Environment.
Added new drivers for WinPE 3.1 environment including some netbooks and HP eCopy machines.
Added the newest stable version of GimageX.
Removed GHOST from packages.
Added WinPE 3.1 from the WAIK supplement for SP1

WinPE3.1 Contents_x86 [Pre-Compiled with GImageX App]

WinPE3.1 Contents x86

Drivers for WinPE 3.1

I have had a couple people ask for me to post the drivers that I have integrated into our WinPE 3.1 discs. A list and download link are below, enjoy!

Includes the following drivers:
d600_nic, d600_vga, d610_vga, e4200_nic, e4300_nic, e5400_nic,
e5500_nic, e6400_nic, e6500_nic
gx110_nic, gx110_vga, gx150_nic, gx150_vga, gx240_nic, gx240_vga, gx260_nic, gx260_vga, gx270_nic, gx270_vga, gx280_nic, gx280_vga, gx620_nic, gx620_vga, gx745_nic, gx745_vga, gx755_nic, gx755_vga, gx960_nic, gx960_vga, HPD530SFF_vga, HPD530SFF_nic
–Virtual Environment–

Download Mirrors

You may also like:

Sysprep a Windows 7 Machine – Start to Finis... This is the old version, please see the new Sysprep a Windows 7 Machine – Start to Finish V2. Note - I highly recommend creating a boot or rescue d...
DISM Tool – WinPE 3.1 Boot Environment This is the new tutorial for the recent release of WinPE 3.1. You can still read the old tutorial here. DISM Tool You will need the following to...
Copy Taskbar Icons Windows 7 Sysprep This is the old version, please see the new Copy Taskbar Icons Windows 7 Sysprep v2. Ok, you can thank a colleague of mine (Dinyero Johnson) for th...
Sysprep Windows 7 – Third Party Anti-Virus I have run into about 20-30 people over the last couple weeks that were having trouble sysprepping and they all narrowed it down to the same thing; th...
Install WAIK supplement for Windows 7 SP1 WAIK Supplement These are instructions for installing the new The Windows Automated Installation Kit (AIK) for Windows 7 SP1. This is assuming that y...
READ ALSO  Deploy LGPO with MDT 2013
  • Dave Keiner

    This is great for 32-Bit. Are the steps for creating a 64-Bit version the same or does it require a different setup because of compatibility issues?

  • Dave Keiner

    I’m not a script writer by any means. I appreciate you guys compiling these for us who aren’t actual scriptors. My next question involves customizing with programs. Could you explain the commands that I would need, or if it is even possible, to mount some random useful programs to this PE that I could add for things like password recovery or reset of a local administrator account?

    I ask because I also use Hiren’s boot for tools in a mini Windows XP environment. Is there a way to configure this to include some of those useful programs? My main focus is creating a 64-bit version that I could use as an “all in one tool”. Thanks for all you’ve done so far.

  • may

    can you please re-upload file

  • @may: The download seems to be fine. I am at work right now and downloaded it. Here is direct link: / If you have any other questions feel free to ask.

  • karon

    I can’t figure out where to add this to the winpe_x86 ….I tried just adding it to the boot disk, and my disk booted, but only with a command prompt, not with the winpe3.1 environment…am starting completely over but still don’t see where to put the files from this download

    • karon

      never mind, I got it……this is all new to me, we were doing clonezilla, and our clone server crashed and so we are trying a brand new way………and sigh……never mind…I think I finally got it 🙂

  • Norm

    Can this be used to capture a x64 image too? I’m trying to get a windows 7 deployment to work.

    • Yes, this can be used to capture a x32 and x64 images.

  • John Nobbs

    Just a quick question – I recently went through the steps of sysprepping a Windows 7 machine up to the point of booting to your WinPE 3.1 boot environment (using your awesome tutorials of course =D). The IT Bros’ WinPE 3.1 Loader came up fine, excelt when I tried to use the #2 option of GImagex, a quick popup would appear and disappear and I would be back in the X:WindowsSystem32 prompt. I could of course type imager to go back to the menu, but GImagex just wouldn’t seem to run. Any suggestions as to why this may be happening? And do you think that I could simply use Norton Ghost to make an image of the sysprep (if we can’t figure out what the problem is)?

    Thanks for everything you guys do!

  • Niels

    Hey John Nobbs,

    Experiencing the same problem! Let’s hope someone knows a solution.

  • Jordan

    Is it possible to integrate user-friendly GUI file manager to WinPE 3.1? I think that it will be very useful 🙂

  • Khat

    When you WinPE, is this not going to be included in the images you are going to deploy. I am curious because I am going to be deploying Windows7 machines 2 days. I have not done sysprep before but I have been following your instructions on how to do it. As of now, it is pretty much simple but when it comes to WinPE part and the rest, it doesn’t rhym with me there. Thanks

  • Alan

    To the users selecting option 2 GImagex and quick screen – a share on the server w/perms and bat needs to be edited to map drive q to server in order to load the gimagex.

    I am trying to deploy win7 64, and receive message “The subsystem needed to support the image type is not present”. Any ideas? I prepared wim using amd64.


    Alan 🙂

  • Amy


    Your tutorials have been very helpful, but I was wondering if you get time, if you’d do a tutorial on how you get the drivers into the WinPE scripts. I have drivers that I’d like to add but when I add them in step 5 of the DISM it goes through the process but it always says an error occurred when it is adding my drivers from my folder. Everything else works great. Thanks for doing and keeping ITBros up and running!

  • Ken

    I cant seem to get the network connectivity. Getting a message “The Workstation Service has not been started” any insight?

  • Antoine


    First off, let me say this is an AWESOME post. I am new to Windows Deployment/Imaging so this type concise, easy to digest information, with examples, is great. However, I have a few questions (sorry I’m a newb).

    1) Where do we get the INF drivers? Would these be the drivers that came with the machine (i.e. C:\Drivers) or are there a set of drivers you provided? Should these be copied to C:\winpe_x86?

    2)What do we do with the contents of the WinPE 3.1 Contents Zip? Should this be copied to C:\winpe_x86?

    Any feedback would be greatly appreciated.


  • jim

    I backup my Windows 7 32bit with driveimagexml, is it possible to make a bootable WinPE with driveimagexml? Can you guide me please? Thank you.

  • topmoo

    Where does sysprep save the WIM file that you have customized? I cannot get past the imagex area where i save the customized Image, but i just cannot find that image or find where to look.


  • Bubba2413

    IT Bros! MOST Excellent blog. Extremely helpful! Thanks, thanks, THANKS!

    Driver comment/blog entry suggestion.

    Perhaps, I’m overthinking this, but I’d like to know how you arrived at all the drivers to inject, and just as importantly, how you define installation order (or if you even do). I’m mostly interested in Dell, but also HP and Lenovo (if you’ve ever messed with them…)

    Let me explain. Lets say you have a Dell Latitude whatever. Going to the dell driver download page, there are a couple of driver bundles, as well as each individual driver package. But there is also a Latitude E-Series Driver installation guide that indicates that driver installation order is critical. If you download the individual driver packs and extract them, they generally go into C:\Dell\drivers\ with each driver in a sub-directory labeled R######.

    So… the questions:
    1. Do you simply point the base of the driver WIM injection command to the C:\Dell directory (after removing all of the unrelated OS subdirs)? And
    2. How do you ensure that Windows will install them in the correct order? (or has it just always worked out?)
    3. Have you had occasion to run across similar driver bundles for HP and/or Lenovo?

    Thanks in advance!

  • Ben

    Thanks so much for the tutorial.. this cloning thumbdrive has saved me numerous times so far.

    Question though, what is the correct procedure in adding new drivers? And for what OS should the drivers be for.. I assume Win7 but I wanted to verify. Thanks so much!

  • Jonathan

    Just a friendly reminder that when adding WinPE drivers make sure you are using VISTA drivers or WinPE drivers if provided by the manufacturer. You don’t want to use Windows 7 drivers for WinPE!

    • brandnubian

      Are you sure about this? I thought you were supposed to use Windows /Vista or 2008 drivers? can somebody please confirm.

  • LAZA

    The script seems gone… 🙁 Tried it with Windows XP/Firefox 6 and Server 2008/IE8 – always the same result. I looked on the page itself you gave ( and none!
    Would you please upload that script again, it would be most preferable!!
    Thanks in advance and for this good blog.

  • Jose

    Hi everyone,
    Does anyone have the WinPE3.1 [Pre-Compiled with GImageX App] iso for 64bit? I’m deploying about 100 Dell’s 790 models 64bit systems. I can also use a link to the dell driver’s pack if anyone has that as well. Thank you.

  • Paul

    What I can’t seem to figure out is whether this guide is (1) supposed to make the USB key bootable in some way, and (2) whether this is WinPE 3.1 in its entirety, or if that is located somewhere else. Just following the guide and then taking the contents of the two files given and copying them to the drive results in “Remove disks or other media” “Press any key to restart”.

  • Murtaza Alibhai

    Download link for both the scripts and drivers not working, please check or let me know another site I can download from

  • rkim

    Is this site not being updated?… link doesn’t work

    • We took a break from this site, but are back now and updating all the content. Links should work now.

  • Adam

    Still returning a 404 error! Please can you re-upload or sent a direct link?

  • Enzio Francescoli

    Hi Brian, Thanks for this information as I wanted to do this for myself but could not find much info on this. Apart from ading more options, the only thing I did was change the numbers to letters to make it really easy to have more options.

    Best Wishes

  • Seven

    Could you please reupload the .zip? Getting a 404 🙁

  • alex greimann
  • @Walt: This has been fixed.

  • Sean Dailey

    How can I load driverse into this so I can use it on a raid card

    I don’t understand how to use that zip file to get GimageX on a raid card if the drivers are not included.

    please let me know! thanks 🙂

  • Harry Tapp

    Where are the links to download the scripts?

    • Harry Tapp

      I think I have answered my own question…The scripts (*.bat) are compiled in the download. I suspect that eve though the dowmload says “x86 ii will still work in x64 boot environments. I just made a copy of your unpacked zip and changed x86 tox64 then added the respective files from Windows AIK and the when creating a custom pe boot disk use the correct respective pe.wim file.

      • Yes for the WinPE environment and using GimageX the x86 will work fine on x64 hardware. Glad you found the download link 🙂

        • Harry Tapp

          Thanks for the quick response, there is a misunderstanding. The issue is not the hardware it is gimagex x86 will not run in an x64 bit pe environment. It works fine on a fully installed win 7×64 os with a functioning 32bit sub system.

  • Ben Hart

    Brian, First off I have massive man-love for you because of this article. Secondly should your procedure above work for AHCI drives? Also.. any plans on updating the article or composing a new one for Win8?


  • disqus_ZTd1NJNWwV

    Brian, I have been having a lot of trouble getting a Windows 7 Enterprise 64 image to work. What I have not seen on your tutorial or any others including Microsoft is mention of the fact that ImageX and GimageX do not take a complete image of a reference computer. As near as I can tell, you have to actually capture the image twice. One is the “System Reserved” 300mb partition and the second is the window partition. This is not made clear on any sites that I have seen. Do you have any plans to add that to your diskpart utility in WinPE 3.1? Also, do you still have the Ghost script. We are trying to move over from Ghost and I need to go back and forth in order to do the full conversion away from Ghost.

    Thank you.

  • disqus_ZTd1NJNWwV

    Brian, I have been trying to find a tutorial on imaging a computer like Ghost does. That information has been a bit vague. It would be useful if you added a change to the diskpart script similar to what Microsoft has posted on this page:

    Also in running your BCDEdit/BootMgr script I get a can not find configuration data store error. It has not been clear how one handles the system reserved 300mb partition but the above mentioned Microsoft page says that BCDBoot must be run to create the boot files. Capturing an image of a computer that has that already and then applying that image to another box apparently does not work.

    I would like to suggest/request that you add an option to your menu to create that bootmanager partition.

    With that and your other items it would be much easier to clone a computer.

    Thank you.

    • Good point. On an interesting note we can add you as a guest writer if you would like to write it for us?

      • disqus_ZTd1NJNWwV

        Hello Brian.
        Intriguing thought, what would you like me to write?

        I did run across a thread in another forum that seemed to work.

        I had to run:
        BCDBoot.exe X:Windows /s E:
        where X is the ramdisk that WinPE loads into and E: is the drive letter that my newly imaged drive acquired. That then made the image bootable and worked. Your fixboot batch file should work but for some reason BCDEdit can not find a bcd store.

        What I would find particularly useful would be either a script for discpart to partition and format efi drives as well as the bios drives you have the batch file for. It would be nice if the script could detect the configuration (bios or efi) and set it up accordingly but I suspect that would be a lot of work and then what do you do if you want to change from efi back to bios.

        Are you planning another article on WinPE5? I do enjoy your articles. They are very informative. I rely on them quite a lot.