Windows 10: DISM image capture missing files after copy

We are having a strange problem taking an image from a VM to deploy on PCs. We have done it this way for a couple years without issue but this round seems to be acting odd. I boot into the VM with Windows PE, run DISM /image-capture etc, save the WIM, life is good. I can mount the wim on that same VM after booting back into windows and it shows all files there, good to go. When I copy the WIM to our WDS server to mount there and inject drivers etc, some system files are missing such as the wdboot.sys files in windows\system32\drivers\wd folder. The three files show there but are 0kb and cause the PC to blue screen on those files when burning to a PC.


At first it seemed like AV is at work but the logs on the AV server are not showing any files being deleted or quarantined. The other thought is that it is making a copy of a reference to the files like dedup but it is just a straight capture of c:\ on a fresh install.


Thoughts?

:)

 

Question about capturing a Windows 10 image using DISM


Hi,

I have the following task to complete; I would like to capture an image from a machine running Windows 10 enterprise using WinPE and DISM and then using Windows Server 2012 R2, PXE boot the captured image onto 10 other machines on the network. I would not like to use any third party tools to complete this task by the way. I am planning on following this guide: Deploy Windows 10 using MDT 2013 and WDS TheITBros but am having some trouble completely comprehending the guide. *Confused If anybody can suggest a better guide which satisfies my requirements I would very much appreciate your suggestions.

My first question is (apart from the Server 2012 R2 which is my domain controllor, the 10 machines I wish to PXE boot the Windows 10 enterprise image to, the switch connecting the 10 machines and the network) how many additional machines do I need to complete this task? (I just want to get a clearer picture of how many machines I will need hence the first question)

My second question is about capturing the Windows 10 enterprise image itself. My current understanding is that I have to run sysprep with the generalise and OOBE (set to shutdown) switches to remove the SID's then boot WinPE on the machine and use DISM to capture the Windows 10 enterprise image. Sounds easy so far except that I've looked at some guides online and rather than capturing just the Windows 10 enterprise image, some people also capture their system and recovery partitions. Just to clear up what I mean by this, when you go into diskpart and then type list volume, you are shown (on my machine at least) the system partition which is about 100MB, the recovery partition which is about 500MB and the partition where my operating system is stored which varies from machine in size but is about 470GB on my machine. My point and question is do I only need to use DISM to capture the partition where my operating system is stored e.g. my C:\ drive and will this be enough when I later deploy the captured Windows 10 enterprise image via Server 2012 R2 and PXE booting?

Also, if you could please give me a small explanation on the steps I need to carry out next after capturing the Windows 10 enterprise image with DISM i.e. the steps to deploy the captured image using Server 2012 R2 and PXE booting across my network.This would be really appreciated, thank you.

Thank you,

 

WHAT'S THE DIFFRENCE BETWEEN "Capture-CustomImage" and "Capture-Image" WHILE CAPTURING IMAGE USING DISM

Hi.

/Capture-CustomImage only captures the customization files. It can’t be used to capture installation files into a new WIM.

/Capture-Image

Captures an image of a drive to a new .wim file. Captured directories include all subfolders and data. You cannot capture an empty directory. A directory must contain at least one file.

Info for customimage here:
https://docs.microsoft.com/en-us/windows-hardwa...

Info for Image here:
https://docs.microsoft.com/en-us/windows-hardwa...

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.