none
Image Capture Boot Image Fails with 0xc000000f

    Question

  • I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from it. After I press F12 and the progress bar finishes the following message appears:

    This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server 2012. Is this a problem with the recent update?


    Friday, April 18, 2014 3:18 PM

All replies

  • Hi,

    We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.

    So far, I found two other posts with exactly the same issue:

    1) http://wp.secretnest.info/?p=1474
    2) http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing

    According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.

    What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.

    So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.

    I used BCDEDIT to show the differences between the working and non-working boot images:

    Windows Boot Loader
    -------------------
    identifier              {1d214c07-6892-401c-a762-04647ad38560}
    device                  ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
    961-85dd-a10f3c46473f}
    description             Windows 7 Boot Image
    osdevice                ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
    ee1-9725-2ab00a957daf}
    systemroot              \WINDOWS
    detecthal               Yes
    winpe                   Yes
    
    Device options
    --------------
    identifier              {b321afc0-8a23-4961-85dd-a10f3c46473f}
    inherit                 {68d9e51c-a129-4ee1-9725-2ab00a957daf}
    ramdiskmcenabled        No
    ramdiskmctftpfallback   Yes
    
    -- Second - Non Working disk --
    
    Windows Boot Loader
    -------------------
    identifier              {872352a0-0ad9-46f6-8612-1aed71ea8534}
    device                  ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
    b86a3a-3651-4f50-a748-34f3e784158c}
    description             Windows 7 Capture
    osdevice                ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
    d9e51c-a129-4ee1-9725-2ab00a957daf}
    systemroot              \WINDOWS
    detecthal               Yes
    winpe                   Yes
    
    Device options
    --------------
    identifier              {7ab86a3a-3651-4f50-a748-34f3e784158c}
    inherit                 {68d9e51c-a129-4ee1-9725-2ab00a957daf}
    ramdiskmcenabled        No
    ramdiskmctftpfallback   Yes


    So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.


    • Edited by C-Laze Saturday, April 19, 2014 10:44 PM Added KB article
    Saturday, April 19, 2014 10:43 PM
  • Hi,

    We are currently testing the same environment and will let you know once we got a result.

    Meanwhile as you both mentioned that the issue occurs on a capture image of Windows 2012 R2 update1 system, will it work with a capture image of a Windows 2012 R2 system without update1?


    If you have any feedback on our support, please send to tnfsl@microsoft.com.

    Tuesday, April 22, 2014 1:47 AM
    Moderator
  • I can verify that i am having the exact same issue. I am in the process of redoing the server and testing with out update one installed.
    Tuesday, April 22, 2014 9:21 PM
  • Having the same issue here with Server 2012 R2 fully updated - even tried a full removal of the WDS role and a recreation of the remoteinstall folder with brand new boot images - this didn't resolve it.

    I am trying a few things now, will update if I progress anywhere.

    EDIT: Just tried rolling back KB2919355 - tried the capture image again with no chances, didn't work. Removed WDS Role, re-added and tried again - worked fine. Based on that, I'd say there's a good chance that the problem is due to the above update.
    • Edited by Gavin Stone Tuesday, April 22, 2014 10:00 PM adding additional info
    Tuesday, April 22, 2014 9:23 PM
  • Okay guys, I think the problem is with every version of R2 server. I installed the "Windows 2012 Server (datacenter)" "Win_Svr_Std_and_DataCtr_2012_64Bit_English.iso" and created a capture image using the boot.wim of the same server I Installed and then booted to Capture image and VOILA! Now i'm going to try to use the same capture image that windows 2012 server datacenter built for me and I'll put it in R2 WDS and see if that works. I'm sure it will but ill update if this technique works!!

    - Copying good copy of Capture.wim to R2 server didn't work.



    Tuesday, April 22, 2014 9:47 PM
  • I just experienced this same problem today when I attempted to create a Windows 8.1 Pro Capture image on a fully patched Windows 2012 R2 Datacenter server. No problems creating then Windows 8.1 Pro boot image. I need to deploy 500 Windows 8.1 Pro clients by the middle of May. Really need an answer soon.
    Tuesday, April 22, 2014 10:43 PM
  • Only way I could get this working was to roll back KB2919355 and reinstall WDS
    Tuesday, April 22, 2014 11:55 PM
  • Ok so maybe this problem is not isolated to 2012 R2 Datacenter. We just checked another server running Windows Server 2012 Datacenter. Same problem. No KB2919355 on either server.
    Wednesday, April 23, 2014 1:36 AM
  • Hi Yordan,

    In our test, we use boot.wim from Windows 8.1 ISO (Enterprise version. also tried Windows Server 2012 R2 Datacenter ISO) and create capture image on a Windows Server 2012 R2 Update1 server - both created successfully. 

    I cannot find any difference between your steps and ours except you mentioned "used the boot.wim from the Windows Server 2012 R2 (with Update) ISO". Where comes the ISO with Update1? We would like to have a try on this and see if it is the cause.

    @Gavin: Your test seems directly related to KB2919355. What's the ISO you are using? Please have a try with boot.wim from a Windows Server 2012 R2 DataCenter ISO to see if you can get the same result as us.

    @WillWally: It seems that your current situation is a little different as OP. If available please post a new thread and share your exact configuration so that we can discuss without confusion. 



    If you have any feedback on our support, please send to tnfsl@microsoft.com.

    Wednesday, April 23, 2014 9:32 AM
    Moderator
  • I can verify that my issue is related to the update 1 of 2012 r2. I had a fresh install and updated all but update 1. My capture images worked with no issues. install update 1 and they then started becoming corrupt. I really hope that there is a hotfix for this issue soon.
    Wednesday, April 23, 2014 3:51 PM
  • I've also experienced this issue, with a clean out of the box install of Server 2012 R2, with no updates.  The trigger for it, is adding a boot image from the recently released ISO of Windows 8.1 with the Update 1 included (SW_DVD9_SA_Win_Ent_8.1_64BIT_English_2_MLF_X19_49847.iso).  The fix for me, adapted from the details on http://wp.secretnest.info/?p=1474 was to remove the WDS role, reboot, delete the RemoteInstall\Boot folder, add the WDS role back, and add a different boot image.  I used the boot.wim from the Server 2012 R2 iso (en_windows_server_2012_r2_x64_dvd_2707946.iso), and was able to create a working capture image for my 8.1 Update clients.

    Nigel Benfell B.Sc. MCSA

    Wednesday, April 23, 2014 9:28 PM
  • Hi all,

    Thank you for sharing the information.

    With updating the boot.wim to update1, we could reproduce this issue as the screenshot posted by Yordan.

    We have already report this issue and hope it could be fixed quickly. 


    If you have any feedback on our support, please send to tnfsl@microsoft.com.

    Thursday, April 24, 2014 9:53 AM
    Moderator
  • Just wanted to update my situation with Windows server 2012 Datacenter. Same problem as reported here with Windows 2012 R2 with the exception of update 1. My Windows 2012 Datacenter server does not have Update 1. I was able to get a capture image to work by first creating it in WDS 2008 R2. I then exported the image and imported it to my 2012 Datacenter server. Image boots successfully. For whatever reason, 2012 Datacenter corrupts the capture image when you try a create one.
    • Proposed as answer by trelf Tuesday, May 20, 2014 4:37 PM
    Thursday, April 24, 2014 1:15 PM
  • Totally legit....Creating the capture.wim file on server 2008 then copying to server 2012 worked for us as well.
    • Proposed as answer by trelf Tuesday, May 20, 2014 4:33 PM
    • Unproposed as answer by trelf Tuesday, May 20, 2014 4:37 PM
    Thursday, May 01, 2014 7:53 PM
  • experiencing the same issue here WDS server is windows server 2012. Havent been able to create a capture image.
    Friday, May 02, 2014 2:30 PM
  • I know this isn't a fix for this problem BUT if you really need to get deployments done - MDT 2013 is really a HUGELY better product than WDS. I am really surprised to see so many people using WDS - it is so massively limited compared to the Free MDT 2013. It is very easy to set up.

    Rhonda J. Layfield

    Wednesday, May 14, 2014 6:45 PM
  • Привет!

    По английски плохо пишу-говорю, долго.

    Поэтому вкратце как решил данную проблему.

    KB291935 у себя не нашел, хотя установлено самое последние обноввления Win Srv 2012

    Пробовал переустановить WDS, не помогло.

    Начал разбирать образы

    причем отличие win-файла образа от win-файла образа записи еще и в том, что в образе загрузки 2 образа, а в созданном в WDS файле WIM один образ.

    , нашел отличие в одно файле, в CaptureImage есть файл winpeshl.ini

    с содержимым,

    [LaunchApps]%SYSTEMROOT%\system32\wdscapture.exe

    Как создать ручками CaptureImage

    (http://technet.microsoft.com/en-us/library/cc730907%28v=ws.10%29.aspx#BKMK_custom)

    Экспортируем Образ загрузки из WDS.

    В моем образе загрузки Win8.1 два образа

    Монтируем его с помошью утилиты DISM (DISM /?) index 2

    Вставляем файл winpeshl.ini в windows\system32\

    Сохраняем изменения, отключаем образ.

    Измененный образ добавляем в WDS в образы загрузки.

    Уррррааааа, заработало!!!

    Правд без бубна, с MS, как всегда не обошлось :(

    Tuesday, May 20, 2014 5:08 AM
  • Had the same issue and was able to create a capture file from the Win 8.1 U1 media on a 2008 R2 WDS server, and it loaded and started working just fine on my 2012 R2 U1 WDS server.
    Tuesday, May 20, 2014 4:36 PM
  • MS is being pretty silent on this issue. We don't have a software assurance contract, so no one will talk to us about this bug.
    • Proposed as answer by Jan Weis Tuesday, June 17, 2014 1:39 PM
    • Unproposed as answer by Jan Weis Tuesday, June 17, 2014 1:39 PM
    Friday, May 30, 2014 3:22 PM
  • If you are looking for help - you need to use English.

    Rhonda J. Layfield

    Friday, May 30, 2014 6:28 PM
  • Hi all,

    Thank you for sharing the information.

    With updating the boot.wim to update1, we could reproduce this issue as the screenshot posted by Yordan.

    We have already report this issue and hope it could be fixed quickly. 


    If you have any feedback on our support, please send to tnfsl@microsoft.com.


    This was confirmed on April 24th as a known issue.  It is now May 31st and the issue is unresolved and uncommented upon by MS in this thread for almost a month.  Using a capture.wim created by another server isn't always possible - is there another workaround for people who can only use Server 2012 R2 besides removing U1 (which is a MAJOR patch covering many known issues)?

    ...John

    Saturday, May 31, 2014 5:12 AM
  • Also having this issue on Server 2012 R2 Update 1, waiting for fix?

    Jed Parkes - MCITP - Windows 7, Enterprise Desktop Administrator

    Thursday, June 05, 2014 2:11 AM
  • One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch. 
    Friday, June 06, 2014 12:51 AM
  • One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch. 

    This worked perfectly; very simple and quick, thank you!!
    Wednesday, June 11, 2014 4:16 PM
  • Any actual Clear instructions for people on doing this?

    Nick "The Naked MVP" Whittome

    Thursday, June 12, 2014 12:58 PM
  • Any actual Clear instructions for people on doing this?

    Nick "The Naked MVP" Whittome

    Here are the exact steps I used to fix the x64 capture image on our production WDS, using Saurabh.k' DISM fix (I assume that you know how to locate the capture WIM on disk, if not it will normally be located in RemoteInstall\Boot\<architecture>\Images\).

    1. Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)
    2. Open a command line window with administrator privileges, you'll run the two DISM commands here
    3. Mount the WIM file with the command dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
    4. Unmount the WIM file, committing changes (even though you didn't make any) with the command dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit

    Worked perfectly in my home lab and our production WDS at work. Both servers were running fully patched versions of Server 2012 R2. The capture image I had at home came from a Server 2012 R2 with Update ISO, while the one at work came from a Windows 8.1 with Update ISO. Neither worked before the fix.

    Output from the successful fix at work:

    C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\>dism /unmount-wim /mountdir:C:\MountDir /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.

    • Proposed as answer by chris_blakey Wednesday, June 18, 2014 8:20 AM
    Sunday, June 15, 2014 7:59 PM
  • One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch. 

    That worked for me! Thanks! Its a Workaround, but i have not to deinstall any Updates.
    Tuesday, June 17, 2014 1:44 PM
  • Thanks! This worked a treat for us on two new separate environments. 
    Wednesday, June 18, 2014 8:21 AM
  • Aaah great, I was struggling with this and was thinking about installing an additional server with 2008 R2 just for WDS.....you saved me a lot of time, great find!

    Keep it up!

    Rob.

    Friday, June 20, 2014 12:12 PM
  • I am also having this issue: Windows Server 2012 R2 Standard U1
    Sunday, June 29, 2014 4:06 PM
  • Try chris blakey's workaround.

    Worked for me too.  Only takes a minute.

    Basically you create a  folder to mount the image to temporarily, mount the image, then unmount it, and for some reason that probably makes sense to chris blakey this fixes the corruption.  Then you have to re-create the 'Create' boot image in WDS with the same one you mounted.

    Monday, July 07, 2014 2:18 PM
  • I  dont have update KB2919355.  butt still O have this same error, did you how to solve this issue
    Friday, July 11, 2014 9:01 AM
  • I want to point something out about this:

    When you install Windows ADK for Windows 8.1 Update (Update 1), it installs a copy of DISM into the tools folder that is version 6.3.9600.17029.  Just wanted to note that.

    If you install a copy of Windows 8.1 with Update 1 from a Microsoft DVD, it can have build versions between 17029, 17030, and 17031, depending on whether the post-U1 version of Update 1 KB package is fully installed (it installs a second time after you install a pre-"patched" version of a U1 Windows 8.1 install).  The stock install AFAIK, always starts at 17029 though.

    Now, when you patch an install of Windows 8.1 U1 with the post-U1 KB2912335 (I think that's the U1 KB number), the version of DISM in the system32 folder gets updated....HOWEVER, your installation of the ADK version of DISM *DOES NOT*.

    In the example above, you'd be using the DISM from the Windows PATH, which would be the fully-patched U1 version of DISM, which you can see from the version number as being build 17031.

    So the question is: are there conflicts with the builds in a stock Windows Setup U1 image (which would only ever be 17029), and a 17031 build of Windows Server 2012 R2 (or Windows 8.1)?

    Has anyone here been able to patch a Windows Setup U1 image all the way to build 17031 by fully integrating the U1 KB, and then tried the WDS Capture build wizard?  I'm assuming here that WDS uses DISM in the system32 folder on the native install of Windows Server 2012 R2 U1, since it doesn't require the ADK.  Just wanted to point out that the ADK version will always show 17029.

    Also, I want to point out that if you have a non-U1 version of Windows Server 2012 R2 Essentials, your Client PC Restore images for WDS NEVER get updated to U1.  If you want to update them, you have to patch them yourself.  I've seen some problems with using the build 16384 boot images for restoring PC's that had U1 installed.

    Saturday, July 19, 2014 4:55 PM
  • I just discovered another "bug" with DISM, just so people know about this:

    I have had no luck mounting WIM files on a ReFS-formatted volume while trying the workaround explained by Chris.  I get an Error 50: the request is not supported.

    So just FYI:  ONLY MOUNT WIM FILES ON NTFS VOLUMES.

    Took me HOURS trying to figure out why I couldn't mount some images migrated from an old system to a new one....

    Windows Server 2012 R2 Essentials on WinServer 2012 R2 Hyper-V with tiered storage.  Separate VHDX's: 1 for OS, 1 for "ServerFolders" data folders formatted ReFS, 1 for WDS formatted NTFS, 1 for backup stored on an external hard drive.

    The last setup I did was with 2012 before R2.  No ReFS.  Now, going with ReFS, noticing some limitations with it.  Good for raw data, bad for anything vaguely related to file system access - and that includes WIM support.

    Can someone from Microsoft please confirm that this is a known issue with ReFS, and comment?  And where in the TechNet Library does it say that ReFS is not supported by WIM mount?

    Saturday, July 19, 2014 7:10 PM
  • Using Windows Server 2012 R2 Datacenter and experiencing the same thing.

    I've tried the WIM mount/unmount trick but with no joy. Now in the processes of creating a 2008 R2 server for the purposes of image capture.

    Where is the fix?

    Wednesday, July 30, 2014 7:10 AM
  • Any actual Clear instructions for people on doing this?


    Nick "The Naked MVP" Whittome

    Here are the exact steps I used to fix the x64 capture image on our production WDS, using Saurabh.k' DISM fix (I assume that you know how to locate the capture WIM on disk, if not it will normally be located in RemoteInstall\Boot\<architecture>\Images\).

    1. Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)
    2. Open a command line window with administrator privileges, you'll run the two DISM commands here
    3. Mount the WIM file with the command dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
    4. Unmount the WIM file, committing changes (even though you didn't make any) with the command dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit

    Worked perfectly in my home lab and our production WDS at work. Both servers were running fully patched versions of Server 2012 R2. The capture image I had at home came from a Server 2012 R2 with Update ISO, while the one at work came from a Windows 8.1 with Update ISO. Neither worked before the fix.

    Output from the successful fix at work:

    C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\>dism /unmount-wim /mountdir:C:\MountDir /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.

    In addition to the above steps to Mount the Capture Image then Unmount with /Commit switch, I had to do the following to get this to work:

    1. Delete the existing capture image in the WDS console and then upload the newly committed capture image
    2. Stop and start the WDS service through the WDS console

    Not sure if theses steps were missed in Rolf HH instructions or whether this is additional step in some cases.

    Paul

    • Proposed as answer by Kohdiferous Wednesday, August 06, 2014 8:05 PM
    Saturday, August 02, 2014 3:28 PM
  • I encountered the same issue today trying to capture a image of Windows 8.1 w/Updates. Thank you all for you posts.

    Paul - I did the additional steps witch helped but I also had to Replace Image using the same captureimage.wim file.

    My steps:

    1. Create MountDir and Mount WIM then Unmount WIM, shown above.
    2. Deleted and recreated Capture Image
    3. Replaced Capture Image using same captureimage.wim file.
    4.  Stop & Start WDS

    Thanks again! Help me save a lot of time!!

    Wednesday, August 06, 2014 6:03 PM
  • Thank you, worked perfectly!
    Friday, August 22, 2014 12:29 PM

  • Thanks to you all above, mounting, unmounting, deleting, adding, restarting did fix the issue booting the capture image.

    Not so many thanks to Microsoft for it still being broken in September.

    Wednesday, September 03, 2014 4:47 AM
  • The dism fix did not work for me for some reason. It would loads up fine, but it would come up with a blank screen instead of the capture wizard.

    Regardless I have another fix for those lucky enough to have backup copy of their reminst folder from a non-update 1 installation. Even better if you already have the deploy and capture boot images in it already. Stop the WDS server and replace that backup version in the folder. Don't install any boot images with update 1 after that. It should work. 

    Does anyone know any updates on this issue from Microsoft? We have workarounds, but this fundamentally feels broken. 

    Wednesday, September 03, 2014 6:15 PM
  • I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from it. After I press F12 and the progress bar finishes the following message appears:

    This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server 2012. Is this a problem with the recent update?


    I have been working with Microsoft Technical Support on this issue.   Case 114072911658380

    The case is now archived with Microsoft as they have escalated this to the relevant team.   They have reproduced this bug and they are working on an official fix / workaround article.    This may come in the form of a support article or a patch, but a fix is being worked on.

    I have done my best to pressure the product group to officially put up a "fash publish" support.microsoft.com article, but so far this has not happened.   I am hopeful that this will however happen soon.


    Nick "The Naked MVP" Whittome

    • Proposed as answer by Nick Whittome Wednesday, September 10, 2014 1:47 PM
    Wednesday, September 10, 2014 1:47 PM
  • Here are the exact steps I used to fix the x64 capture image on our production WDS, using Saurabh.k' DISM fix (I assume that you know how to locate the capture WIM on disk, if not it will normally be located in RemoteInstall\Boot\<architecture>\Images\).
    1. Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)
    2. Open a command line window with administrator privileges, you'll run the two DISM commands here
    3. Mount the WIM file with the command dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
    4. Unmount the WIM file, committing changes (even though you didn't make any) with the command dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit

    Worked perfectly in my home lab and our production WDS at work. Both servers were running fully patched versions of Server 2012 R2. The capture image I had at home came from a Server 2012 R2 with Update ISO, while the one at work came from a Windows 8.1 with Update ISO. Neither worked before the fix.

    Output from the successful fix at work:

    C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\>dism /unmount-wim /mountdir:C:\MountDir /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.

    These steps helped! Thanks Rolf! dammit Microsoft, this problem was reported in April, today is September 10 2014, still have the problem!
    • Proposed as answer by Sten Lootens Friday, October 10, 2014 12:12 PM
    • Unproposed as answer by Sten Lootens Friday, October 10, 2014 12:12 PM
    • Proposed as answer by Sten Lootens Monday, January 19, 2015 8:59 PM
    Wednesday, September 10, 2014 9:05 PM
  • I just ran into this issue now while creating a capture image.

    WDS Server is Windows Server 2012 R2 Standard; Capture image is based on a Windows 7 Professional boot.wim file. This workaround saved me oodles of time!

    Thanks!!

    Thursday, September 25, 2014 8:51 AM
  • Today is 25 September (in South East Asia, at least) and this hasn't been fixed yet... The mount / unmount workaround just saved me oodles of time.
    Thursday, September 25, 2014 8:56 AM
  • This "mounting" and "unmounting" worked for me! Thx!
    • Proposed as answer by MR. LONSKi Thursday, October 29, 2015 5:35 AM
    Monday, October 06, 2014 3:32 PM
  • Worked for me too.

    Cheers

    Wednesday, October 08, 2014 2:06 PM
  • dism /mount-wim /wimfile:C\RemoteInstall\Boot\x64\Images\capture.wim /mountdir:C\MountDir /index:1
    dism
    /unmount-wim /mountdir:C:\MountDir /commit

    Was the fastest solution as already stated by everyone, be aware  thath his Problem was confirmed by me totday (10-10-2014) with the Official Windows Server 2012 R2 Evaluation ISO

    Friday, October 10, 2014 12:22 PM
  • Just followed Gavin Stone's advice (Removed KB2919355, removed and added back WDS role) and it's working correctly now.  Thank you so much for that post !

    David Harris


    • Edited by TessCompany Wednesday, October 22, 2014 5:30 PM
    Wednesday, October 22, 2014 5:29 PM
  • This remains broken for 6 months now !!!
    Tuesday, October 28, 2014 10:53 AM
  • Thanks...
    Tuesday, October 28, 2014 10:58 AM
  • Thanks MannyManuel!
    Tuesday, November 18, 2014 2:37 AM
  • Just a note: You are not supposed to use WDS for deployment/capture, only for PXE booting the actual boot images. Use the real deployment solution from Microsoft that integrates nicely with WDS (MDT 2013).

    On TechNet you find well-proven step-by-step guides.

    TechNet Docs - Create a Windows 8.1 Reference Image    
    http://technet.microsoft.com/en-us/library/dn744290.aspx

    TechNet Docs - Deploy a Windows 8.1 Image Using MDT 2013 and WDS
    http://technet.microsoft.com/en-us/library/dn744279.aspx


    On TechNet Virtual Labs you can walk through each scenario, over and over again. Ready-made labs just waiting for you to connect. Yes, they are free :)

    Creating a Windows 8.1 reference image  
    http://go.microsoft.com/?linkid=9845755

    Deploying Windows 8.1 with MDT 2013 (Lite Touch)
    http://go.microsoft.com/?linkid=9845757


    The jumpstart videos is a collection of four videos, covering the basics of Windows deployment using MDT 2013 (and ConfigMgr/SCCM 2012 as well)

    Windows 8.1 Deployment Jump Start
    http://www.microsoftvirtualacademy.com/training-courses/windows-8-1-deployment-jump-start

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Thursday, November 20, 2014 5:49 AM
  • I still get the same error like the thread starter.

    I have tried the mount think but still get the error.

    I have even tried to reinstall windows server 2012 R2 and try with a boot.wim from a windows 7 disk but nothing works. 

    anyone have any idears what I am doing wrong?

    Thursday, November 20, 2014 10:59 AM
  • ok now I found out that is was the wrong wim file i mounted.

    but that only opens up for the next problem, where I get the windows loading logo and then black screen.

    Friday, November 21, 2014 8:12 AM
  • I get the same issue, have run through all the example resolution without any success.  Have also updated the capture boot.wim image using the process outlined (http://technet.microsoft.com/en-us/library/dn622020.aspx) and still have the bank screen after the initial boot sequence.

    running windows server 2012R2 std. with all latest updates

    Image Version: 6.3.9600.17031

    Boot image is windows 8.1 direct for Microsoft volume licensing download.

    I can boot fine from the original install, it's the capture disk that WDS creates that has the issue.

    Friday, November 28, 2014 3:16 PM
  • I am experiencing the same thing. Did you happen to find a solution?
    Monday, December 01, 2014 2:30 AM
  • Hi

    Here's the solution that worked for me:

    Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)Open a command line window with administrator privileges, you'll run the two DISM commands here

    Mount the WIM file with the command

    dism /mount-wim /wimfile: /mountdir: /index:1

    Unmount the WIM file, committing changes (even though you didn't make any) with the command

    dism /unmount-wim /mountdir: /commit

    Then add your Capture Image to WDS Boot Image Folder...

    • Proposed as answer by MTorabi Wednesday, December 03, 2014 2:17 PM
    Wednesday, December 03, 2014 2:07 PM
  • The mount, unmount thing only help on the 0xc000000f error.

    The black screen error that some of us are getting now, is a new error.

    I think it has somthing to do with the driver in the boot.wim but i am not sure yet.


    • Edited by Jerslund Friday, December 05, 2014 10:23 AM
    Friday, December 05, 2014 10:23 AM
  • Same issue here.  Spun up a fresh 2008R2 box, configured WDS.  Created new boot.wim file and new capture image file.  Imported the .wim files from 2008R2 to 2012R2 box.  All is well.

    If anyone is need.  here are our windows 8 boot files.

    https://docs.google.com/a/marist.com/file/d/0ByvarSY6f0yRcDMzMXd0SjhWM2M/edit

    https://docs.google.com/a/marist.com/file/d/0ByvarSY6f0yRZm9oMTJCSDJhQzA/edit


    • Edited by MARIST SCHOOL ATL Wednesday, December 10, 2014 6:28 PM
    • Proposed as answer by Jerslund Monday, December 15, 2014 8:04 AM
    Wednesday, December 10, 2014 6:22 PM
  • Just wanted to update my situation with Windows server 2012 Datacenter. Same problem as reported here with Windows 2012 R2 with the exception of update 1. My Windows 2012 Datacenter server does not have Update 1. I was able to get a capture image to work by first creating it in WDS 2008 R2. I then exported the image and imported it to my 2012 Datacenter server. Image boots successfully. For whatever reason, 2012 Datacenter corrupts the capture image when you try a create one.
    Same problem, used a capture image from another server and it works fine.
    Thursday, December 11, 2014 6:14 PM
  • The wim files from server 2008 R2 works. Thanks a lot.

    Monday, December 15, 2014 8:05 AM
  • Dear : ALL 

    I faced this problem from 2 days and i spent many times try to fixing this problem and i solved it but you have common steps you should to do or sure its done :

    im talking about WDS SERVER 2012 R2 :          PROBLEM ( 0XC000000F )

    Common Steps :

    1- DHCP Server  scope option

    PXEClient = 060       add your WDS Server IP this you should add by manual in scope option 

    boot server host name = 066    add your WDS Server IP

    Boot file Name = 067                add ( \boot\x86\wdsnbp.com )

    Now your Done in DHCP SERVER

    2- When you install Clean WDS Server  ( win server 2012 R2 ) close Automatic Update For Windows and Remove

    this Fucken Update  ( KB2919355 ) cause you will find this update installed by default  , Then Install your WDS Service ) and for configure server on any partition not in c:\   drive    ,     and save all images and capture you will add in RemoteInstall Folder 

    3- Ports Allowed 

    you should allow the following ports in your Firewall if you have and in your Antivirus server : 

    TCP =   135 , 5040

    RPC= 137 , 139 ,

    UDP = 67 , 69 

    DHCP= 4011 , 68 

    TFTP = 64001 : 65000

    I Hope this can help >>>!!!!


    kano

    Sunday, December 28, 2014 9:53 AM
  • i also had to stop and restart the WDS service through the WDS console however i have written a simple batch script to simplify the process of moving, mounting, unmounting and  committing the images http://www.mediafire.com/view/ucauj2yahi4g0f8/WDStool.bat  
    Monday, December 29, 2014 11:38 AM
  • hi

    i just finished updating my Windows 8.1 Enterprise Master image (and do this in hyper-v on a windows 8.1 x64 client - fully patched) and the wsus is a Win 2012 r2 fully patched server also and get the same error when trying to capture now.

    i was able to push the image into hyper-v and boot with a setup ok but am unable to capture now :\

    i have recreated both setup and capture .wim files and restarted wds service in case the original files were corrupt - still no go.

    any help would be much appreciated

    thanks in advance : )

    Tuesday, January 13, 2015 11:39 AM
  • ok guys- here is what i did and what i found to be the problem -

    i tried all the above and none of this worked so i ended up stopping my WDS server and built another WDS in hyper v on my file server - and voila! i imported my original boot wim's (capture and custom tools i have made on win pe) and everything works like before.

    i also tried copying  winload.efi files from anotherwokring wds server (from another site) but that did not work also the files were exactly the same size hmm

    must have been some corruption

    my new server is fully patched also and one thing i have done is enabled system recovery, and made sure snapshots are taken before updates take place - so if something goes pear shaped - i can always go back

    infact im gonna export this hyper v wds i built and bang it on the physical wds i used to have and turn that into a hyper v host instead.

    hope this helps.

    • Proposed as answer by MR. LONSKi Wednesday, January 14, 2015 4:35 AM
    Wednesday, January 14, 2015 4:35 AM
  • Worked for me Thanks

    I used Mount-WindowsImage/Dismount-WindowsImage

    Thursday, January 15, 2015 1:22 PM
  • I'm confused on which wim to use. Bear with me, I'm not incredibly smart with this stuff yet.

    So I've captured my Windows 8.1 image to a wim file. Is that the file that I do the DISM patch on? Is there anything I have to change in the SCCM console afterward? I tried these steps, tried re-adding the OS image, tried creating a new task sequence, etc. I'm using the default boot images.

    Friday, February 20, 2015 5:40 PM
  • FYI:

    Using a Capture Wim created on a Windows 2008 server solved the issue. Once created I right clicked my existing capture image on the Windows 2012 R2 server and selected replace.

    • Proposed as answer by SeanB13 Tuesday, February 24, 2015 7:03 PM
    Tuesday, February 24, 2015 7:01 PM
  • Any actual Clear instructions for people on doing this?


    Nick "The Naked MVP" Whittome

    Here are the exact steps I used to fix the x64 capture image on our production WDS, using Saurabh.k' DISM fix (I assume that you know how to locate the capture WIM on disk, if not it will normally be located in RemoteInstall\Boot\<architecture>\Images\).

    1. Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)
    2. Open a command line window with administrator privileges, you'll run the two DISM commands here
    3. Mount the WIM file with the command dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
    4. Unmount the WIM file, committing changes (even though you didn't make any) with the command dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit

    Worked perfectly in my home lab and our production WDS at work. Both servers were running fully patched versions of Server 2012 R2. The capture image I had at home came from a Server 2012 R2 with Update ISO, while the one at work came from a Windows 8.1 with Update ISO. Neither worked before the fix.

    Output from the successful fix at work:

    C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\>dism /unmount-wim /mountdir:C:\MountDir /commit
    
    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031
    
    Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.

    After mount and unmount as shown here I had to also do this to make the capture image load:

    1) From the WDS console, right click the capture image in the Boot Images section.  Click Replace Image.

    2) Browse to the image you just mounted and unmounted, select it to replace the existing image

    3) close WDS console and restart windows deployment services server from services.msc

    It must be using some kind of cache, errors persisted until I used the replace image option following the mount and unmount.  Did not have to delete the capture image from the console, did not have to use any server 2008.

    On another note, Microsoft, fix this problem it's been almost a year now.  

    • Proposed as answer by Brian44cc Wednesday, May 20, 2015 3:43 PM
    Monday, March 02, 2015 7:54 PM
  • Can I ask does anyone know if the version of DISM makes any difference? I've mounted an image from the "Deployment Tools Command Prompt" but the version is way behind.  6.1.7600.16385. 

    I've yet to fully test but concerned by mounting using a old version will not fix the issue. Will update...

    Thursday, March 12, 2015 11:22 AM
  • Hi,

    I had this problem too.

    Here is the way I solved it (I hope it will be useful):

    (WDS and Dhcp are not on one server)

    First remove my new and fully updated Win 2k12 R2 Then reinstall a 2K12 R2, this time I did not update the server and for boot image I imported the Win8.1 pro without update 1 , then make capture image.

    Finally it work. I think there is something with latest update for 6.3 version of windows (Win 8.1 or Win Server)

    thanks.

    Thursday, April 09, 2015 6:27 AM
  • Имею Server 2012R2 U1

    Задача такая была, создать на нем образ WDS Discover image экспортировать и импортировать на Server 2008R2 

    При экспорте и импорте на Server 2008 R2, получал такую же шляпу.

    Подтверждаю, Mount Unmount реально помогло ! Спасибо! Причем без каких либо правок, просто Mount и Unmount

    Wednesday, April 22, 2015 1:37 PM
  • That did it for me too, I scripted it. I did find that the copy of windows 8.1 I had, still did not work. So I tried it with a windows 7, and that script. 

    dism /mount-wim /wimfile:D:\wds\capture\satellitea135.wim /mountdir:D:\wds\capture\MountDir /index:1
    dism /unmount-wim /mountdir:D:\wds\capture\MountDir /commit

    If it is any use to you, copy and edit it. 

    Make sure you create that MountDir first. 


    Sunday, April 26, 2015 2:05 AM
  • Thank you so much. You just saved my sanity. I've been working on this for two weeks.
    Wednesday, May 20, 2015 3:43 PM
  • I am struggling with the same issue.

    I believe the problem is in WDS.

    PXE boot loads the "boot.wim" image  but not the "capture boot image"

    When we try to create capture boot image from boot.wim, it doesn't capture all the files from boot.wim.

    If you compare the file size of capture boot image with boot.wim, file size is small.

    The result when we try to load the capture boot image using PXE boot, it gives an error that "required files are missing or contains error"

    Friday, June 26, 2015 2:19 AM
  • NOTE: While this method is clearly not ideal, it does work and works well. I just wanted to share this in case anyone is at the point of pulling out their hair or looking for another solution with Symantec or something else.

    So like everyone else I was getting the Black Screen of doom. We have more of a customized setup as I am running Hyper-V on a (2) node 2012R2 Cluster.  From the cluster I stood up a virtual 2012R2 WDS Server in Stand alone mode running DHCP locally as we are not allowed to join this server to the Domain, or AD and is also running in a private VLAN. The goal was to use WDS to image computers with a Dell OEM version of Windows 7 SP1 x86 including updates and custom apps. As it stands OEM is not supported by WDS so we did use a Windows 7 x86 Volume License copy to create the capture and boot images. 

    No matter with our with out the KB2919355 or using dism from the server or dism from the AIK tools to unpack/repack the capture.wim, nothing worked. The best I got was a mouse cursor and the black screen. I also tried to capture just the Windows 7 VL, and or Dell OEM with no dice no matter which way I tried. I also rebuilt the server a total of three times as well trying different methods with no updates, all updates except KB2919355, or all updates period. As a work around I went forth and made a custom WindowPE disk to create the image and push it to the server. Below are the steps I took.

    ---
    Create Bootable Windows PE Media (AIK) (POSReady 7)
    https://msdn.microsoft.com/en-us/library/hh273179(v=winembedded.21).aspx

    NOTE: 
    If you need to create a USB thumb drive from an ISO I was able to use ISO to USB, make sure to check mark the Make Bootable option and you should be good to go.
    http://www.isotousb.com/

    ---
    Add Device Drivers on an Offline Windows PE Image

    https://technet.microsoft.com/en-us/library/dd799289(v=ws.10).aspx

    NOTE: Make sure to read the comments at the bottom as you need to copy the file winpe.wim to boot.wim before you create the ISO or no drivers will be in your WindownPE

    ---

    Once you have PE usb/cd created you would still do the normal sysprep/ generilze obo /shutdown on the computer you want to create the image from. Once shutdown you then want to boot off the windowsPE disk and then follow the remaining steps to capture the image and place it on the WDS server

    Capture the Installation on a Network Share (AIK) (POSReady 7)
    https://msdn.microsoft.com/en-us/library/hh273236(v=winembedded.21).aspx

    Hope this has been useful for you, good luck and happy deploying :)


    • Edited by Joey of Troy Friday, July 03, 2015 3:10 PM forgot a word :P
    Friday, July 03, 2015 2:25 PM
  • Works perfectly for me!!!! Yeah Baby!!!! Thank you!
    Wednesday, July 08, 2015 1:27 PM
  • This issue is also present in Windows Server Technical Preview, haven't tried to find the KB patch for it what I did do however is just use an boot.wim from windows 7 and it is able to boot just fine, I'll be testing my images to a VM after they capture.
    Monday, July 13, 2015 1:09 AM
  • thanks! this worked for me as well.

    in my case win 8.1 Enterprise capture wim that was missing winload.efi

    however, the solution of mounting and unmounting still worked.

    Tuesday, July 14, 2015 1:09 AM
  • Hi,

    I check the thread and some cases related to this thread. Here are 2 suggestions provided by Microsoft. Please see if it could help:

    Use Microsoft Deployment Toolkit 2013 to run sysprep and capture.  

    or

    Create capture image on Windows Server 2008 R2 WDS and then import the image to Windows Server 2012 R2 WDS.  


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

    Thursday, July 30, 2015 2:01 AM
    Moderator
  • Solution problem.

    http://dave.harris.uno/capture-error-0xc000000f-with-wds-on-server-2012-r2/

    Thursday, September 17, 2015 8:40 PM
  • Can confirm this works! Rolling back that WinUpdate didn't work, mounting/unmounting the capture wim didn't work, but creating the capture file on a Server 2008 box then moving it to the deployment server worked! 
    Thursday, September 17, 2015 10:29 PM
  • I just had this issue and initially, the dism method did not work because I completed the commands on the capture.wim file located in my C:\remoteinstall\boot\x64\images\ drive. To get it to work, I removed the capture.wim boot image from Windows Deployment Services MMC. I then ran the two commands listed above to the capture.wim file that I first created which was located on my D:\Images folder. I went back into WDS, right clicked on Boot Images->Add a Boot Image. Browsed to my D:\Images\capture.wim file. Once the file was added, I booted up the desktop, hit F12, selected my capture file and it is now capturing. Below are the commands used.

    1. dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
    2. dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit

    Thank you to everyone on this page.


    Tuesday, October 27, 2015 6:06 PM
  • One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch. 

    thank mate! that totally worked! :) 2012R2server with all patches to date.
    microsoft please fix : (
    Thursday, October 29, 2015 5:36 AM
  • this link resolved for me this issue

    https://technet.microsoft.com/en-us/library/cc730907(v=ws.10).aspx#BKMK_custom

        • I created capture image
        • Mount the image using either DISM
        • Create a Winpeshl.ini file in the Windows\System32 folder of the custom boot image with one of the following sections.
    Capture Images.
    [LaunchApps]%SYSTEMROOT%\system32\wdscapture.exe
    
  • Discover Images.
    [LaunchApps]%SYSTEMROOT%\sources\setup.exe, "/wds /wdsdiscover"
    
    
    or
    [LaunchApps]%SYSTEMROOT%\sources\setup.exe, "/wds /wdsdiscover /wdsserver:<server>"
    
    

  • Martin Hubka nework admin

Tuesday, November 03, 2015 11:38 AM
  • One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch. 

    Thats the Solution, thanks!
     
    It's a shame that MS has not fixed it already! :-((
    Tuesday, November 03, 2015 5:47 PM
  • Tried to Mount, commit and unmounted the wim image.

     It worked!!!

    See here

    https://social.technet.microsoft.com/Forums/en-US/37aeb3f6-7ea9-4095-ae55-33d04e47c452/error-booting-to-capture-image?forum=winserversetup

    For God, and Country.

    Wednesday, December 09, 2015 12:48 PM
  • This has worked for so many but not for me! I'm using a Win7 SP1 Disc, so that may be the cause.. Although this should have been fixed by Microsoft already.
    • Edited by piffington Thursday, August 18, 2016 7:17 PM
    Thursday, August 18, 2016 7:17 PM
  • Thank you very much, this fixed it for me as well.  Glad I didn't blow WDS away and reinstall only to have it still broken.

    Cole

    Thursday, September 15, 2016 4:41 PM
  • It's still broken, in case anyone cares.  But mount with dism, unmount and commit, then delete and re-add the image in the WDS console, then restart the service....it worked for me, too.
    Thursday, November 17, 2016 3:41 PM