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\).
- 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:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
- 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.
Virgilio Pontes 