Any
actual Clear instructions for people in doing this?
Nick "The Naked MVP" Whittome
Here is the exact steps I used to fix the x64 capture image in our production WDS, using SAURABH.K ' DISM fix (I assume th At your know how to locate the capture WIM on disk, if not it'll normally be located in REMOTEINSTALL\BOOT\<ARCHITECTU re>\images\).
Log on to your WDS server and create a empty directory that can mount the WIM in (I used C:\MountDir)
Open a command line window with administrator privileges, you'll run the both DISM commands here
Mount the WIM file with the command dism/mount-wim/wimfile:<path-to-wim-file>/mountdir:< Your-mount-dir-of-choice>/index:1
Unmount the WIM file, committing changes (even though you didn ' t do any) with the commandDism/unmount-wim/mountdir :<your-mount-dir-of-choice>/commit
Worked perfectly in my home labs and our production WDS at work. Both servers were running fully patched versions of Server R2. The capture image I had at home came from a Server-R2 with Update ISO, while the one in work came from a Windows 8.1 With Update ISO. Neither worked before the fix.
Output from the successful fix on work:
C:\>dism/Mount-Wim/Wimfile:C:\remoteinstall\boot\x -\images\capture_x64.Wim/MountDir:C:\mountdir/Index:1Deployment Image Servicing and ManagementToolVersion: 6.3.9600.17031MountingImage[==========================100.0%==========================] theOperation completed successfully.C:\>dism/unmount-Wim/MountDir:C:\mountdir/CommitDeployment Image Servicing and ManagementToolVersion: 6.3.9600.17031Image File :C:\remoteinstall\boot\x -\images\capture_x64.WimImage Index : 1SavingImage[==========================100.0%==========================]unmountingImage[==========================100.0%==========================] theOperation completed successfully.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/a164b948-1778-42bd-8d77-9cef1ca70866/ Image-capture-boot-image-fails-with-0xc000000f?forum=winserversetup
WDS R2 0xc0000000f capture Mirror failed