The opposite is also true. It seems it is quite easy to confuse Windows when it comes to calculating the actual size on disk when shortcuts such as hardlinks, symlinks and inodes are involved.I cannot for sure explain why the difference in Size on disk is so small. I do believe this is because of default allocation unit size; the UUP download contains mostly small files which do leave a lot of allocation units half empty requiring unused space, whereas the ESD method basically differs from UUP download only by the install.esd file which only leaves one unit only partly filled.
One example being the 3.9Tb of supposed data Disk Cleaner would remove on a disk magnitudes smaller than that.
Another example pertains to this very version of IP where I copied a .esd file about 790 Mb large, extracted it and much to my surprise the sum of all files was several Gb. According to Windows the size on disk was only a couple hundreds of Mb...
Confusing but the answer must lie in the thousands of crosslinks I guess.
I wanted UEFI only and that's what I selected and the little b*stard reset it to Bios, UEFI CSM behind my back.
Naturally I didn't notice straight away as I was still talking to you guys.
Of course it did not boot so I had to start over again.
Since I use UEFI only I did it the easy way, quick formatted the stick to FAT32, mounted the ISO and copied everything over to the USB stick.
Little did I know that I had not updated Kari's ESD to ISO program so when it finally started setup it got stuck complaining about missing stuff.
When I saw what was going on on screen I had this deja vu feeling but the Euro didn't drop right away.
This morning however, having related my Alice in Wonderland story here, Kari was quick to point out that the ESD to ISO version I used was outdated.
So I started all over again and lo and behold it worked perfectly this time 'round.
Long story short, if you want to make a ISO for this IP then download the ESD from Kari's One Drive share and make sure to use his latest ESD to ISO program. It works very well indeed.
As many of you may have noticed, the upgrade install created a new Recovery partition behind the system partition of about 2 Gb. Always a nuisance to have it there and it nibbled the space to do so from the system partition too meaning you can no longer extend the system partition should need to without some serious shuffling about.
But, guess what, during the clean install I deleted all partitions bar my DATA one and surprise, surprise, all is back as we've known it.
No more 2Gb Recovery partition but just the 450MB Recovery one where it should be. In front of the system partition.
All in all I recommend this new version, it works very well. Well worth a clean install in my opinion. Besides, what else do you want to do between now and X-mass any way, right ?
As UUP becomes the de facto standard, though, I guess that we will see that new partition start popping up in clean installs as well.
I certainly hope that it is not going to happen any time soon, though.
Hermann Schinagl's Link Shell Extension in my folder structure to keep all the .ISOs that I have separated in a very organized tree but have them all easily accessible from a single location. Although my HD space doesn't actually change, Windows seems to think that I have more files on the storage drive than I actually do....
The only place I had issues was in Edge.
I downloaded Kari's install.esd and made an ISO. Used Rufus to make a start/boot disk and it booted with it. Museum has new showpiece now.
- Clean install - I assume this will work from a VM? If I have a lot of other programs installed (not clean) will the imaging process still capture the image, albeit a much larger, more comprehensive image of all my apps and such?
- I should capture the image after upgrading and fully allowing it to boot back into the workable envireonment, correct?
Neither of the VMs I made last night wanted to grab the update after I change the registry keys to grab the standard .ISO. I made 2 VMs, 1 on a 40 GB vd to install WinX normally, and one with dual drives, One 40 GB and one 20 GB, to keep testing the \User tree moving from build to build, both had the registry entries for UUP fixed.
I now plan to make a third VM, leaving UUP enabled, to test this method to grab the image and make the .ISO.
BTW, I was able to modify the ESDtoISO.cmd file to add the type of .ISO made into the filename as well. Now I can make both back to back and not worry about one overwriting the other