Windows 10 image taking over an hour to capture

[boomerman]

I have a windows 10 ( Creator edition 1709)  image that is 35 gigs that takes about 80 minutes  to capture once it starts the capture phase.

I have another windows 10 image ( Creator edition 1709) that is 40 gigs that only takes 45 mins at the most.

I have cleaned up the image as much as possible by removing temp files, pagesys files and restore points.

My host pc is 8 gigs of ram running windows 10. It runs nothing else but SmartDeploy and my virtual images

I am on version 2.0.2097 of SmartDeploy.

Any ideas why this one is taking so long?

 

[Jeff Harris]

I've seen instances where Windows Defender real-time scanning affects capture time. I would look at that first.

Also; SmartDeploy does a file-by-file copy to create the image. The difference in your images doesn't just have to be file size to make a difference in image creation time. The 35GB and 40GB VHD sizes aren't necessarily a reliable indicator of what's being used by files. 

 

[boomerman]

Windows Defender is not running on the pc. 

 

[Jeff Harris]

I'd be interested to see the file count between the 2 images once complete. Capture time is most related to the make up of the reference VM disk, but can also be affected by disk/network speed, or any real-time file scanning in place. It sounds like you would need to look at what's in your reference VMs.