none
WDS Image Capture Wizard Stalls at 28%

    Question

  • Hi- Single Site, single domain. I have WDS running on Windows Server 2012 Standard. Have been using WDS for quite a while now without issue. Created a new image from scratch, applied all updates, installed apps.

    Ran sysprep (successful) and rebooted to initiate an image capture. Selected the volume, selected the WDS server, and storage group. Ran Net Use to map a network drive to copy the image file to. Capture started and gets to 28% and then stalls. Left it overnight and still at 28%. Tried it twice with the same results.

    What's going on here? Where should I look to find info on what the cause might be?

    Thanx


    You should never, never doubt what nobody is sure about. -Willy Wonka

    Wednesday, August 26, 2015 3:31 PM

Answers

  • Thanks for all of the suggestions and ideas. I tried a base install on the same PC with the same results. There is plenty of room on the WDS Server and alternate location where I save WIM files...

    I tried the image process again, but with a different box, and it was successful. So it had to be hardware or BIOS related. Seeing as how the BIOS on the first, failing, system was quite a bit older (2009), I am going to claim that it was an issue with the older, Atheros Boot Agent.

    The system that failed has an ASUS P5KPl-AM EPU m/b with AMI BIOS rev 2009

    Thanx


    You should never, never doubt what nobody is sure about. -Willy Wonka

    • Marked as answer by SteveSmo Monday, August 31, 2015 10:57 PM
    Monday, August 31, 2015 10:57 PM

All replies

  • You could try to test the following method.

    https://support.microsoft.com/sv-se/kb/2797676

    Wednesday, August 26, 2015 4:39 PM
  • [Update] I monitored the folder location I selected to save a copy of the image file. I could see that the image file was being created. I turned my attention to other things and when I looked again, the image file and temp files were gone and the progress bar for the WDS Image Capture Wizard was stalled at 28%...

    The article you referred above does not apply...

    Thanx


    You should never, never doubt what nobody is sure about. -Willy Wonka

    Wednesday, August 26, 2015 5:09 PM
  • I looked for log files on the workstation I'm attempting to capture the image from... Could only find two:  winpeshl.log and NetSetup.log; neither have any info regarding the failure. Any info on what files I should be looking for or at?

    You should never, never doubt what nobody is sure about. -Willy Wonka

    Wednesday, August 26, 2015 5:52 PM
  • Hi,

    It is rare that the process hanging at image capture phase even it already started to capture. Is that a network location on WDS server or a local location on workstation? Try both of them to rule out network issue. Also try using a fresh Windows 8.1 image for test since it might be caused by some application you installed. Looking into the WDS server's event logs (Deployment-Services->Debug), even I am in doubt about if there is failure entries in it since there is no error message and failure information, but it still worth to give a check.

    How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012

    https://support.microsoft.com/en-us/kb/936625

    Regards,

    D. Wu


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, August 31, 2015 3:19 AM
    Moderator
  • Thanks for all of the suggestions and ideas. I tried a base install on the same PC with the same results. There is plenty of room on the WDS Server and alternate location where I save WIM files...

    I tried the image process again, but with a different box, and it was successful. So it had to be hardware or BIOS related. Seeing as how the BIOS on the first, failing, system was quite a bit older (2009), I am going to claim that it was an issue with the older, Atheros Boot Agent.

    The system that failed has an ASUS P5KPl-AM EPU m/b with AMI BIOS rev 2009

    Thanx


    You should never, never doubt what nobody is sure about. -Willy Wonka

    • Marked as answer by SteveSmo Monday, August 31, 2015 10:57 PM
    Monday, August 31, 2015 10:57 PM