Windows 10: What is the new RecoveryImage directory?

Page 2 of 2 FirstFirst 12

  1. Posts : 154
    Windows 10 Technical Preview x64
       12 Oct 2014 #11

    essenbe said: View Post
    I have the technical Preview installed on 2 computers. One was through Windows Update and the other was through a clean install. I have done restores on both of them. neither time was one of the options I had to select to go back to Windows 7. They were always to go back to a clean install of technical preview, go to a clean install keeping my personal files (but not programs) or to wipe the disk clean.
    And that's the way it should be done Steve
      My ComputerSystem Spec


  2. Posts : 8,180
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       13 Oct 2014 #12

    Thanks, and BTW, I have system images of my Windows 7 with 3 different imaging programs. So, whatever happens, I'll be OK.
      My ComputersSystem Spec


  3. Posts : 43
    Windows 10 Enterprise x64
       14 Oct 2014 #13

    EvilJenius said: View Post
    That is exactly why [Prevents a Windows 10 upgrade from replacing the on-disk recovery image].
    But like adamf said, and I can confirm, this directory appears on upgrades of non-OEM installs of 8.1 that have no recovery directory in the first place, so there is nothing to save.

    I'm going to go ahead and move this directory off to another partition, and if nothing breaks with the next build upgrade, eventually delete it.
      My ComputerSystem Spec


  4. Posts : 804
    10 Pro Preview x64
    Thread Starter
       22 Oct 2014 #14

    At 9841 the file DONOTREPLACE.txt said this

    adamf said: View Post
    Code:
    Upgrade will not replace the on-disk recovery image if this file is present. Do not delete or modify this file.
    Build ID: 9841.0.amd64fre.fbl_release.140912-1613
    Upgrading to 9860 changed it to this
    Code:
    Upgrade will not replace the on-disk recovery image if this file is present. Do not delete or modify this file.
    Build ID: 9860.0.amd64fre.fbl_release.141008-2044
    but it did not update the drivers or wim - they remained the same as the initial install so it seems to work
      My ComputerSystem Spec


  5. Posts : 5,003
    Windows 10 Pro X64 15063.138
       22 Oct 2014 #15

    After 9860 is installed, the directory contains:

    Directory of c:\RecoveryImage

    10/21/2014 07:40 PM <DIR> .
    10/21/2014 07:40 PM <DIR> ..
    10/21/2014 07:40 PM 328 DONOTREPLACE.txt
    10/04/2014 02:22 AM <DIR> Drivers
    10/03/2014 10:08 PM 3,618,526,248 Install.wim
    10/03/2014 11:01 PM <DIR> OEMInformation
    2 File(s) 3,618,526,576 bytes
    4 Dir(s) 188,399,144,960 bytes free
      My ComputersSystem Spec

  6.    23 Oct 2014 #16

    Since you can't install Build 9860 directly, they are just leaving it so 9841 is the result of a Reset. Probably part of the exercise in upgrading an OS in stages over a long period.

    Since that Reset would be like a factory Reset to Windows 10 - 9841, I suppose if you had upgraded over 8.1 or 7, all that information would be lost. Maybe something to test if they don't get the Nvidia stuff straightened out!!
      My ComputerSystem Spec


  7. Posts : 5,003
    Windows 10 Pro X64 15063.138
       23 Oct 2014 #17

    I upgraded 8.1.1 Pro X64 to Win 10 TP then to build 9860. Results are as I listed for the C:\RecoveryImage directory.
      My ComputersSystem Spec


  8. Posts : 804
    10 Pro Preview x64
    Thread Starter
       23 Oct 2014 #18

    Ztruker said: View Post
    I upgraded 8.1.1 Pro X64 to Win 10 TP then to build 9860. Results are as I listed for the C:\RecoveryImage directory.
    Me too and I also have the wim not the ESD same as you.
      My ComputerSystem Spec


  9. Posts : 5,003
    Windows 10 Pro X64 15063.138
       23 Oct 2014 #19

    I believe the install.wim is from build 9841, the initial Windows 10 TP release. It will stay there as a way to refresh (I think) back to build 9841 when future updates are installed. I believe this is to address the broken refresh in Windows 8 and 8.1 but that's just a guess.

    So if you have install.wim it's for build 9841.
    If you have install.esd it's for build 9860.
      My ComputersSystem Spec

  10.    23 Oct 2014 #20

    Ztruker said: View Post
    So if you have install.wim it's for build 9841.
    If you have install.esd it's for build 9860.
    I have two systems. One was upgraded to build 9860 through Windows Update and one through PC Settings.

    The Windows Update one is showing the .esd file instead of the .wim file and dated Oct 22.

    The PC Settings upgrade is still showing the original .wim file.

    Since I do not know how to get info on an .esd file, even though it has a newer date, the properties show OCT. 9. So, is the .esd a image of 9860 or 9841, and if you believe they are different, why do you believe that?

    I would think Microsoft would want to keep any Reset computers running the same version of Windows 10 so it could be upgraded the same way.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
There's been a lot written about Win7's ever-expanding WINSXS subdirectory. In my Win7 install (which started out as a clean install) WINSXS is now 9.5GB in size. Granted, my system is several years old, but I know at some point the size or...
25771 I just noticed some change in the Get Windows 10 app..
I have started with 10130 and have 10166. I am not finding install.esd or C:\RecoveryImage in my installation. Somewhere in forum I read install.esd is available in $windows.~BtT folder. When I did search I am not finding it in C:\. Am I missing...
So, i have installed Windows 10 technical preview a while back using the media that I created from the 10041 build. Yesterday, via Fast Ring updates, I got the 10130 release installed. I was going to take the install.esd and make an...
I have installed build 10049 today. Why have I got a Windows.old directory dated 1st April 2015? :confused: The Windows directory is dated 31st March 2015 which makes sense.
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 06:53.
Find Us