WinRE Loop - /fixmbr - access denied

This what happens when I turn the PC on
Preparing automatic repair
Diagnosing your computer
Your PC did not start correctly
Press restart to restart your pc which can sometimes fix the problem. You can also press advanced options to try other options to repair your pc

If I hit restart the same thing happens as happens when I turn the machine on.

No the pc does not start windows 10

I have a Windows 10 DVD

I also have a windows 10 bootable usb

As an fyi - somewhere along the line my C: drive got relabeled to D: and my D: drive got relabeled F:

The o/s is installed on a 500gb ssd (was C, currently D)

My data is on a 1tb raid 1 sata set (was D, currently F)

I am using secure boot, so there is a FAT32 100mb EFI volume

There are 2 recovery volumes
1 is C which is 499mb
The other is E that is 533mb

I'll post the log files shortly

- - - Updated - - -

Here are the SRT logfiles

If I go into diskpart rename D to C & F to D when WinRE runs it relabels them back to D & F. Now maybe one of the 25 auto repairs went through the registry and changed everything to D but I certainly hope not. I do have a backup (robocopy) from 4/30

I watched the video. The concern I have is that the current state of the drive letters is incorrect. The pc has 2 drives (3 physical). Before the h/w problem: C: was where windows was installed & D: was my data drive. Right now D: is where windows is installed and F: is the data drive. I did a backup of the C drive on January 21 and a backup of the D drive on April 11. I have a log of both of those backups which will show the source of the files backed up.

I do not believe we will be able to boot successfully to windows 10 until the drives are labeled correctly.

If I go into diskpart, correct the drive letters & reboot something is putting the drive letters back to D & F.

Freebooter - haven't had a chance to watch your video yet. It's been a bad month for my computing environment. Something is up with my isp connection. I was out today and hope to get to them and my pc tomorrow.

I understand how from an o/s perspective I'm probably ok. It's everything else that's going to be a pia - shortcuts, excel macros, embedded links in word documents ... I know I'm getting ahead of myself.

I didn't use restore points. I'll let ya know how I make out

- - - Updated - - -

Freebooter, followed the instructions in your video - thank you skipping to the command prompt. Everything went according to plan until I rebooted. Hopefully I can attach a picture.

I didn't try safe mode if as windows indicates wof.sys is missing or corrupt I'm thinking its going to be missing or corrupt in safe mode as well, maybe not but its pretty clear the evaluation of windows has left this old man in the dust. I used to get annoyed when dfu's tried stuff so as much as I'm dyeing to play I won't, I'll be a good little dfu and wait. I do have a couple tricks up my sleeve from Server 2012 that might help but I'm not touching anything.

What pisses me off is that I am using robocopy to back the pc up. I looked at the last backup of the C: drive, no wof.sys, 1/2 the damn directory is missing.

Can you ease this old man's mind and tell me eventually we're going to get my volume letters back to C & D?

Freebooter, I'm a little confused. Do you want me to boot off of the Windows 10 set up media or do you want to me to boot to the screen above? If you want me to boot off of the windows set up media I need to disable EFI / enable legacy boot. If I boot to the screen above I will need to run diskpart & mount the windows 10 dvd - not a problem, just want to be sure I am on the correct environment

Well it looks like we may be going a bit backwards. From the screen above I press F1 and the PC reboots. When it comes back up I get the screen below, I press F1 the PC reboots & I get the screen above so stuck in yet another loop.

So I went in, disabled EFI & booted off the USB stick. Then did your BCD command - "The Boot configuration data store could not be opened" "The requested system device can not be found"

Attempted the SCF command - Windows Resource Protection could not start the repair service

In Server 2012 Microsoft released an in place upgrade. My team & I were very skeptical as historically Microsoft was a little lax while testing new "features". We wound up testing the thing & eventually upgrading a bunch of servers with it. So the trick I have up my sleeve is there such a thing in Windows 10 & can we use it to do a repair? Another option was in Windows 2003 you could boot off the CD and there was an option to "repair an existing installation of windows". Does that still exist? Both of those options preserved the existing environment.

- - - Updated - - -

Here's the 'screen below'

Consider the facts: You will not get it solved this year, next year and not in 10 years.
FreeBooter made your Recovery Environment inaccessible and nothing else.
Your system is ruined and you can run a clean installation today, tomorrow or in 10 years.
No other way. Mission Impossible