Getting 0xc0000225 error when entering Recovery mode-Win81

[genet]

- Recovery partition (Windows RE tools partition and Recovery image partition)

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

gpt attributes=0x8000000000000001

 

[arcturius]

Yes, done. Marked 1, 5, 6 partitions as recovery. Marked #1 partition with gpt attr.

Results:

DISKPART> list partition


Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 1000 MB 1024 KB
Partition 2 System 260 MB 1001 MB
Partition 3 Reserved 128 MB 1261 MB
Partition 4 Primary 217 GB 1389 MB
Partition 5 Recovery 350 MB 218 GB
* Partition 6 Recovery 12 GB 218 GB
Partition 7 Primary 7167 MB 231 GB

Screenshot attached.

 

[topgundcp]

Now it does look correct with partitions layout. At this point I suggest that you make a backup of the BCD store then use Visual BCD to repair: Visual BCD Download

NOTE: If you are running 64 bit, Visual BCD will pop up an error message at the beginning, just ignore it. From the Menu, click on Repair->Repair BCD

 

[genet]

Yes, done. Marked 1, 5, 6 partitions as recovery. Marked #1 partition with gpt attr.

Also partitions 5 and 6.

Type reagentc /info and post the result.

edit:

rem == CreatePartitions.txt ==
rem == These commands are used with DiskPart to
rem    create five partitions
rem    for a UEFI/GPT-based PC.
rem == Usage: diskpart /s ScriptFileName
rem == Example: diskpart /s D:\CreatePartitions.txt
rem ================================================
select disk 0
clean
convert gpt
rem == 1. [COLOR=#ff0000]Windows RE tools partition[/COLOR] ===============
create partition primary size=1000
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
[COLOR=#ff0000]set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001[/COLOR]
rem == 2. System partition =========================
create partition efi size=260
format quick fs=fat32 label="System"
assign letter="S"
rem == 3. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 4. Windows partition ========================
rem ==    a. Create the Windows partition ==========
create partition primary
rem ==    b. Create space for the recovery image ===
shrink minimum=20480
rem       ** NOTE: Update this size to match the size
rem                of the recovery image           **
rem ==    c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 5. [COLOR=#ff0000]Recovery image partition [/COLOR]=================
create partition primary
format quick fs=ntfs label="Recovery image"
assign letter="R"
[COLOR=#ff0000]set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001[/COLOR]
rem ================================================
list volume
exit

 

[arcturius]

I dont see any duplicate {bookmgr} in the Visual BCD (see attached screen shot). Run 'repair' in Visual BCD anyway. I am sending the result of reagentc /info.

C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:


Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 76d67320-3c71-11e4-8226-c8d0021f90
3f
Recovery image location:
Recovery image index: 1
Custom image location:
Custom image index: 0


REAGENTC.EXE: Operation Successful.

Updated partition 5,6 with gpt attr.

As a test, tried to run:

C:\windows\system32>reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\p
artition1\Recovery\WindowsRE
REAGENTC.EXE: The Windows RE image cannot be stored in the specified volume. Use
the RETAIN command in DISKPART to prepare the volume and try again.

 

[arcturius]

Thanks. That's what I did.

Yes, done. Marked 1, 5, 6 partitions as recovery. Marked #1 partition with gpt attr.

Also partitions 5 and 6.

Type reagentc /info and post the result.

edit:

rem == CreatePartitions.txt ==
rem == These commands are used with DiskPart to
rem    create five partitions
rem    for a UEFI/GPT-based PC.
rem == Usage: diskpart /s ScriptFileName
rem == Example: diskpart /s D:\CreatePartitions.txt
rem ================================================
select disk 0
clean
convert gpt
rem == 1. [COLOR=#ff0000]Windows RE tools partition[/COLOR] ===============
create partition primary size=1000
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
[COLOR=#ff0000]set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001[/COLOR]
rem == 2. System partition =========================
create partition efi size=260
format quick fs=fat32 label="System"
assign letter="S"
rem == 3. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 4. Windows partition ========================
rem ==    a. Create the Windows partition ==========
create partition primary
rem ==    b. Create space for the recovery image ===
shrink minimum=20480
rem       ** NOTE: Update this size to match the size
rem                of the recovery image           **
rem ==    c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 5. [COLOR=#ff0000]Recovery image partition [/COLOR]=================
create partition primary
format quick fs=ntfs label="Recovery image"
assign letter="R"
[COLOR=#ff0000]set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001[/COLOR]
rem ================================================
list volume
exit

 

[Saltgrass]

I have not used the path description since I haven't had a situation to do so, but I will a little later. But someone in another forum said it should work.

Since it doesn't seem to be working, you will need to put a drive letter on it again to set this up. Use the R: or T: type letter and not one that might be used by another device.

 

[topgundcp]

Since it doesn't seem to be working, you will need to put a drive letter on it again to set this up. Use the R: or T: type letter and not one that might be used by another device.

This is what I suggested in this thread:
http://www.eightforums.com/general-support/53334-could-not-find-recovery-environment.html#post425220

 

[Saltgrass]

Well, I have been playing and will provide the results. I am not suggesting you do anything, but maybe it will help.

For the sake of brevity, I will just say I messed up my system and then tried to reset it back to the original configuration. I had no problem using reagentc to set the RE image, even using the alternate path I mentioned earlier. But since you have already done that, I will just say I was still getting the Disabled indication in the reagentc /info listing. I checked the BCD store and everything looked normal, but it would not enable even though it said it was successful.

So I decided to see if the Recovery Tools would work and used the PC Settings, Recovery to boot back into the Advanced options. After the reboot, I was presented with 3 options and chose the Troubleshooting one. Then the Startup Settings one where I was given the F8 options only. Since I did not want anything there, I went back to the first menu and choose "Continue to Window 8.1", which booted the system into Windows. When I checked the Reagentc /info listing, it was showing as enabled and the RE image location was indicating correctly.

Things I noticed during the process. The original Winre.wim file, and the entire directory structure, had been removed from its original location. I do not know how this happened but I will being going through the process again to see if I can find out.

Also, after the reboot was complete, the Recovery Partitions had been assigned drive letters. If I removed those in Diskpart, the Recovery option would go to Disabled again, so don't remove those if they show up. I will get back after some more testing concerning this.

I will have more information by tomorrow. I never got the message you got with the alternate path related to the Retain option in Diskpart. Since that options seems to be related to a Dynamic volume not sure what would cause the message in your case.

 

[Saltgrass]

I just re-ran the test on the same install as before. This time I ran into no problems and the recovery system re-enabled without problems.

Commands I used to switch the Winre.wim being used.

reagentc /disable
reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
reagentc /enable

You might even want to try setting it to the 350 MB partition to see if that can be done.

I did not have to set any drive letters. Why this time I encountered no problems, not really sure. I had removed the entries in the Registry which were setting the partition drive letters in the HKLM\System\MountedDevices section.

I also noticed this time, the GUID number in the BCD store for the Recoverysequence changed where in the first test, it did not change.

So, I will say, make sure you are supposed to be using partition 1 for your Recovery Tools partition. Then use Diskpart and do a det par on that partition and post the results. You can copy from the Command Prompt window by using the right click "Mark" option.

If the partition looks normal, we can then run through the trying the recovery tools and see if that will allow the tools to be enabled.

 

[arcturius]

Tried to assign a letter to the first partition. Same output:

DISKPART> select disk 0


Disk 0 is now the selected disk.


DISKPART> list part


Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 1000 MB 1024 KB
Partition 2 System 260 MB 1001 MB
Partition 3 Reserved 128 MB 1261 MB
Partition 4 Primary 217 GB 1389 MB
Partition 5 Recovery 350 MB 218 GB
Partition 6 Recovery 12 GB 218 GB
Partition 7 Primary 7167 MB 231 GB


DISKPART> select partition 1


Partition 1 is now the selected partition.


DISKPART> assign letter = R


DiskPart successfully assigned the drive letter or mount point.


DISKPART> exit


Leaving DiskPart...


C:\windows\system32>reagentc.exe /setreimage /path R:\Recovery\WindowsRE /target
C:\windows
REAGENTC.EXE: The Windows RE image cannot be stored in the specified volume. Use
the RETAIN command in DISKPART to prepare the volume and try again.

 

[arcturius]

When I try to access R:, I get:

C:\windows\system32>r:
The device is not ready.

 

[Saltgrass]

There appears to be something different about that partition. Use Diskpart and after selecting the partition, do a detail partition command and attach the results. Although it looks normal in all your attachments, there must be something different about it.

 

[arcturius]

Here it is:

DISKPART> select partition 1


Partition 1 is now the selected partition.


DISKPART> detail partition


Partition 1
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 1048576


Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 R RAW Partition 1000 MB Healthy Hidden

 

[theog]

@ Saltgrass

Looking at the screenshot of the Lenovo G580 the last partition is 20gb. genet Post 29.

That 7gb partition may be part of the Recovery partition.

Also arcturius Lenovo x240 may need the OEM 1000mb partition

 

[Saltgrass]

It looks like the partition is showing as RAW, which would mean to me the information is not in the Partition Table about its formatting.

What I would do is to boot to some third party partitioning software, like Partition Wizard and try to recover the partition. Since I only have experience with this utility, I will point out if you use it to recovery the partition, make sure and check all the partitions it finds, if they look normal. If you do not see an accurate representation of the partitions you expect, do not continue the process.

As you may know, do not use EaseUS.

I am assuming the drive is configured as GPT since your attachments seem to indicate that, but the best way to know is by using the list disk command in Diskpart it should show that on the right end of the listing was an asterisk.

 

[Saltgrass]

@ Saltgrass

Looking at the screenshot of the Lenovo G580 the last partition is 20gb. genet Post 29.

That 7gb partition may be part of the Recovery partition.

Also arcturius Lenovo x240 may need the OEM 1000mb partition

I think the unallocated space was because the drive had been reimaged, or recovered in the manner described. I have yet to see an install where the Factory Recovery Image partition was not the last one on the drive.

Since the Recovery Tools partition is showing as RAW, the drive configuration is still incorrect. I wonder if any of the other partitions are showing as RAW...

 

[arcturius]

This partition 1 was functional just 1 day ago. See post #34 by me. I was able to find e.g. winre.wim on it. Now it seems to be gone..

 

[arcturius]

partition 1, 5, 6 all raw now. those are the partitions we marked as recovery.

 

[arcturius]

In Disk Manager no local menus are available when I select recovery partitions. See screen shot.