I recently compiled a new library of commands since the upgrade from WinPE 2.0 to WinPE 3.0. With Windows 7 coming along they released a new way to create bootable USB sticks using Deployment Image Servicing and Management (DISM.exe). You might be asking yourself, what could I use this for? We are using it at my work to re-image computers, capture backup images, mount images, etc. There are many other uses for it but I will not get into that here. I have literally done this procedure a couple hundred times. In a future article I will show you how to write a simple batch script to automate this process. But it helps to understand what is going on with each command in case you have trouble. Batch scripts never work 100% of the time.
You will need the following to proceed:
Windows® Automated Installation Kit (AIK) for Windows® 7 RC (Download from Microsoft) : 05.01.09
Once you have installed WAIK then you will need to browse to your start menu and click on “Deployment Tools Command Prompt”. I have provided a picture below.
DISM
Once you have launched DTCP you will need to follow through the commands I have compiled below. The first one I have provided a screenshot.
DISM – Step #1 – Prep/Cleanup
DISM /Cleanup-Wim
The DISM cleanup command simply cleans up any previous wims/mounts you have been working with. If you do this a lot, you will need to use this command otherwise you will start receiving errors from previous wims possibly still left on the system.
DISM Step #1
DISM – Step #2 – Copy WinPE 3.0 to your local C Drive
copype.cmd x86 c:\winpe_x86
copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim
This creates a winpe_x86 folder on your C: drive and then copies the contents of the WinPE folder from the WAIK installation to your folder.
DISM – Step #3 – Mounting .Wim File on your local C Drive
Dism /Mount-Wim /WimFile:C:\winpe_x86\winpe.wim /index:1 /MountDir:C:\winpe_x86\mount
This command mounts the wim file that was copied over in step #2 so that you can browse the system32 folder and insert your custom scripts, etc.
DISM – Step #4 – Adding Packages to your WIM
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab”
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab”
There are many packages you can add to your WINPE boot environment, these are two I always add to mine.
DISM – Step #5 – Adding Drivers to WinPE
DISM /image:c:\winpe_x86\mount /Add-Driver /driver:C:\YOUR_FOLDER_OF_INF_DRIVERS\ /recurse
A nice addition to DISM over the previous peimg command in WINPE 2.0 is the ability to add drivers with the /recurse command. The /recurse command now allows us to simply have all of our drivers in their own directory and tell DISM to scan the root folder and everything beneath it. The number of sub directories won’t matter. I have a huge library of drivers, for example, you will want to have the network and vga drivers for anything that you boot up to in the WinPE environment. By adding the network driver to your WinPE boot environment, it allows you to access network shares for capturing and deploying .wim images.
DISM – Step #6 – Adding Custom Scripts, Batch Files, Etc.
xcopy /e /y “C:\YOUR_FOLDER_OF_SCRIPTS” C:\winpe_x86\mount\Windows\System32\
Without adding anything to your WinPE boot environment you will simply be left with a command prompt window when booting to it on a computer. I have added over 15 different batch scripts with different functions. Click here to download my WinPE discs. One thing I highly suggest adding is GImageX. GImageX is a very small GUI program that you can add to be able to capture, deploy, and mount images within the WinPE boot environment. I have provided a picture of GImageX GUI below.
For WinPE 3.0 Boot Environment - Mount, Deploy, Capture Images
DISM – Step #7 – Unmounting your finished .WIM
Dism /Unmount-Wim /MountDir:C:\winpe_x86\mount\ /Commit
This commits the final changes to your .WIM file and anything you added to it. It is very important to unmount your .WIM file when you have finished.
DISM – Step #8 – Copies your .WIM to Boot ISO
copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim /Y
DISM – Step #9 – Creates bootable .ISO of WinPE 3.0
oscdimg -n -bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso
Now, if you are wanting to use a flash stick you will need to format a flash stick in a certain way, and then simply copy the contents of the c:\winpe_x86\ISO\ to your flash drive. And thats it! Stick it in a computer, restart, and boot to it. The .ISO made in step #9 can simply be burned to a CD with Nero or other program capable of making bootable CD and then you can boot to it in the same way.
DISM – Step #10 – Optional Backup
xcopy /e /y “C:\winpe_x86″ E:\BACKUP_FOLDER_FOR_LATEST_BOOT_BUILD\
This step is optional, but I always like to keep a backup for the future. Also, if you ever need to create another bootable flash stick or CD you can simply go to your backup and grab the files.
Tags: Batch Script, GimageX, ImageX, Microsoft, Windows 7, Windows Vista, Windows XP, xcopy
The instructions work great.
I was following msdn’s instructions and could get it to work.
Thanks a lot!
I’m glad the instructions were helpful. If you have any questions about them just let me know.
[...] http://blog.brianleejackson.com/deployment-image-servicing-and-management-dism-winpe-3-0-boot-enviro... [...]
These are great instructions. I am just getting into WAIK and winPe 2.0, it was nice to find an updated link to the 7RC/WinPE 3.0 install. Are you still planning to upload some of your custom scripts? It would be nice to see how other people are attacking their imaging process. We just migrated to Vista images because we have highly powerful Revit/AutoCAD desktops with drivers that Ghost does not support. this works great, ut currently I use everything from the CMD prompt in winPE 2.0.
Thanks!
Sorry for the delay in my response, yes I am uploading my scripts as we speak so that people can download them and see how I have tackled the imaging process. Last Thursday and Friday we re-imaged 52 computers; upgrading them to Windows 7 with brand new sysprepped image (that tutorial coming soon) using only my WinPE 3.0 boot environment disc and scripts. Made the process very easy and fast. Took only about 5 minutes to deploy to Dell GX755’s. I have created new links on the right hand side of my blog called WinPE 3.0 and MSI Packages. Feel free to look in there for what you need. If you have any questions please feel free to ask.
Great docs…looking forward to trying WinPE 3.0
Question for you – how did you get ImageX / GImageX into the WinPE and implement the filters so as to be able to mount WIM’s?
I know – n00b question, sorry…
I have my 2.0 working all except that – and I just cant seem to google a straight answer on how to fix it.
Thanks in advance.
There is never a noob question when it comes to WinPE
We all started there at one point. I’m assuming you want to mount WIMs you have taken on another computer? Just to clarify, there is a difference between mounting a WIM file and applying a WIM file. Applying a WIM file would be if you have an image you want to apply to another computer. Mounting a WIM file means you probably want to insert drivers, or you have WIM backup and you want to extract data from your backup WIM, etc. Mounted WIMs have read/write access so you can actually change almost anything you want in your image and save the changes to your mounted WIM. You can mount WIMs using the Imagex commands, however I highly recommend using Gimagex which is simply a GUI for Imagex. (http://www.autoitscript.com/gimagex/) On the computer you want to mount the WIM to look at, make sure you download WAIK and install it. There is a new version as of 08/06/09. (http://www.microsoft.com/downloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en) Once you have WAIK installed, then install Gimagex App. Launch the GimageX app and then you can go to the Mount Tab and mount your WIM file. If that doesn’t fully answer your question feel free to ask. Have a great evening.
Let me clarify a bit.
I had the WAIK installed on a PC, and can perform all functions on/with a WIM from there with out issue.
I am having to reinstall WAIK on a new PC (test machine DIED) – and I dont remember what I had to do to make the mounting work… I think it had something to do with filters? (mounting gives error re: file not found, but it is)
Thats one thing…
The other was I built a WinPE on a 64GB flash drive, and it is what I use for image development (capture, apply to test, etc). What I want to to be able to do is to R/W Mount a WIM that is on the flash drive to a folder on the flash drive from GImageX.
Why?
Case example – image is done, ready… and someone reminds me that the Custom11.prf file needs a modification as the mail server has changed in the environment. I just want to mount the WIM, go out to the file, modify it, and commit changes.
Any help / guidance would be greatly appreciated.
What OS are you running? With Vista or Windows 7, there are no filters necessary to be able to mount WIMs. All you need is the newest version of WAIK and GimageX. If you are still running Windows XP then yes, you do have to install some extra components, I think, to make the mounting work. I do all my mounting/editing WIMs on a Windows 7 workstation. I had never actually tried mounting a WIM and editing it all on the same flash drive before. I just tried it and didn’t have any problems. You have to mount the image and pick a mount point (flash drive). Let me know if you are still having issues on your end and I’ll see what i can do to help you out. Good luck.
Thanks for the guide – has been a good start.
I am running Windows 7 Enterprise x64 Edition and have the latest WAIK
I am having major issues trying to get an PE image with imagex copied into and also some network card drivers present in order to capture an image.
Have followed the instructions and can get a PE environment to boot successfully but, the customisations have not committed to the PE image.
I have been trying to achieve this for a 64bit deployment in mind.
To get back to basics I have decided to try a 32bit version and then build from there.
I’ve used your steps as a guide and I’ve noticed that I get two errors throughout the process:
Dism /image:C:\winpe_x86\mount/Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab
Returns me the error:
DISM doesn’t recognize the command-line option “Files\Windows”.
And adding the drivers:
DISM /image:c:\winpe_x86\mount /Add-Driver /driver:C:\drivers\ /recurse
Returns me the error of:Searching for driver packages to install…
Found 2 driver package(s) to install.
Installing 1 of 2 – C:\drivers\netadapter.inf: Error – An error occurred. The driver package could not be installed
For more information, check for log files in the \inf folder of the target image.
Installing 2 of 2 – C:\drivers\netbridge.inf: Error – An error occurred. The driver package could not be installed
For more information, check for log files in the \inf folder of the target image.
Error: 2
Any suggestions
Jason V, I had the same problem and it is related to the spaces in the folder name. The fix for this is to find out what the DOS Shortname of the folder is. You can do this by opening a command prompt and then CD program files and then typing dir /x to find the DOS folder names.
For me, the Windows AIK folder was called WI4A4E~1. For you, it might be the same, but it is good to check.
Then, you simply change the command accordingly:
sm /image:C:\winpe_x86\mount/Add-Package /PackagePath:”C:\Progra~1\WI4A4E~1\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab
And there you go!
Thanks for helping out Jason V with the error. I’ve started to get overwhelmed with comments on my blog relating to WinPE, DISM, Windows7, etc.
HELP!! did what mark said the command went through but now im getting this error !
any ideas ??
I gave rights all folder and still no luck, running AIK on Win7 RTM
Error: 2
Unable to access the image.
Make sure that the image path and the Windows dircetory for the image exist and you have Read permissions on the folder.
@Phill
At what point in the process are you getting this error? In what step? (Look in article for step numbers) It sounds like something might be interfering with your mounted WIM during the creation process. Maybe knowing what step that appears at might help me be able to solve your problem a little quicker.
hey Brian,
It happens when i try and do step 4, using the DOS shortnames
dism /image:C:\winpe_x86\mount/Add-Package /PackagePath:”C:\Progra~1\WI4A4E~1\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab
@Phil : That is a puzzling one. I have never even used the DOS short names before. You shouldn’t have to. I am going to recompile my WinPE environment and I will try to reproduce your error. I’ll let you know if I come up with anything.
@Brian: i fugured it !! i had to be in the C:\Progra~1\WI4A4E~1\Tools\PETools\x86\WinPE_FPs root and then just run winpe-wmi.cab in its short name as well.. all is working fine now.. thanks again
anyone know whats the main difference between doing this vs. using winbuilder (Win7PE)
is that just a automated way of making a PE disk !!
@Phil: Glad you got it working! I will make a note of that. I am not familiar with Win7PE, I will have to check it out. Do you have a link to Win7PE Phil?
Just to throw in my two cents, I had the same issue and the problem was simply with the quotation marks..the first set was facing backwards
Hello Brian, Great info here.
How do you add your gimageX package to my WIM. I’ve been able to add packages from
DISM – Step #4 – Adding Packages to your WIM
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab”
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab”
I’ve dowloaded your GimageX zip file but can you complete or correct the syntax for me to add this?
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\folder name\file name.ext”
thanks,
I am referring to your downloadable WinPE3.0_Contents_x86 [Pre-Compiled with GImageX App] that I am having trouble adding this to my WIM file.
thanks,
I’ll throw in another two cents. After experiencing a substantial amount of frustration trying to make BartPE universally bootable from USB on our various equipment at work, I tried out WinPE 3.0 about 6 months ago. It saved my sanity.
Using a base build I was able to boot everything we had. Desktops, laptops and tablets all booted into the WinPE 3.0 environment without a problem.
As we already have a single hardware independent image, the next thing to do was to write a front-end to simplify the process for our contractors who replace PC’s on a nightly basis (We are a large company and replace about 50 a night just to keep up on the 4 year rotation).
I wanted to write the front-end in Visual Studio but .Net is not supported in the booted PE environment so now what? Solution: AutoIt.
AutoIt applications work very well in the WinPE boot environment and where I need them, I can call vbscripts from the AutoIt front-end.
Now it’s boot, click on target drive and drop the HII. Dropping a 1.5 GB image in about 2-1/2 minutes from a USB is a beautiful thing. Suddenly the PXE servers are lonely.
@Bob : Are you trying to add the GimageX application to your boot disc? Or are you trying to add the driver package to the WIM? If you are adding driver package, then here is correct syntax (shown in step 5):
DISM /image:c:\winpe_x86\mount /Add-Driver /driver:C:\YOUR_FOLDER_OF_INF_DRIVERS\ /recurse
If you are trying to add the GimageX app you do this very last thing (shown in step 6). You can basically just copy the EXE over. If you have any additional questions feel free to ask. I hope that answered your question correctly.
@ Bob : If you are trying to add “WinPE3.0_Contents_x86″ contents please refer to step #6 in article above.
Example:
Copy the unzipped “WinPE3.0_Contents_x86″ folder to the root of your C: drive
then in step #6 you would run this command:
xcopy /e /y “C:\WinPE3.0_Contents_x86” C:\winpe_x86\mount\Windows\System32\
That should work for you. Just make sure you do all 1-5 steps first before doing this. Let me know how that works for you
@ Alan: That is awesome Alan. Sounds like you had similar experience I was having. When I first arrived at my workplace they were still using GHOST to image and deploy. I then took up the project with the WinPE and have never looked back
I’m hoping to get time to work with the single hardware independent image. Any tips to save me time with the single hardware independent image?? And yes, deploying from USB stick is amazing 
I deploy from USB stick on my own personal computers and it is about as slick as butter! Couldn’t be happier. I’m also hoping to re-design this blog site as I am now getting over 15 comments per day. I don’t have time to answer all the questions lol. Have a great night!
[...] deploy it after the sysprep reboots the computer. Tutorial on creating WinPE 3.0 Boot environment: Deployment Image Servicing and Management (DISM) – WinPE 3.0 Boot Environment – Blog.BrianLeeJ… Free Pre-Complied WinPE 3.0 Boot environment scripts: WinPE 3.0 Boot Environment Scripts – [...]
boa tarde estou com um problema no winpe como é que eu consigo chama net use por ele
pois ele mim dez que a rede não está presente ou não foi instalada como é que eu instalo esses driver.
@Philipe : Sorry but I don’t speak Spanish…. I tried translating it online but did not succeed. Can you please translate to English and I might be able to help you. Thanks
@ Brian: My Portuguese is very rusty but here’s how I translate Philipe’s question:
Good afternoon. I have a problem with winpe. How can I call “net use” with it? Because it tells me that the network isn’t present or wasn’t installed. How can I install this driver?
@ Philipe: Thanks to Jim H for translation.
First check to see if you are getting an IP address. If not, and
you can’t call a net use then it is because your network card drive is not
in your WinPE environment. First give me the computer name and model. You
will need to inject that driver while building the WinPE 3.0. You should
be able to download it from the manufacturer’s website.
Dear Brian
Thx for your step-by-step instructions, they are helpful
I try to add some network-drivers to a WIM-Image but get always Error: 1815
“Die angegebene Sprachkennung für die Ressourcen wurde nicht in der Image-Datei gefunden.”
Sorry, have it only in german
Do you have an idea?
How do you install the cutom IMAGE that was created using your process? I feel so lost with this new way
@Chris G: Is there any way you can get me a translation of this error?
@LostinIMAGEX : Lol, I like your name. Have you read through my article on “Sysprepping Windows 7 from start to finish”?? I am assuming you haven’t because that answers a lot of people’s questions. http://blog.brianleejackson.com/sysprep-a-windows-7-machine-start-to-finish I should probably re-arrange this blog a little bit with the most popular articles at the top.
@LostinIMAGEX : Also, you should check out my WinPE 3.0 scripts that I have already pre-packaged. http://blog.brianleejackson.com/winpe-3-0-boot-environment-scripts
I am new to WinPE & WAIK. Few Queries here..
What could be the advantages to migrate from WinPE 2.1 vs WinPE 3.0?
Is DISM a replacement for ImageX?
Can anybody tell good tutorials / links on using Wimgapi.dll to use in C++?
When i run step 4 i keep getting this error. Any idea:
An error occurred trying to open – “C:\PROGRA~1\WI4A4E~1\Tools\PETools\amd64\WIN
PE_~1\WIDA6B~1.CAB” Error: 0×80070003
Error: 3
The system cannot find the path specified.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
When try to add packages in WIM, I get following error
c:\winpe_x86>Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Progra
mFiles\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab”
Error: 87
DISM doesn’t recognize the command-line option “AIK\Tools\PETools\x86\WinPE_FPs\
winpe-wmi.cab”".
For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
c:\winpe_x86>Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Progra
mFiles\WindowsAIK\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab”
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
An error occurred trying to open – “C:\ProgramFiles\WindowsAIK\Tools\PETools\x86
\WinPE_FPs\en-us\winpe-wmi_en-us.cab” Error: 0×80070003
Error: 3
The system cannot find the path specified.
c:\winpe_x86>Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Progra
mFiles\WindowsAIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab”
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
An error occurred trying to open – “C:\ProgramFiles\WindowsAIK\Tools\PETools\x86
\WinPE_FPs\winpe-wmi.cab” Error: 0×80070003
Error: 3
The system cannot find the path specified.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Please help…..Also, It’s my first time trying something like this…..Just to be sure…i’m creating this Win PE on my personal computer and then once it’s done….i’ll build a new machine with windows 7 and tweak it to our requirements and tehn use this to build an image…..sorry but i’m a noob….
thanks for the help….
Hi Brian
Thanks very much for the guide, it has been most useful.
I have managed to create a Sysprep image for Win7 and have deployed it to a couple of workstations.
I took the sysprep from a Dell Vostro 420 Desktop and have had some success in restoring the image to another Vostro 420.
In the past I had a pretty good hardware independent sysprep of Windows XP to go on work Desktops therefore want to use this Win 7 image on other machines within our environment.
I have managed to deploy the image on a Vostro 1220 laptop with some success but on another attempt of the batch I get a Windows file missing error.
Bootvid.dll
Have you had any troubles with this in your deployment experiences ?
Thanks
How about a little more info on WinPE 3 for “super” beginners as tyhere is almost nothing at the true beginner level and even this blog assumes the user has had SOME experience with WinPE. I am at the “power level” user of experience with windows and happen to be the go to person when it comes to fixing stuff a.k.a. “make it work”.
I’d ultimately like a win PE with a gui preferably a windows type desktop and my rescue tools, just like they are now. I can use a command line but using the GUI is sometimes just easier or more intuitive for certain things.
I know a bit about things such as administrative snap ins and all that, but win PE is totally foreign to me (coming from a “just reinstall”, restore from an image or a sysprep install – for curiosity background)
The reason I ask is that I have a few beginner questions.
I’d like to boot into a gui shell like winbuilder, but want to build it myself so as to choose my own apps and not do a hack job or “frankenscript” some sort of half baked mess.
How do I:
Add a desktop ?
Install my own 3rd party apps (Avast and Trueimage for example ?)
- do i just install them to the .vhd after I mount it and boot off of the PE ?
-What about registry info and serial numbers if I don’t just install to the running PE
- do I modify the boot menu to boot off the .vhd file? How ?
- I assume that I just repackage stuff to a .wim file somehow like your blog says after my stuff is installed.
It’s simple basics like this that are going to stump many beginning WinPE users who are just doing this at home for fun.
@Pramod Kulkarni : One big advantage I found with WinPE 3.0 is when injecting drivers. DISM uses a recursive command that searches your root folder for the INF files and automatically injects them. DISM is not a replacement for ImageX, they are two totally different things. You would still want to use ImageX for capturing and deploying images. I have not worked much with the wimgapi.dll, sorry. Good luck!
@Thierry: Have you verified that the file is actually in that location??
Which one is this happening on??
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab”
OR
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab”
I’ll try to help as much as I can…
@Vaneet : Make sure you have spaces and quotation marks in correct places, I know a few other people were having issues with this and it was because there was either an extra space or missing quotation mark somewhere.
@ Gavin: Funny you brought this up, I was doing some testing at work last week with images trying to get the hardware independent images working and discovered they were already working!! I have 20 images and immediately that was cut down to two images. Epic! I deployed a Dell Latitude D620 image to a Dell GX755
. So now I have two images, a 32 bit Windows 7 ENT, and 64 bit Windows 7 ENT. Works on all dell models, Asus netbooks, etc. If you are receiving an error like that it is most likely that you just need to inject an additional driver into your image. The cool thing is, this is very easy and you don’t have to redo your image at all. What you need to do is mount your finished image and then inject the driver, the steps are the same as in above tutorial, just you are doing it with an already finished image. I would recommend using GimageX app to mount with read/write changes enabled and the commit your changes when you are done injecting your drivers.
@Thomas Lukins: Ya unfortunately this was written towards more of a large business standpoint for WinPE. I am actually trying to find time to work on a GUI for WinPE 3.0 and GimageX that would integrate everything into one small thing. I think it would be amazing. And it would definitely be very popular. For me, I am currently a full time student plus working almost 40 hours a week and so I just don’t have much time for extra projects like writing a small GUI app. Once I graduate I would love to do this.
Thanks Brian, I think it would be great for cleaning up messed up computers, and since I am looking off your awesomely helpful blog, I will gladly forward to you anything I find out on the best ways to do this.
Also the resource kit was a great tip, it fills in a lot of the simple stuff for noobs like myself. Any advice on an easy book on learning to write scripts for this type of enviornment ?
Brian -
WinPE 3.0 Rookie
Thank you for all the information you have provided for WinPE 3.0 it has been very helpful. With your guides I have been able to create bootable USB devices and CD’s. I have also created a couple of images (1 with the boot option) but I am running into a problem when I apply the images. I have been using the GIamgex interface to create the images and apply the images. I first run the “Format Disk with DiskPart” option then apply the image everything appears to work fine, but when I reboot I receive a BOOTMGR is missing error. I then try to run the BCDEdit/BootMGR option. This option returns the following errors:
bcdedit /set {default} device partition=c:
The boot configuration data store could not be opened
The system could not find the file specified.
bcdedit /set {default} osdevice partition=c:
The boot configuration data store could not be opened
The system could not find the file specified.
bcdedit /set {bootmgr} device partition=c:
The boot configuration data store could not be opened
The system could not find the file specified.
Do I need to make some changes to the fixboot.bat you supplied or can you tell if I am doing something else wrong? I am running Windows 7 Enterprise both 32bit and 64bit. Any help you can provide would greatly be appreciated.
Thanks,
Roger
Brian,
Which folder do you use for standard intel x86_64 systems?
Lance
Brian,
Let me preface this with a gigantic “thanks!” Things have gone from making no sense at all to making broken sense!
Here’s an example of my broken sense:
I’m using MDT (which I know you are not) and have added drivers for several Dell models into the “Out-of-box drivers.” When I “update the Deployment share” a new wim/iso are created. When I go about adding your WinPE scripts and such, I mount that wim that I created from MDT.
When I’m running the /Add-Driver command as part of the mounting process, are the drivers loaded into this portion strictly for the WinPE experience or do they make their way into Windows? Do the drivers I add in MDT make it into Windows? I’m wondering if things I’m doing are redundant.
I’m hoping that one of the driver additions makes it into Windows so I can have my universal image (which I am having -some- luck with but feel I may simply be getting lucky). Currently, I’m using the same image created from an e4300 and applying it to D630’s, etc. When I find a driver that’s not automatically found, I go back to MDT and add it to the repository.
I’ll stop rambling – thank you so much for everything you’ve done. I’ll be making a well earned contribution this evening.
Brian –
WinPE and Imagex Rookie
Thank you for all the information you have provided for WinPE 3.0 and Imagex. With your information I have been able to create bootable USB devices and CD’s. I have also created a couple of images (1 with the boot option) but I am running into a problem when I apply the images. I have been using the GIamgex interface to create the images and apply the images. Everything appears to work fine, but after I reboot I receive a bootmgr error. I then try to run the BCDEdit/BootMGR option you provided. This option returns the following errors:
bcdedit /set {default} device partition=c:
The boot configuration store could not be opened
The system can not find the file specified
bcdedit /set {default} osdevice partition=c:
The boot configuration store could not be opened
The system can not find the file specified
bcdedit /set {bootmgr} device partition=c:
The boot configuration store could not be opened
The system can not find the file specified
I am running Windows 7 Enterprise both 32bit and 64bit. Any help you can provide would greatly be appreciated.
Thanks,
Roger