Davidk

You mixed MBR and GPT disks! Only disk 3 is GPT.

Your Recovery is working from C:\Recovery and the SafeOS updates will work also.

To create a separate Recovery Environment run these...

markky99

You are free to believe what you want. And what you believe is only your truth!

But as I said before: Your Commands don't work! And that is very easy to prove also!

Your way shows:...

Good decision to leave it as Data-Disk. But that is a good reason to run it as a much safer GPT disk.
Run
diskpart
sel disk 1
clean
convert GPT
create partition primary
format quick fs=ntfs...

Your System changed from UEFI to BIOS. BIOS is a default setting and when the power is too low, it switches to default.

A high impedance Voltmeter doesn't detect the battery charging (capacity)!...

OK, that's correct. The /export command is valid only for the active system-bcd and not for a store-bcd.
Sorry for the confusion.
I see that you boot from (F:) but what happens if you doubleclick...

There are many possibilities:

1. to solve the problem with the right steps takes 10 minutes
2. to wait for the right answer can take a long time as you see
3. to unblock KB5034441 and try takes...

That was a misunderstanding: I mean the partition changes in post # 51.

I also checked your mentioning about the partition size of „System“ Partition. You are right, it was 350 MB some years ago...

Just one question. Is that stuff that is running on disk 0 (C:) the problem disk that gave you the boot failure and is running now?
I don't need reagentc any more.

The answer please! A good...

You must have used a 3rd party tool to do that


diskpart
list vol
sel vol #
ATTRIBUTES VOLUME CLEAR HIDDEN

select the vol from disk 1

Can you post a screenshot of "Diskmanagement" again please.
1T boot didn't have a driveletter before.


diskpart
sel disk 1
ATTRIBUTES DISK

diskpart
sel vol #

We don't need that skript any more!
Rightclick on the unallocated space and create a new volume. Assign any free letter and the problem is solved!
You just killed the culprit :mad:

Be patient! Don't run that skript now! There is time!
Run this first:

diskpart
sel disk 1
sel par 3
delete partition override
sel par 2
delete partition override
exit

OK, so you don't know how to copy a file to (C:). Doesn't matter!
Sometimes troubleshooting brings new ideas! When I look at your last Diskmanagement screenshot I have just one idea.
Use disk 0 as...

Yes, reboot and see what happens to the letter.

409362

same disk with 2 different drive letters!

And why don't you use cmd?

I changed the drive letter to k

diskpart
sel disk 1
sel par 3
det par

I use this script for years now and Microsoft doesn't use your instructions! :p

This is the original Microsoft Script to prepare the disk.
copy the file to C:\

409356

run cmd command
C:\Windows\System32>DiskPart /s C:\disk1.txt


after 5 seconds the disk is ready (C:)...

No, that's wrong
the first disk is disk 0
the first partition is always 1

According your screenshot
disk 1, partition 3 is the problematic one. Is that right?

You found
Partition 3
Type : 07
Hidden: No
if not means if you had found
Partition 3
Type : 27 for...

And why don’t you follow advices?

Diskmanagement like post #15 including the disk that has (F:) on it

cmd (admin)
reagentc /info

Did you download explorer++?

The problem is identified...

Everything is a real disaster.
- Your "Diskmanagement“ screenshot is not as it should be.
- If you know how to use Macrium the right way, s.th. like that doesn’t happen.
- The reason why you have...

The BCD_Cleanup was successful

"Diskmanagement" screenshot update was also needed!

3 long Commands to get the Recovery working

1.
bcdedit /store...

bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast

bcdedit /store...

You must have a 2nd EFI!

step by step and watch the system response after each input. Don't continue if s.th. was not successful

bcdedit /store...

To finalize the BCD-Clearance in addition to #20 run cmd:

bcdedit /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
bcdedit /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}

bcdedit /set {fwbootmgr}...