Capture and Deploy Image Without Sysprep


If you are using WinPE 2.0 or WinPE 3.0 to capture your PC images (.wim files) and deploy them you have probably run into a little problem when trying to deploy an image of Vista or Windows 7 when not first running sysprep. The problem is that if you try to re-deploy an image of a nonsysprepped image of Vista or 7 that the BootMGR will be broken. Follow the steps below to fix this problem.

Step 1

I am assuming you have captured your image already and are ready for deployment. Go ahead and boot up your image deployment software (WinPE 2.0 or WinPE 3.0).

Step 2

In my other articles I describe how to use DiskPart and also avoiding the hidden partition before deploying a new image. I suggest reading them.

Step 3

After you have deployed your non-sysprepped image you need to run the following commands: (I have a batch file I use to do this).

bcdedit /set {default} device partition=c:
bcdedit /set {default} osdevice partition=c:
bcdedit /set {bootmgr} device partition=c:</blockquote>

Step 4

This will fix the BOOTMGR problem when deploying a non-syprepped image in Vista or 7. Enjoy!

Incoming search terms:

  • sccm 2012 capture image without sysprep
  • capture image without sysprep
  • capture wim without sysprep
  • wds capture image without sysprep
  • wds without sysprep
  • APagano

    Well, I ran through all three articles – diskpart, hidden partition, and this one – and I am not able to get the bcdedit option to work, it keeps throwing me ” The boot configuration store could not be opened. The system cannot find the file specified.” I am entering the commands as written. Just wondering if you had any thoughts on this – I will review the afore mentioned articles to see if I missed something and then move onto looking for answers in the web. Thanks for any help you guys can offer :)

  • Mike

    I was playing around with your WinPE scripts and ran the selected the menu option that runs the commands listed above… only problem was that I did that on a machine that has both a reserved partition and a windows parition – whoops! Is this going to mess anything up? Upon rebooting windows repair ran and did some tests and verified that everything was ok. After that, windows booted up fine.

    So, I was wondering if I run those commands, do I need to run anything else to revert things back to normal, or is all still good?


  • JazziJessi

    I have followed the sysprep and winpe docs and all was going well for my Windows 7 64bit image. The custom sysprep works well. I created the winpe iso but it only boots to a flashing non responsive command prompt not the GImageX App. Any suggestions?

  • Haxcid

    completely failed for me. I deployed a non sysprepped image and like apagano the bcd fix does not work.

    also the reference to other docs… put a link because I am not clear what previous entries you are referring to. There are a mention of 3 articles but which 3. I would really like to get this to work. Sysprep screws up our image horridly by resetting half the settings and tweaks we do to our systems.

  • Pingback: Win 7 - win 7 64 imagen - MCSE Forum

  • Clark

    Its my understanding that Windows PE does not have Boot Rec utility installed by default. So if one is booting from Windows PE one cannot run the BCD option of Boot Rec in the Command Prompt.One could create a Boot Rec plugin for Windows PE by installing the four files that Bootrec needs to run.They are Bootrec.exe, Bootrec.exe.mui,Wer.dll and Wer.dll.mui. These can be found in the Boot.wim of a Windows 7 recovery disk.Once its mounted one can find these files in the Windows\system 32 folder and copy these to the same folder in the Windows PE Bootwim file. I may create one to see if this works.