Fresh Install Windows 10 TP Build 9860

Page 2 of 3 FirstFirst 123 LastLast
  1. Ztruker's Avatar
    Posts : 10,255
    Windows 10 Pro X64 1909 18363.815
       #11

    I'll see what turns up after the update of the Win 10 TP running under Hyper-V finishes. I'll look for install.esd and install.wim, see if it turns up anywhere.
      My Computers

  2. Kari's Avatar
    Posts : 17,113
    Windows 10 Pro
       #12

    Ztruker said:
    I'll see what turns up after the update of the Win 10 TP running under Hyper-V finishes. I'll look for install.esd and install.wim, see if it turns up anywhere.
    Enable showing hidden items, then search the drive C: for EXT:ESD and EXT:WIM.
      My Computer

  3. Ztruker's Avatar
    Posts : 10,255
    Windows 10 Pro X64 1909 18363.815
       #13

    EXT:ESD turned up C:\RecoveryImage\install.esd. Nothing for EXT:WIM.

    I downloaded 9860 yesterday but did not install till this morning. This is what I see:

    Fresh Install Windows 10 TP Build 9860-after-9860.png

    so this time I got a install.esd and not install.wim. No idea what is going on and why I got install.esd here and install.wim on my Acer Laptop.

    The only difference I can think of is the Acer Laptop was upgraded from Windows 8.1.1 to Windows 10 TP then 9860 build. The Hyper-V VM was a clean install of Win 10 TP then upgrade to build 9860.
      My Computers

  4. Kari's Avatar
    Posts : 17,113
    Windows 10 Pro
       #14

    Ztruker said:
    The only difference I can think of is the Acer Laptop was upgraded from Windows 8.1.1 to Windows 10 TP then 9860 build. The Hyper-V VM was a clean install of Win 10 TP then upgrade to build 9860.
    I am at the moment upgrading 8.1 to 10 TP Build 9841 to test this scenario if it explains this ESD <> WIM dilemma. Got the idea from Adam's post which you now confirmed.
      My Computer

  5. Pendaws's Avatar
    Posts : 327
    Windows 10 Pro 64bit 1909 (18363.836)
       #15

    topgundcp said:
    If you have multiple PC's to update or having trouble updating VM or don't want to see multiple Recovery partitions created from the update.

    If you've already have the C:\RecoveryImage folder or if someone can put it in the dropbox for you to download.


    1. Download: esd-decrypter-v3 and unzip to the desktop
    2. Copy the content of the RecoveryImage folder into the same place where decrypt.cmd is
    3. Open Admin Command Prompt and type: decrypt install.esd
    4. Select option 3 or 4 (use 4 if you want to customize the installation)
    5. Use Rufus - Create bootable USB



    Hope this helps.
    Cheers
    I got the link from: Chris 123 Blog
    The link for ESD you added is not working. I found a link for the latest version, 4C ESD 4C
      My Computer

  6. davehc's Avatar
    Posts : 513
       #16

    Ztruker said:
    EXT:ESD turned up C:\RecoveryImage\install.esd. Nothing for EXT:WIM.


    The only difference I can think of is the Acer Laptop was upgraded from Windows 8.1.1 to Windows 10 TP then 9860 build. The Hyper-V VM was a clean install of Win 10 TP then upgrade to build 9860.
    You have answered you query with the last sentence. You get the ESD with a clean install and the wim with an upgrade.

    I have no idea why the mechanics of installing are making it work like this. But, the Wim is the "Windows to go" item, which is available in the enterprise release only??
      My Computer


  7. Kari's Avatar
    Posts : 17,113
    Windows 10 Pro
       #17

    davehc said:
    You get the ESD with a clean install and the wim with an upgrade.

    I have no idea why the mechanics of installing are making it work like this. But, the Wim is the "Windows to go" item, which is available in the enterprise release only??
    The WIM (Windows IMaging) is the normal file format for installing Windows, you can take any install media (DVD / USB / ISO) for any Windows version and edition and browse to its Sources folder, the file install.wim will be there. It is the Windows; it contains everything to install Windows. It is a big file, about 90% of the total size of the Windows install disk or ISO. In Windows 10 Technical Preview's case, the size of the installation ISO is 3.7 GB including a 3.3 GB install.wim.

    The ESD (Electronic Software Delivery) is a relatively new highly compressed file format used by Microsoft for delivering Windows upgrades. Basically it is nothing else than a compressed WIM file, reducing the size needed to be downloaded with almost 30%. It was first time used in Windows 8 to 8.1 upgrades, the upgrade when launched from Windows Store downloaded the ESD file.

    From our (users) point of view ESD saves both time and bandwidth needed for the download, for example the ESD file for the build 9860 x64 is 2.58 GB whereas the same as WIM file is 3.3 GB. The bootable ISO file created from either of them is 3.7 GB.

    I did some quite extensive testing yesterday and last night to find out in which cases the user gets the build upgrade as WIM and and in which cases as ESD. Results can be seen in this post in the tutorial thread: ESD to ISO - Create Bootable ISO from Windows 10 ESD File

    Kari
      My Computer

  8. John Pombrio's Avatar
    Posts : 402
    Windows 10 Fast Ring
       #18

    I have Win10 Pro (not Enterprise) and I got an .ESD file with my 9860 update. Using this link with its latest Decrypt tool:

    Get ISO image for Windows 10 build 9860 for a clean install | Winaero

    I now have a Win 10 9860 ISO file.

    I wonder how I know that the install.esd file I am using is for the 9860 update tho? It SEEMS to be but...

    My final .iso file

    JM1_CPRA_X64FRER_EN-US_DV9.iso

    Fresh Install Windows 10 TP Build 9860-2014-10-24_151719.jpg
      My Computer

  9. Kari's Avatar
    Posts : 17,113
    Windows 10 Pro
       #19

    John Pombrio said:
    I have Win10 Pro (not Enterprise) and I got an .ESD file with my 9860 update. Using this link with its latest Decrypt tool:
    The Ten Forums tutorial for the same, with a simplified decrypter: ESD to ISO - Create Bootable ISO from Windows 10 ESD File

    John Pombrio said:
    I wonder how I know that the install.esd file I am using is for the 9860 update tho? It SEEMS to be but...
    The file install.esd (Win10 TP clean install) or install.wim (Win10 TP upgraded from 8.1) in folder C:\RecoveryImage is for the currently installed build as this was the first build upgrade you did. In your case now the file is build 9860 and will only be replaced when you upgrade to next build if you delete the whole folder which upgrade will then recreate, or at least delete the marker file DONOTREPLACE.txt file in said folder.

    If the marker file is not deleted prior to upgrade to next build ithe ESD file in C:\RecoveryImage will remain build 9860 and the upgraded build ESD file will be found in C:\$Windows.~BT\Source (notice: C:\$Windows.~BT is a hidden folder).
      My Computer

  10. gregrocker's Avatar
    Posts : 281
       #20

    I am downloading the latest build .iso file now because it wouldn't download via Settings>Upgrade Builds.

    Is there a way to run it as an Upgrade of 9841 which was Clean installed?

    How does the Recovery folder work for Clean Installs? Does it only provide the Reset and Refresh, or do something more?

    Does the Do Not Delete file only pertain to preserving Factory Recovery partitions for those particular Upgrades, or 8/8.1 Recovery via Reset/Refresh?
      My Computer


 

Related Threads
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 15:19.
Find Us




Windows 10 Forums