Windows 8 and 8.1 Forums


Need help accessing Recovery partition

  1. #1


    Posts : 8
    Windows 8

    Need help accessing Recovery partition


    Hello Everyone,

    I have an Asus laptop. I am running Windows 8.1. I upgraded from 8 to 8.1 via the MS app store. I am having difficulty using the Windows 8 recovery option to do a completely fresh restore back to factory state.

    Each time I try to Restore back to factory state, the program starts and a few minutes later I am told my recovery environment partition is missing. I know it is there because Easeus shows it as available as does Windows Disk Management Tool.

    I have tried to run Recovery via settings.
    I have tried to run Recovery via F9 at startup.

    More Background Information:
    I did have a linux distro installed which is why I have many partitions as seen in screenshot.
    I naively did not make a Recovery USB drive when I got the laptop.

    I have attached a picture of Windows Disk Management Tool to show that the Recovery partition is there but with no letter. I am thinking I need to assign it a drive letter but the option isn't available when I right click on the partition. The only option available is, "help."

    In the screenshot, the two partitions labeled, New Volume and New Volume2 are old linux partitions.

    Any suggestions on how to access my Recovery environment to allow myself to reset back to factory state would be greatly appreciated.

    Click image for larger version

    thanks,
    Randy

      My System SpecsSystem Spec

  2. #2


    Posts : 1,121
    Windows 8.1 x64


    You might want to check post #72 in the linked thread.

    Unable to use built-in ASUS recovery partition

    There may be some other posts in the thread that could be relevant also.

    Make sure you run the reagentc /info command so we can see what it might be doing.
      My System SpecsSystem Spec

  3. #3


    Posts : 8
    Windows 8


    Thank you for the link to the recovery thread. I did run reagentc /info and it returned a message something like, Operation Failed: 3 Error.
      My System SpecsSystem Spec

  4. #4


    Posts : 1,121
    Windows 8.1 x64


    Are you going to verify your situation using Diskpart and Repair using the procedure?

    I wish I knew how to repair the Volume Information for the partition without having to change the Partition Types, but I don't. Maybe someone else would.
      My System SpecsSystem Spec

  5. #5


    Posts : 8
    Windows 8


    As I was reading through the thread you suggested I look at, I saw that since the reagentc /info command failed for me, and it did for the person in that thread, I ran this command that you suggested, bcdedit /enum all > %userprofile%\Desktop\bcdtext.txt
    I hope it applied to my situation and will offer you some information.

    I wasn't sure what was meant by 'verify your situation using Diskpart'.

    Here are the results. I pasted them in code blocks, to hopefully not ruin the formatting.
    Thanks again, Randy

    Code:
    
    
    Firmware Boot Manager
    ---------------------
    identifier              {fwbootmgr}
    displayorder            {bootmgr}
                           {b475378b-c28f-11e3-8c62-806e6f6e6963}
                           {b475378a-c28f-11e3-8c62-806e6f6e6963}
    timeout                 2
    
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                 partition=\Device\HarddiskVolume1
    path                   \EFI\Microsoft\Boot\bootmgfw.efi
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {current}
    resumeobject           {d6fa96e4-4124-11e2-8ff5-cdc51c76d3ec}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    
    Firmware Application (101fffff)
    -------------------------------
    identifier             {b475378a-c28f-11e3-8c62-806e6f6e6963}
    device                 partition=\Device\HarddiskVolume1
    path                    \EFI\ubuntu\grubx64.efi
    description             ubuntu
    
    
    Firmware Application (101fffff)
    -------------------------------
    identifier             {b475378b-c28f-11e3-8c62-806e6f6e6963}
    device                 partition=\Device\HarddiskVolume1
    path                    EFI\Ubuntu\grubx64.efi
    description             ubuntu
    
    
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                   \Windows\system32\winload.efi
    description             Windows 8
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence       {d6fa96e7-4124-11e2-8ff5-cdc51c76d3ec}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject           {d6fa96e4-4124-11e2-8ff5-cdc51c76d3ec}
    nx                      OptIn
    bootmenupolicy          Standard
    
    
    Windows Boot Loader
    -------------------
    identifier             {d6fa96e6-4124-11e2-8ff5-cdc51c76d3ec}
    device                 ramdisk=[\Device\HarddiskVolume2]\sources\boot.wim,{ramdiskoptions}
    path                   \windows\system32\boot\winload.efi
    description             WinPE
    osdevice               ramdisk=[\Device\HarddiskVolume2]\sources\boot.wim,{ramdiskoptions}
    systemroot              \windows
    nx                      OptIn
    detecthal               Yes
    winpe                   Yes
    
    
    Windows Boot Loader
    -------------------
    identifier             {d6fa96e7-4124-11e2-8ff5-cdc51c76d3ec}
    device                 ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{d6fa96e8-4124-11e2-8ff5-cdc51c76d3ec}
    path                   \windows\system32\winload.efi
    description             Windows RecoveryEnvironment
    locale                  en-us
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice               ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{d6fa96e8-4124-11e2-8ff5-cdc51c76d3ec}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    
    
    Resume from Hibernate
    ---------------------
    identifier             {d6fa96e4-4124-11e2-8ff5-cdc51c76d3ec}
    device                  partition=C:
    path                   \Windows\system32\winresume.efi
    description             Windows ResumeApplication
    locale                  en-US
    inherit                 {resumeloadersettings}
    recoverysequence       {d6fa96e7-4124-11e2-8ff5-cdc51c76d3ec}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    filedevice              partition=C:
    filepath                \hiberfil.sys
    bootmenupolicy          Standard
    debugoptionenabled      No
    
    
    Windows Memory Tester
    ---------------------
    identifier              {memdiag}
    device                 partition=\Device\HarddiskVolume1
    path                   \EFI\Microsoft\Boot\memtest.efi
    description             Windows MemoryDiagnostic
    locale                  en-US
    inherit                 {globalsettings}
    badmemoryaccess         Yes
    
    
    EMS Settings
    ------------
    identifier              {emssettings}
    bootems                 No
    
    
    Debugger Settings
    -----------------
    identifier              {dbgsettings}
    debugtype               Serial
    debugport               1
    baudrate                115200
    
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    
    Global Settings
    ---------------
    identifier              {globalsettings}
    inherit                 {dbgsettings}
                            {emssettings}
                            {badmemory}
    
    
    Boot Loader Settings
    --------------------
    identifier              {bootloadersettings}
    inherit                 {globalsettings}
                            {hypervisorsettings}
    
    
    Hypervisor Settings
    -------------------
    identifier              {hypervisorsettings}
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    
    
    Resume Loader Settings
    ----------------------
    identifier              {resumeloadersettings}
    inherit                 {globalsettings}
    
    
    Setup Ramdisk Options
    ---------------------
    identifier              {ramdiskoptions}
    description             Ramdisk options
    ramdisksdidevice       partition=\Device\HarddiskVolume2
    ramdisksdipath          \boot\boot.sdi
    
    
    Device options
    --------------
    identifier             {d6fa96e8-4124-11e2-8ff5-cdc51c76d3ec}
    description             Windows Recovery
    ramdisksdidevice       partition=\Device\HarddiskVolume2
    ramdisksdipath         \Recovery\WindowsRE\boot.sdi
      My System SpecsSystem Spec

  6. #6


    Posts : 1,121
    Windows 8.1 x64


    This is not a BCD store problem. EaseUS seems to remove the volume information from the recovery partitions on UEFI installs. The only way I know of to get it back is to change the Type ID of the Recovery partition to a General Data partition, like the OS partitions, reboot and then change the Type ID and Attribute back to the Recovery partition.

    The linked post shows what the commands are to accomplish this. If you need help with diskpart, let us know. The commands can use just the first three letters for most, although some cannot. But lis is list, par is partition, and so on.

    The recovery partition Type ID I know about is shown below. When you detail the partition, make sure the ASUS Type ID is the same, or copy it somewhere to keep. You can copy and paste into, out of, and within a Command Prompt window.

    de94bba4-06d1-4d40-a16a-bfd50179d6ac

    So to check you first recovery partition, open an Administrative command prompt. Type these command with enter after each. Use the Disk and partition numbers from the listing obtained with the list commands.

    Diskpart
    list disk
    sel dis 0
    lis par
    sel par 2
    detail par

    You would then use the commands below to change the Type ID and Attributes

    set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    This sets the partition to a Data partition. Reboot and change the Type ID and Attributes back to the original.

    set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

    gpt attributes=0x8000000000000001

    EaseUS has been notified about this situation, but to this time I have received no response from them. But I hope they will repair their software and put out a utility which will correct the problem for their users.
      My System SpecsSystem Spec

  7. #7


    Posts : 5,592
    ME, XP,Vista,Win7,Win8,Win8.1


    Quote Originally Posted by Saltgrass View Post
    You might want to check post #72 in the linked thread.

    Unable to use built-in ASUS recovery partition

    There may be some other posts in the thread that could be relevant also.

    Make sure you run the reagentc /info command so we can see what it might be doing.
    Also take a look at posts 55 & 70.
      My System SpecsSystem Spec

  8. #8


    Posts : 8
    Windows 8


    Quote Originally Posted by Saltgrass View Post
    This is not a BCD store problem. EaseUS seems to remove the volume information from the recovery partitions on UEFI installs. The only way I know of to get it back is to change the Type ID of the Recovery partition to a General Data partition, like the OS partitions, reboot and then change the Type ID and Attribute back to the Recovery partition.

    The linked post shows what the commands are to accomplish this. If you need help with diskpart, let us know. The commands can use just the first three letters for most, although some cannot. But lis is list, par is partition, and so on.

    The recovery partition Type ID I know about is shown below. When you detail the partition, make sure the ASUS Type ID is the same, or copy it somewhere to keep. You can copy and paste into, out of, and within a Command Prompt window.

    de94bba4-06d1-4d40-a16a-bfd50179d6ac

    So to check you first recovery partition, open an Administrative command prompt. Type these command with enter after each. Use the Disk and partition numbers from the listing obtained with the list commands.

    Diskpart
    list disk
    sel dis 0
    lis par
    sel par 2
    detail par

    You would then use the commands below to change the Type ID and Attributes

    set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    This sets the partition to a Data partition. Reboot and change the Type ID and Attributes back to the original.

    set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

    gpt attributes=0x8000000000000001

    EaseUS has been notified about this situation, but to this time I have received no response from them. But I hope they will repair their software and put out a utility which will correct the problem for their users.

    Thanks for the information. I was under the weather for a couple days and now ready to think about this again...

    I tried post 55 option to solve my problem. I got all the way to copying my install.wim file to the sources folder, and wouldn't you know, and error shows that my jump drive doesn't have enough space. It does, though. The file is about 8 or 9 GB and file jump drive is 32GB.

    So I thought I would give your instructions in my thread a try.
    I want to be sure I have this correct before I try.

    1. I have the detailed information about partition 2 on disk 0. (Not sure if this needs to be known, but this appears to be the recovery partition as the id was already de94bba4-06d1-4d40-a16a-bfd50179d6ac)
    2. After getting to Disk 0, Partition 2 selected, I use, set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 in the elevated command prompt.
    3. I reboot.
    4. Upon rebooting, I open an elevated command prompt, type set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
    and I also type gpt attributes=0x8000000000000001.
    5. I then reboot and go to settings and try the typical system restore process.

    Does this appear to be the correct steps?

    Thank you again for the time and help,
    Randy
      My System SpecsSystem Spec

  9. #9


    Posts : 1,121
    Windows 8.1 x64


    You have 3 recovery partitions that are corrupted, but you have the procedure correctly. The important ones are probably the 350 MB and the 20 GB ones. You might as well repair all three partitions to get your system back to normal. Remember, copy and paste saves a lot of typing.

    You can do all three partitions at the same time, just select those partitions. It only takes a couple of minutes to do this procedure, so if you want to continue with the other procedure, you haven't lost anything.
      My System SpecsSystem Spec

  10. #10


    Posts : 8
    Windows 8


    Yes, I love copy paste, too. Nothing better than ctrl+C, ctrl+V, well except ctrl+A, ctrl+C, ctrl+V in my opinion. Anyway...

    I was able to "relabel" three partitions to Recovery partitions. I did have progress, meaning, now I can create a recovery jump drive. I did that. I can at least now, initiate the Reset process. When I do, I get started and I do the various clicking from, 'yes, rewipe all drive', to click a final button that says, 'Reset'. The problem is, if I do this from settings when running the laptop or if I boot from the jump drive, both ways result in an error saying unable to complete reset, nothing was changed.

    I was able to run reagentc /info now. I have attached the screenshot of the results.


    Click image for larger version


    I'm not sure where to go from here.

    Thank you,
    Randy
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Need help accessing Recovery partition
Related Threads
Well I finished my project - the program script allows me to create MBR and GPT hard drive partitions with a recovery image partition. The script also allows me to install 3 different versions of windows. and lastly it allows me to capture a recovery (push button reset) image. which can then be...
Hello, i'm using Windows 8 Home 64 Bit. I used AOMEI Partition Assistant Standard to add a NTFS Partition to my USB drive. I want to store large files over 4GB on this partition, while having the rest of my files on the primary partition which is FAT32. The problem is, when I plug my drive into...
If you have a recovery drive - that includes the recovery partition - made on one computer, but have a toshiba laptop with a bad drive (but the recovery partition is ok), can you replace/copy the partition on the recovery drive with the recovery partition from the bad laptop HD? My friend's...
Hi, I'm not the most computer savvy person out there-so I may need extra explaining. I have an Asus ux32a zenbook and basically, I was wanting to reinstall my windows 8 back to the factory settings. Long story short, my recovery image I saved is deleted and I may have started formating my hard...
I'm wondering if anyone can help me out here; I have a strange situation. I'm running Windows 8 and I have an external hard drive that won't let me access 900GB or so of its 1TB. The drive mounts about 10GB, and the rest is nowhere to be found. If I go into Disk Manager I can see both of them: the...
I have a Samsung Ultrabook series 5 laptop..some couple of month usage i completely remove my hard drive and change the windows 8 to windows 7..when i use windows 7 i realize windows 8 is much better then windows 7 so again i clean install of windows 8. i boot drive in PXE UEFI Only Mode.​Some...
Hello everyone, I'm a technician at TigerDirect, and for one of our services we create recovery media for newly purchased machines. For Windows 8 machines (As I'm sure you know) we cannot create recovery disks, and have to create a recovery drive using a flash drive. On multiple occasions...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook