Announcing Windows 10 Insider Preview Build 15025 for PC Insider

slicendice · 04 Feb 2017

Cliff S said:

For me, it was the prep work that took so long, the actual download & install, was close to the old system(ESD way).
I wonder it has to do with it looking at your settings, which default apps you have uninstalled, then writing an answer file to respect those whishes.

I already answered this question. The initialization process verifies each file integrity already on the system using SHA1 hash values that are downloaded as XML-files compressed in CAB-files. Each CAB-file is one package with a lot of SHA1 values. A default Windows system has 50k+ files to be verified. The setup process first finds and verifies what you have, then it copies each and every file to the setup directory either by downloading it or from the local system, depending whether the file existed locally or not and if it could be verified for integrity. Then the setup verifies that copied/downloaded file again. Once all 50k+ files has been verified the actual setup preparation begins. After this it's time to reboot, and the setup does it's thing as usually.

kado897 · 04 Feb 2017

slicendice said:

I already answered this question. The initialization process verifies each file integrity already on the system using SHA1 hash values that are downloaded as XML-files compressed in CAB-files. Each CAB-file is one package with a lot of SHA1 values. A default Windows system has 50k+ files to be verified. The setup process first finds and verifies what you have, then it copies each and every file to the setup directory either by downloading it or from the local system, depending whether the file existed locally or not and if it could be verified for integrity. Then the setup verifies that copied/downloaded file again. Once all 50k+ files has been verified the actual setup preparation begins. After this it's time to reboot, and the setup does it's thing as usually.

With that approach it is never going to be fast.

slicendice · 04 Feb 2017

kado897 said:

With that approach it is never going to be fast.

Nope.

slicendice · 04 Feb 2017

Either way, completely disabling Delivery Optimization in Services, helps skipping at least one verification step, which decrease the upgrade time significantly. And it does not matter if you have Delivery Optimization enabled or disabled in the settings, that process will run either way if the service is not disabled completely.

EDIT: with delivery optimization in settings I mean that it does not matter if you have enabled Windows to download files from other users or not. (Choose How Updates Are Delivered option in WU Settings)

kado897 · 04 Feb 2017

slicendice said:

Either way, completely disabling Delivery Optimization in Services, helps skipping at least one verification step, which decrease the upgrade time significantly. And it does not matter if you have Delivery Optimization enabled or disabled in the settings, that process will run either way if the service is not disabled completely.

I may give that a try next time.

slicendice · 04 Feb 2017

kado897 said:

I may give that a try next time.

For me the Upgrade time dropped from 8h+ to about 1h+ after disabling this service.

AndreTen · 04 Feb 2017

kado897 said:

sfc /scannow runs clean.

Try running CCleaner. On registry and MRUs too.

kado897 · 04 Feb 2017

AndreTen said:

Try running CCleaner. On registry and MRUs too.

OK.

Cliff S · 04 Feb 2017

slicendice said:

I already answered this question. The initialization process verifies each file integrity already on the system using SHA1 hash values that are downloaded as XML-files compressed in CAB-files. Each CAB-file is one package with a lot of SHA1 values. A default Windows system has 50k+ files to be verified. The setup process first finds and verifies what you have, then it copies each and every file to the setup directory either by downloading it or from the local system, depending whether the file existed locally or not and if it could be verified for integrity. Then the setup verifies that copied/downloaded file again. Once all 50k+ files has been verified the actual setup preparation begins. After this it's time to reboot, and the setup does it's thing as usually.

Oh yeah I remember reading the earlier on too

Yeah it will be slow no matter how fast your system is jacked up either, as it needs to unpack those compressed CAB file first.

DavidY · 04 Feb 2017

kado897 said:

I'm on 256MB and 3D enabled. Oh and guest additions are running.

Yes I had Guest Additions going too - sorry I should have mentioned that.
If I change to 3D and 256MB, that breaks right-clicking on Taskbar icons for me too.
So I think I'm seeing the same problem as you, with those settings
If I put it back to settings as my post above, right-click works better.
Right-click on a blank part of the Taskbar itself seems to work in both scenarios though.