OK. The important WinRE.wim is there!
C:\Windows\System32\Recovery
So don't panic and don't worry. We fix that.
But right now I have to leave you and I will be back in appr. 2 hours

You don't have to look for anything. Just type in command prompt

dir /a /s c:\Windows\System32\winre.wim

and Windows finds it for you

This problem is only because you didn't run the format...

Command prompt is correct.

Will not solve your sfc-problem

The Recovery Partition is OK and healthy

Run cmd

reagentc /disable

wait 10 seconds

reagentc /enable

As Partition 1 is no longer a Recovery Partition give that partition other attributes

C:\Windows\system32>
diskpart
sel disk 0
sel par 1
set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
gpt...

Run
diskpart
sel disk 3
sel par 4
det par
exit

Post the output of det par

Problematic access permissions to certain directories are different from file attributes

Try to run the xcopy-command with the t-switch. It copies just the dir without any file
xcopy /? gives you...

Davidk

Don't worry! My above given commands are correct and are based on the info you provided:

409501

The IT number-counting starts at (0) ZERO and not (1) ONE!
Your C-Partition is...

That are good NEWS. You can mark this thread as solved now

Good! Since I run all my disks as GPT and some Servers with ZFS-Pools I didn't loose 1 KB!
The problem we had wouldn't have happend on a GPT. MBR allows just 4 primary partitions
Some diskpart...

Sorry, can't help. The problem description is confusing. Now the boot menue offers you WIN11, and a password is needed etc.
WIN 10 Recovery needs a password. WIN 11 not.

I don’t see the sense of all these instructions
When you are able to boot up to the „advanced options“ your BCD can’t be damaged!!

409477
You don’t have to search the BCD! In "Command Prompt"...

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...