Page 54 of 88 FirstFirst ... 444525354555664 ... LastLast

  1. Joined : Nov 2014
    Floyd, VA
    Posts : 298
    Windows 10 Build 15007
       12 Dec 2016 #531

    Interesting. Buildfeed still shows the latest build as the one we are on - 14986 compiled on Dec 2. Of course I understand buildfeed (like this forum) are not official Microsoft sites. Maybe the "leaker" has been brought to heel?
      My System SpecsSystem Spec


  2. Joined : Oct 2015
    Posts : 1,390
    Windows 10 Pro X64
       12 Dec 2016 #532

    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,
      My System SpecsSystem Spec


  3. Joined : Dec 2013
    Portsmouth Hampshire
    Posts : 1,195
    Windows 10 x86 14383 Insider Pro and Core 10240
       12 Dec 2016 #533

    fjk61011 said: View Post
    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? :

    Click image for larger version. 

Name:	Screenshot (65).png 
Views:	9 
Size:	134.2 KB 
ID:	113390

    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:

    Click image for larger version. 

Name:	Screenshot (64).png 
Views:	11 
Size:	164.3 KB 
ID:	113391
      My System SpecsSystem Spec


  4. Joined : Oct 2015
    Posts : 1,390
    Windows 10 Pro X64
       12 Dec 2016 #534

    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,
      My System SpecsSystem Spec


  5. Joined : Feb 2015
    3rd Rock
    Posts : 345
    WinX Pro x64 IP v14986
       12 Dec 2016 #535

    fdegrove said: View Post
    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,
    However, as you noted, this is all new. They're playing around trying to figure out how to work this best.

    My suppositions:
    1. The isolated scratch are is a good way to look at it - but there may be more to it than that.
    2. When all this settles down we will probably loes the original recovery partition, giving us back ~450 MB of real estate.
    3. This is still new, and future downloads on UUP enabled machines may be a lot smaller considering what is already in that new partition.

    Guess we'll just have to wait and see.

    Fafhrd said: View Post
    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? :

    Click image for larger version. 

Name:	Screenshot (65).png 
Views:	9 
Size:	134.2 KB 
ID:	113390

    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:

    Click image for larger version. 

Name:	Screenshot (64).png 
Views:	11 
Size:	164.3 KB 
ID:	113391
    Correct. Setup (I'm assuming WinPE), WinRE (recovery) and the actual install files. however, #3 still doesn't lead to an easy .ISO generation.

    fdegrove said: View Post
    Hi,

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

    Cheers,
    Not if you consider that this is the first iteration of it. Future iterations may not have 1 and / or 2, just 3....
      My System SpecsSystem Spec


  6. Joined : Dec 2013
    Portsmouth Hampshire
    Posts : 1,195
    Windows 10 x86 14383 Insider Pro and Core 10240
       12 Dec 2016 #536

    fdegrove said: View Post
    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.
      My System SpecsSystem Spec


  7. Joined : Oct 2014
    Posts : 302
    10x64
       12 Dec 2016 #537

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

    Click image for larger version. 

Name:	NewPartitionAddedby14986.png 
Views:	13 
Size:	244.4 KB 
ID:	113396

    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.)...
      My System SpecsSystem Spec


  8. Joined : Feb 2015
    3rd Rock
    Posts : 345
    WinX Pro x64 IP v14986
       12 Dec 2016 #538

    waltc said: View Post
    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.)...
    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.
      My System SpecsSystem Spec


  9. Joined : Oct 2014
    Posts : 302
    10x64
       12 Dec 2016 #539

    johngalt said: View Post
    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.
      My System SpecsSystem Spec

  10.    13 Dec 2016 #540

    I've finally got this release working in VirtualBox without continual BSODS. The problem appears to be with the display driver. This is the workaround for any others in this situation.

    1. Boot into safe mode.
    2. Uninstall the VirtualBox Guest Additions from the control panel programs and features.
    3. Shut the VM down.
    4. Navigate to the VM definition files and edit the .vbox file in a text editor. I use Notepad++
    5. Locate the <ExtraData> section
    6. Add a line like this
    <ExtraDataItem name="CustomVideoMode1" value="1366x768x32"/>

    The values specified should be your monitor resolution width x height x bit depth

    7. Boot in full screen mode. This will probably come up in a 4:3 aspect ratio
    8. Right click the desktop and select Display Settings.
    9. Select Advanced Display Settings and then your desired resolution from the dropdown.

    Future boots will come up in this display mode. Obviously you have lost the advantages of Guest Additions but it is very usable in full screen mode.
      My System SpecsSystem Spec


 
Page 54 of 88 FirstFirst ... 444525354555664 ... LastLast


Similar Threads
Thread Forum
Insider Announcing Windows 10 Insider Preview Build 14366 & Mobile Build 14364
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 11102
690233336740974592 Source: Announcing Windows 10 Insider Preview Build 11102 | Windows Experience Blog
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 10565
UPDATE 3: Microsoft Releases PC build 10565 to Insiders in the Slow ring today. 655071954639020032 UPDATE 2: Download: https://www.tenforums.com/tutorials/9230-windows-10-iso-download.html#option3
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 10130 for PCs
Source: http://blogs.windows.com/bloggingwindows/2015/05/29/announcing-windows-10-insider-preview-build-10130-for-pcs https://www.tenforums.com/tutorials/2451-preview-builds-check-new-windows-10-builds.html
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 10122 for PCs
Source: http://blogs.windows.com/bloggingwindows/2015/05/20/announcing-windows-10-insider-preview-build-10122-for-pcs/ https://www.tenforums.com/tutorials/2451-preview-builds-check-new-windows-10-builds.html UPDATES: 601080802793922560
Windows 10 News
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:56.
Find Us
Twitter Facebook Google+



Windows 10 Forums