New
#290
@Tony I know that you are dual booting. Are you sure you are capturing the image from Insider partition, not FCU?
Anyway, it's 4 AM here. Need to have a few hours break.
From an admin command prompt I get:
C:\Windows\system32>dism /Capture-Image /ImageFile:C:\Image\install.wim /CaptureDir:C:\ /ScratchDir:C:\Scratch /name:"W10" /Compress:maximum /CheckIntegrity /Verify /Bootable
Deployment Image Servicing and Management tool
Version: 10.0.17025.1000
Error: 32
The process cannot access the file because it is being used by another process.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Now what?
Absolutely sure. Here are FE captures after reboot. Of course it didn't get as far as making image.
Yes, time for bed. Tomorrow is another day.
Attachment 162158
Attachment 162159
Well it's only 11:21 here but the switch to standard time will make it 1 hour earlier. So I will fool with this for awhile. Since it cannot access a file in use I will try to boot off the install media and hand type (gasp) the command. Then again its our wedding anniversary so ....
@Kari
I did the DISM "benchmark" you requested.
Refer to my PC 1 System Specs for hardware details.
I captured a relatively clean Windows 10 Pro EN-US Build 17025.1000 image, that has been created in Hyper-V.
For all disk operations everything was hosted on my SSD. The system I captured was contained within a dynamically expanding virtual disk. The image and scratchdir were put on another virtual disk (preallocated space).
Space used on system: 12GB
Time taken on my hardware: 32 minutes 2 seconds
Image size: 4 527 244 722 bytes
Hope this helps with your stats. :)
Still having big problems updating to 17025
I’ve installed a spare new hard drive as this is my main machine and I dint want to format that disk
Downloaded and installed fall creators version with no problems
Downloaded and installed the latest iso from MS 16299 with no problems at all
But when it comes to 17025 as always it just crashes on the first reboot windows logo and cant load the circling dots underneath it
You cannot capture Windows image when Windows is running, being online. Windows installation you want to capture to a WIM image must be offline. You need to either boot to Command Prompt or boot from install media and open Command Prompt.
That should work.
Something funny going on with your PC. DISM command shouldn't cause BSOD / GSOD, can't find any relevant information on the net.
Considering that you most certainly have faster and better system than I, and that you you have VM on SSD, that's awfully long time. I'm really surprised!
Here's result from a Hyper-V VM on my slow i5 laptop, VM on 5,400 RPM HDD. C: drive (Windows installation) used space 18 GB, VM has 4 GB of RAM and two virtual processors:
As I have done this most certainly at least a couple hundred times, capturing Windows 10 images almost daily in my customizing / deployment tests and I have never had image capture with DISM to fail or create a non-working image, I can speed up the process by not using integrity check and image verifying (removing /CheckIntegrity & /Verfiy switches from command) and simply trust that image will be OK.
Doing so, I can cut the time with over 20%. Here's with no integrity check, no verification on same VM:
Kari