Announcing Windows 10 Insider Preview Fast & Skip Build 16273 for PC Insider

CountMike said:

Yes, fast one, less than an hour on this machine and that's counting download of about 40mbps. I attribute that to missing 77-79% high disk usage which is slowest part of all. It would be even faster if process used more resources, I have 6 cores, 12 thread 4GHz processor and update uses only one core/thread. Same with RAM, only 20% of 16GB. If it was using more resources it would be even faster. It's not very best idea to use computer during the update as it may interfere with process so saving resources is not a priority.
I'm going to use same ISO, I made from this one, on second computer that's much slower with 4 cores and 5400Rpm HDD and see how long it takes. That would be minus download time of course.

OS upgrades should really have a button where one could tell it to use all available resources in the system. Would speed up things a lot. I'd rather wait 30minutes doing nothing, than use computer while upgrade is in progress and risk a failed upgrade. Using the computer while updates are working is pain anyways. :)

As I mentioned elsewhere, it may no longer be possible to run UUPtoISO before restarting and get a viable ISO: UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 82 - Windows 10 Installation Upgrade Tutorials

... at some time before 100% of the install is complete, most of the larger ESDs, CABs, and folders get removed...

... this change makes it easier for installs on limited storage to complete successfully - and speeds up the update process removing between ~1.5GB and ~3.5GB files that may otherwise need to be copied, transferred or otherwise processed.
This means that if you leave it too late, UUPtoISO may find that some of the files it depends on may be removed before they can be processed into WIMs.

Along with the quicker install times noted (for some users!) you may need to be snappy when deploying UUPtoISO!

There is possibly some optimum % of download complete to start UUPtoISO, as after installation starts, there may not be enough time to process all the UUP download files to Install.WIM.

YMMV. - This of course will vary with machines constructed with SSDs or HDDs, faster or slower processors, or greater or lesser quantities of RAM etc.

Fafhrd said:

As I mentioned elsewhere, it may no longer be possible to run UUPtoISO before restarting and get a viable ISO: UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 82 - Windows 10 Installation Upgrade Tutorials

Agreed, but that is an easy fix. Nothing gets removed completely, it just changes shape to something that current UUP2ISO does not understand. :)

Upgrading on my Skippy VM, on my ancient Asus, took me less than an hour to get from old desktop to new desktop. Really fast upgrade.

40 minutes on second computer, updating from USB2 stick and still at 1% of initial part of update.

I had two VMs, skippy and rs3. Skippy found upgrade bang on 6pm last night. RS3 says it is up to date. Go figure!

CountMike said:

40 minutes on second computer, updating from USB2 stick and still at 1% of initial part of update.

An hour, 15m and and only up to 20%.

CountMike said:

An hour, 15m and and only up to 20%.

Really slow upgrading on physical hardware. Not sure what it's doing. I already had 2 fails. Now scanned system, disabled AV and non essential services. Hope I get it updated now!

Interesting that the VM was so fast on same hardware, but upgrading the host is a pain.

slicendice said:

Really slow upgrading on physical hardware. Not sure what it's doing. I already had 2 fails. Now scanned system, disabled AV and non essential services. Hope I get it updated now!

Interesting that the VM was so fast on same hardware, but upgrading the host is a pain.

I'd say it's because of really slow HDD and USB2 stick. Now it's at first restart, 2%.

CountMike said:

I'd say it's because of really slow HDD and USB2 stick. Now it's at first restart, 2%.

But I have none of that! One would expect the VM to be slow while the host being fast, but it's the other way around for me. :)