Announcing Windows 10 Insider Slow Build 17025 for PC Insider

Kari · 04 Nov 2017

@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.

martyfelker · 04 Nov 2017

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?

Tony K · 04 Nov 2017

Kari said:

@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.

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

martyfelker · 04 Nov 2017

Kari:

Your tutorials are great btw I will provide you more information tomorrow.

martyfelker · 04 Nov 2017

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 ....

cereberus · 05 Nov 2017

martyfelker said:

The relevance is that grammar and spell checkers are not perfect. Should be "feat" of course.

Eye no ewe are write.

I was only joking :-D.

slicendice · 05 Nov 2017

@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. :)

bordi · 05 Nov 2017

bordi said:

I gave up after the 4^th attempt

It freezes on widow’s logo after configuring updates and reboots

bordi said:

Seems the last two versions 17017 and 17025 are incompatible with my machine
Neither version will install, both get stuck on windows logo on first reboot
Both on a never ending loop

bordi said:

Like me, I’ve tried everything suggested on this forum and elsewhere to upgrade to the last two builds with no success at all.

Something is blocking windows from installing after the very first reboot, it just crashes on the windows logo.

Windows failed to install 22 times

Tried legacy enabled then UEFI enabled still no good

I’ve even upgraded my bios and the chipset to the latest version available for my motherboard

bordi said:

I’ve done the Extended Disk Cleanup and clean up system files and deleted SoftwareDistribution folder and downloaded a fresh 17025

I already tried the ISO method, mounted way USB and DVD

There is nothing connected to the machine other than mouse and keyboard

There is no antivirus programs installed other than windows defender, I even tried after disabling that

The only thing I haven’t tried yet is a fresh install

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

bordi · 05 Nov 2017

bordi said:

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

Process of elimination, when you have eliminated the impossible, whatever remains, however improbable, must be the truth

MS must be experimenting with me to see what i do next by giving me dud downloads of 17025

Kari · 05 Nov 2017

martyfelker said:

From an admin command prompt I get:

Error: 32

The process cannot access the file because it is being used by another process.

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.

martyfelker said:

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 ....

That should work.

HippsieGypsie said:

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.

Something funny going on with your PC. DISM command shouldn't cause BSOD / GSOD, can't find any relevant information on the net.

slicendice said:

Space used on system: 12GB
Time taken on my hardware: 32 minutes 2 seconds
Image size: 4 527 244 722 bytes

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:

Announcing Windows 10 Insider Slow Build 17025 for PC-image.png

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