Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Building Standard Image - capture error

Answered Building Standard Image - capture error

  • Friday, November 13, 2009 11:14 PM
     
     
    Sign In to Vote
    1

    I am following the instructions to Building a Standard Image of Windows 7 Step-by-Step Guide
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=901663e1-934f-4793-8eae-7c0a1ccb83a5

    Capturing my customized installation of Windows 7 imagex fails:

     

    [ 79% ] Capturing progress: 5:22 mins remaining

    [ ERROR ] d:\Windows\winsxs\x86_microsoft-windows-mediaplayer-core_31bf3856as364e35_6.1.7600.20518_none_0c186845c94f7465\wmploc.DLL (Error = 112)

     

    Error imaging drive [d:\]

    There is not enough space on the disk.

     

    Where D:\ is the partition with the actual installation.
    I am using Windows 7 Enterprise downloaded from TechNet.


    Windows was originally installed on a 30GB partition. In the mean time I have extended the partition several times, and ultimately included the complete remainder of the drive of 110 GB.     Every time the exact same error was reproduced and now I am stuck.

     

    Any hints on possible solutions or workarounds would be very much appreciated. Thanks, clau

     

All Replies

  • Saturday, November 14, 2009 12:25 AM
     
     
    Sign In to Vote
    0
    Post the imagex command you used. There was not enough space for the target wim file I would assume.
     
  • Saturday, November 14, 2009 12:44 AM
     
     
    Sign In to Vote
    0

    Thanks for answering.

    I did as stated in     Building a Standard Image of Windows 7 Step-by-Step Guide
    http://technet.microsoft.com/en-us/library/ee523217(WS.10).aspx

    F:\imagex /compress fast /check /flags “Enterprise” /capture D: F:\install.wim “Windows 7 Enterprise” “Windows 7 Enterprise Custom”

    where F is the UDF and D the windows installation partition.

    with no better idea I just fired up my image again and System File Checker tool (sfc.exe) reports no errors.
    thanks, clau

     
  • Saturday, November 14, 2009 12:52 AM
     
     
    Sign In to Vote
    0

    Was f:\  the directory that ran out of space - and of course you ran sysprep generalize first.

     
  • Saturday, November 14, 2009 1:45 AM
     
     
    Sign In to Vote
    0
    f: was a 80 GB laptop hd connected via usb used as ufd.
    actually, thats what I thought first too. used space for the windows installation was 15.3 GB (just before sysprep), with 8.25 GB for a full system image, so I started with 16 GB size of the UDF.

    I had 5 attempts gradually increasing first the ufd to 32, 48 and the full 80 and second windows partition size from the original 30 to the full 110. At some point I even switched the UDF to yet another laptop drive.
    I hooked up the drives via usb to another machine to extend via windows 7 disk manager and ended up with the same error at 79%.

    yes, I ran sysprep. I am not much familiar with the procedure so I followed the guide closely. thanks, clau
    • Edited by claudh Saturday, November 14, 2009 3:20 PM
    •  
     
  • Saturday, November 14, 2009 1:59 AM
     
     
    Sign In to Vote
    0
    The only place your going to run out of space is the target where the .wim is stored. Increasing the system image partition would have no effect because if it works like it's supposed it will only capture the system image but not the entire partition. If the sytem image to capture is 16 GB your finished .wim should be under 3 GB. 

    imagex /compress maximum /flags "Ultimate" /capture g: d:\install.wim "Ultimate"

    Installing programs in audit mode after from a clean installation and running sysprep.
     
  • Saturday, November 14, 2009 3:45 PM
     
     
    Sign In to Vote
    0

    Did as suggested. Repartitioned and reinstalled Win7 on a 30 GB partition, installed all apps in audit mode, left the udf at the full 80 GB.

    Now, three hours later, capture returns:
    [ 77% ] Capturing progress: 5:42 mins remaining
    [ ERROR ] d:\Windows\winsxs\x86_microsoft-windows-iis-ftpsvc_31bf3856ad364e35_6.1.7600.16385_none_4a416cb5f6f47883\ftpsvc.dll (Error = 112)


    Error imaging drive [d:\]

    There is not enough space on the disk.

     

    Where d:\ is the partition containing the windows installation. used space of the installation was 14.4 GB.

    thanks, clau

     
  • Saturday, November 14, 2009 4:22 PM
     
     
    Sign In to Vote
    0

    Re-tried capture using suggested maximum compression

    f:\imagex /compress maximum /flags "Enterprise" /capture d: f:\install.wim "Windows 7 Enterprise" "Windows 7 Enterprise Custom"

     

    [ 89% ] Capturing progress: 2:54 mins remaining

    [ ERROR ] d:\Windows\winsxs\x86_microsoft-windows-s..oxgames-purbleplace_31bf3856ad364e35_6.1.7600.16385_none_0601d49e5fc57a03\PurblePlace.dll (Error = 112)

     

    [ ERROR ] d:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\DrUpdate.dll  (Error = 112)

     

    Error imaging drive [d:\]

    There is not enough space on the disk.


    thanks, clau

     
  • Saturday, November 14, 2009 5:29 PM
     
     Answered
    Sign In to Vote
    0

    Retried capture to d:

    f:\imagex /compress maximum /flags "Enterprise" /capture d: d:\install.wim "Windows 7 Enterprise" "Windows 7 Enterprise Custom"

    success 18 mins 52 sec

    install.wim size 4.07 GB

     

    moved install.wim


    retried capture to d:

    f:\imagex /compress fast /check /flags "Enterprise" /capture d: d:\install.wim "Windows 7 Enterprise" "Windows 7 Enterprise Custom"

    success 13 mins 44 sec

    install.wim size 4.26 GB

    apparently the error occurs trying to capture the image to ufd. thanks, clau

    • Marked As Answer by claudh Saturday, November 14, 2009 5:31 PM
    • Unmarked As Answer by claudh Saturday, November 14, 2009 8:15 PM
    • Marked As Answer by claudh Sunday, November 15, 2009 1:12 AM
    •  
     
  • Saturday, November 14, 2009 8:26 PM
     
     
    Sign In to Vote
    0

    Trying to copy install.wim to deployment ufd results in an error: The file ‘install.wim’ is too large for the destination file system.

     

    Deployment ufd file system is FAT32 as per instructions.

    This might be the explanation for the previous errors since capture ufd was also formatted FAT32 as per instructions.

     

    Using NTFS file system for the deployment ufd the original reference machine boots up, setup starts and my custom installation runs through just fine.
    This is a DELL laptop. Another DELL laptop also boots up with this ufd and starts setup.

    However, using the same ufd results in an error on two other desktop computers (which I actually want to deply to): A disk-read error occurred. Press Ctlr + Alt + Del to restart.

     

    After playing around with this for 4 straight days now this is getting more and more frustrating. Any suggestions are very much welcome. Thanks, clau

     

     

     
  • Sunday, November 15, 2009 1:12 AM
     
     
    Sign In to Vote
    0

    Follow up: installed Windows 7 manually on one of the desktop computers that did not want to start from UFD earlier.

     

    Still can not get it to boot from USB.

    Trying to boot from capture UFD with a FAT32 32GB partition results in the error below.

    The same UFD works fine booting up both of the two DELL laptops.

    USB boot appears to be a hardware issue rather then a Microsoft related problem. Thanks, clau

     

    **start error

    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

    1. Insert your Windows installation disc and restart your computer.
    2. Choose your language settings, and then click “Next”.
    3. Click “Repair your computer”.

    If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

     

    File: \Boot\BCD

    Status: 0xc000000e

     

    Info: An error occurred while attempting to read the boot configuration data.”

    **end error

     

     
  • Tuesday, January 26, 2010 10:41 PM
     
     Proposed Answer
    Sign In to Vote
    1
    try formatting the UFD as a NTFS drive, that worked for me as my wim file was 5.2gb
     
  • Monday, April 19, 2010 5:43 AM
     
     Proposed Answer
    Sign In to Vote
    1

    I do beleive George57 is correct.

    I received same type of error when doing this:

    capturing a simple image of a drive ... i had a c: and a d: drive to do, using imagex ... i never have problems with imagex and when i do i solve them thus to date nothing has stopped a good image.

    So i try to capture c: drive of approx 18GB and dump to a external drive using USB Western Digital and thus five times of trying i keep getting a error 112 about not enough space to C: drive

    Well first problem is that i am not dumping image to C: drive i am dumping image to external drive of extra space of 411GB on the external hard drive ...

    so i thought i maybe need more swap space on c drive as there was very little on c: but what the ____? is not memory enough to run imagex? and futhermore its putting data from c: to external ... but ok i do my thought, thus i take off ____ of c: drive and gain approx 1.5 GB and that should be enough .. thus run again (and yes i have commands correct) and thus same thing ...

    So i read a bit more and find George57 a thought of interest ... as i always dump my images onto a exteranl drive and never problems ... bu this time i used a different external drive as my usuall one was filled ... so i go check my external drive i always used and worked and sure enough ... NTFS and then i check the exteranl drive that is maybe giving and causing the issue ... and sure enough FAT32

    Thus i clean up some space on my external drive that is formatted with NTFS and walla ... the ol image is now in its new home :)

    George57 ... you have done well :)

    The only thing that would have really helped and directed a user to slove this quicker would have been if imagex could have shown an error pointing to the correct drive .. and not point to C: drive .. as the error stated C: drive did not have enough space .. this is very misleading ... and thus shows you why i started thinking swap files and or more memory needed ... the error should have shown the actuall drive that was causing the issue.

    Hope this helps ...

     
  • Monday, March 07, 2011 8:45 PM
     
     
    Sign In to Vote
    0

    I know this thread is old, but I was having the same issue....error 112.

    What I was able to do was on a 32GB UFD with file system NTFS create my bootable PE UFD.  I then took a 2GB thumb drive and also created a formatted ufd, but not bootable PE.

    Once I booted into the PE on the 32GB ufd, I then inserted the "dummy" thumb drive.  That was when "E:\" then became "ready".  All the other times I only had the single thumb drive plugged in only X:\ and C:\ where visible to DIR.  E:\ kept coming back as "device not ready"

    I had issues from the beginning with the mentioned guide, so I stuck IMAGEX.exe under \MOUNT\WINDOWS\MyApp (I created MyApp folder) because I could never find E:\ which was where the copied IMAGEX.exe was supposed to end up upon booting into PE.

     
  • Thursday, June 23, 2011 3:56 PM
     
     
    Sign In to Vote
    1
    Just wanted to put my two cents in here. I was also having this error 112 trying to copy to an external hard drive formated as FAT32. Once I re-formated the drive as NTFS it took care of the problem.
     
  • Tuesday, May 08, 2012 1:51 AM
     
     
    Sign In to Vote
    1

    Yup, same here.

    The problem is the DAMN NTFS FS

    Just  format fs=ntfs quick

    instead of  format fs=fat32 quick

    And that makes the trick.

    • Proposed As Answer by TheG_o_D Wednesday, August 01, 2012 5:11 PM
    • Unproposed As Answer by TheG_o_D Wednesday, August 01, 2012 5:11 PM
    •  
     
  • Wednesday, August 01, 2012 5:18 PM
     
     Proposed Answer
    Sign In to Vote
    1

    The reason for the error is most like due to the file size limitations of FAT32 files. 

    FAT32 partitions can only supports a maximum file size of 2-4GB depending on implimentation.  If the file exceeds this size it will produce errors. 

    Formatting as NTFS will allow the file size to be upto 16TB. 


    • Edited by TheG_o_D Wednesday, August 01, 2012 5:19 PM miss spelled
    • Proposed As Answer by TheG_o_D Wednesday, August 01, 2012 5:32 PM
    •