Announcing Windows 10 Insider Preview Build 14986 for PC Insider

Hi,

I looked at its contents before and after set up terminated and after ran disk clean up.
It contains about 333 MB of the pre-existing recovery partition leaving that with a small amount of files after cleanup, prior that it's quite filled up.
So, I guess it's used during setup as an isolated scratch area.

So when all has settled down you have an almost empty original Recovery partition and a rather chunky new partition containing these 300Mb something of files.
My guess is that MS still has work to do to perfect (but then they never do that, do they ?) the UUP delivery process.

Running reagentc /info reveals that the new recovery partition is now the one it's pointing to. So we loose around 1.8 Gb of real estate in the upgrade process.
Too bad I already deleted the image I made of it but for sure someone can mount his/hers to verify its contents by mounting and exploring their MR backup.

Cheers,

fjk61011 said:

There was a file in the Windows directory Professional_en-gb.esd which unzipped to three folders. Folder 1 has a setup file which properties gives as 14986. I'm wondering what it's for.

By "unzipped", I guess you are referring to 7-Zip unarchiving and expanding the Professional_en-gb.esd file to give this view in the 7-Zip file manager - is this what you mean? :



The 3 indexed images, according to the XML metadata, are 1: Setup, 2: WinRE, and 3: Windows 10 Insider Preview (Build14986.1000).

Presumably there are other xml files which allow the Windows UUP update processing program to create the full Install.esd from the mass of ESD and CAB files in the Download folder, some of which are seen here:

Hi,

Presumably there are other xml files which allow the Windows UUP update processing program to create the full Install.esd from the mass of ESD and CAB files in the Download folder, some of which are seen here:

That would be missing the entire point of using UUP, wouldn't you say ?

Cheers,

fdegrove said:

Hi,
Presumably there are other xml files which allow the Windows UUP update processing program to create the full Install.esd from the mass of ESD and CAB files in the Download folder, some of which are seen here:
That would be missing the entire point of using UUP, wouldn't you say ?
Cheers,

I should have added: "If the registry entries to disable UUP were present" after "full Install.esd"

Now this is Microsoft Windows, not an Open Source OS. Obfuscation has always been the name of the game, and changing the process regularly keeps those geeks like us wondering, or at least second guessing. In the absence of an Install.esd, it is difficult to measure the sum total of the downloaded component sizes.

I discovered long ago that you could sometimes do a repair of Windows 7 by applying (imagex.exe) an install.wim from a custom Windows 7 wim backup directly to a damaged Windows 7 installation. It seems that here a similar process is going on - an in-place replacement of changed components, but until there is a standard set of Windows components on the machine to be upgraded (i.e. managed by some unified cumulative update process), there is no way to guarantee a successful unified build upgrade without downloading all the possible components just in case that something is missing from the existing installation that would cause the upgrade to fail.

Remember Microsoft cannot issue Service Packs any longer because they stopped issuing them. A rose by any other name... :)

In the Install.esd files for previous builds there were 4 indexed images - 1 Setup, 2 WinPE, 3 WinRE,and 4 Windows 10
In this new case the specific WinPE image seems to be missing.

Here is my Drive 0 partition layout after upgrading via WU to 14986 from 14971:



Note the new 1.97 GB partition added to my SSD boot drive, Drive 0...

I wasn't actually expecting this... I see several others in the thread also got this, too....Also noted that my free space on c:\boot actually increased a couple of GBs from what Windows was reporting free in 14971...(Drive H:\boot is my backup partition of c:\--it holds a clone image plus a full Win7 Backup image with System image, etc.)...

johngalt said:

1. How much free space did it show before?
2. Had you run DiskClean on it?
3. Was that 23GB unallocated space already there?
4. That new partition is if you leave UUP enabled.

Yes, interestingly enough, the increase came in the measurement after using DiskCleanup fully in both builds (as I always do after I ascertain the new build is running my software without a problem)--I remove all the files relative to the build install except for the ~3GBs or so that need to be there for a Refresh, repair, etc. After 14971 it was showing roughly ~90 GBs free; after 14986 it's ~92GB free...It's not a big deal, really, just interesting. It could be that after I installed 14986 I might've deleted some older AMD GPU driver files myself, emptied some long-neglected trash--or the Windows file-space reporting mechanism might be including the new partition space...don't recall...

The unallocated space is what Samsung recommends for my SSD--10% unallocated so if bad blocks pop up it can borrow from the unallocated space transparently--at least that's what I gather, anyway.