Monday, January 28, 2013 11:00 PM
I am running Windows PE with Imagex off of a bootable UFD. I used technet articles to create my UFD.
I am trying to capture a sysprepped image, and it has worked before. Here is the problem. When I run my command the capture runs, but it only takes about 3 seconds and gives me no error messages. In the past it has taken 15 or so minutes. When I check to see if the image has been captured there is nothing in my c drive where I am telling it to go. Like I said I have used this command before and it has worked.
I am capturing a Windows 7 32-bit image and my Windows PE has the x86 drivers. I thought that maybe my image was bad, so I reworked my image, and the same thing is happening. I also remade my bootable UFD. I'm not sure what is going on. I just started working with all of this about 2 weeks ago, so i'm very new at using windows pe and imagex. I do not have the ability to copy it to a network drive. Is it a problem with c:\ not being mounted when booting into RAM? If so why did it work before?
The command I am using is as follows;
imagex /capture c:\ c:\install.wim "FinalImage" /verify
Does anyone have any ideas? Thank you for your time.
Tuesday, January 29, 2013 3:41 PMI figured it out, from reading some other articles. Apparently my PE environment reassign D to my C drive and I wasn't imaging the correct drive. Honestly I'm not sure why that happened. I had created two images prior to this time and both times it was my C drive. Anyway thank you everyone who looked into this for me.
- Marked As Answer by Vincent Wang-MCSCMicrosoft Contingent Staff, Moderator Wednesday, January 30, 2013 6:19 AM
Wednesday, January 30, 2013 6:19 AMModerator