Windows 10 Need to migrate MBR Win10Pro C drive HDD contents or my Macrium Reflect backups of it to new on-the-motherboard NVMe SSD device set to UEFI GPT

@ChatGPT

in Hiren's, under your step A, item 2, upon invoking bcdboot E:Windows /s C: /f UEFI, I get:

BFSVC Error: Could not open the BCD template store. Status = [c000000f]

Good catch — that c000000f from bcdboot means it couldn’t open/create the BCD store on the target ESP. Often the cause is either a syntax/drive‑letter mixup, the ESP not actually writable/usable, or the Windows folder not where you think it is. Let’s check the basics and retry with the safe sequence below. Copy/paste each command and tell me the full output if anything fails.
Important: confirm you have a current Macrium image of the NVMe before we write anything. Yes/no?
1) Reconfirm volumes and which drive is which
(so we don’t touch the 12TB drive)
diskpart
list disk
list vol
exit
Confirm (from the list vol) which volume letter is the Windows install (should show a Windows folder) and which is the FAT32 ESP.
2) Verify the Windows folder actually exists on the Windows volume
Replace E: below with whatever letter list vol showed for the Windows partition.
dir E:\Windows
If you get “File Not Found” or no Windows folder, tell me the exact listing — we need the correct Windows volume letter.
3) If the Windows folder is correct, assign a safe letter to the ESP and make sure it’s writable

• Replace <VOL#> below with the volume number of the FAT32 ESP reported by list vol (it was volume 2 previously).
  diskpart
  select vol <VOL#>
  assign letter=S
  exit

Now check S: contents to ensure it isn’t empty (should be mostly empty or contain an EFI directory if anything):
dir S:\
4) Clear read‑only and format only if necessary
If dir S:\ returns permission/access or bcdboot errors again, clear readonly and (only if needed) reformat the ESP to FAT32:
diskpart
select disk 0 <-- make sure this is the NVMe (confirm with list disk earlier)
attributes disk clear readonly
select vol <VOL#>
format fs=fat32 quick label=ESP
assign letter=S
exit
(Formatting will wipe any existing EFI data on that partition; only do this if bcdboot keeps failing and you have a backup of the image — confirm before formatting.
5) Run bcdboot against the Windows folder and put files on the ESP
Use the Windows volume letter you verified in step 2 and the ESP letter S you just assigned:
bcdboot E:\Windows /s S: /f UEFI
Expected success message: “Boot files successfully created.”
6) Firmware settings & test boot

• Reboot into UEFI settings (Del/F2).
• Set Boot Mode = UEFI (CSM = Disabled).
• Ensure “Windows Boot Manager (Samsung …)” is first.
• Secure Boot = Disabled for first test.
• Save and try to boot.

If bcdboot still returns the same c000000f error

• Paste the exact full output of:
  • the diskpart list vol output you ran in step 1
  • the dir E:\Windows output from step 2
  • the exact bcdboot command and full error text

If bcdboot succeeds but Windows still bluescreens INACCESSIBLE_BOOT_DEVICE

• We’ll load the offline SYSTEM hive and enable storage drivers (I can give the exact reg commands). That’s the usual fix for driver mismatch (NVMe driver/StorAHCI/etc.. Tell me if you want to proceed with that.

If you’d rather try the quick fallback to get desktop now

• We can enable CSM/Legacy and run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  which often gets an MBR image booting quickly, then convert later.

Which do you want to try now — (A) bcdboot to assigned S: (I’ll wait while you run the commands above and paste outputs), (B) proceed to enable storage drivers in the offline SYSTEM hive, or (C) try the Legacy/bootrec quick route?

@ChatGPT

Okay, got to step 3, and assigned the relevant partition to S, and a dir of S:\ shows:

10.12.2025 08:05 am <DIR> EFI
0 file(s) 0 bytes
1 DIR(s) 234,605,504 bytes free

Perfect — seeing the EFI folder on S: is good. Next we’ll (A) confirm the Windows folder exists, (B) inspect the existing EFI boot files and move the old BCD out of the way if present, then (C) run bcdboot to create a fresh UEFI boot store.
Please copy/paste these commands (one block at a time) into Hiren’s Command Prompt and paste back the outputs.
1) Confirm Windows folder is where we think it is (replace E: if your Windows volume letter is different)
dir E:\Windows
2) Confirm the EFI folder contents and whether a BCD file already exists
dir S:\
dir S:\EFI
dir S:\EFI\Microsoft\Boot
If the last command shows a BCD file (or files) in S:\EFI\Microsoft\Boot, we’ll rename the existing BCD before attempting to write a new one.
3) If a BCD exists, rename it (safe, non‑destructive)
ren S:\EFI\Microsoft\Boot\BCD BCD.old
(If the file is locked or you get an error, paste the error text.
4) Make sure the ESP is writable and disk not read‑only
diskpart
select disk 0
attributes disk clear readonly
exit
5) Now create the UEFI boot files (this is the bcdboot step)
bcdboot E:\Windows /s S: /f UEFI
Paste the full output of that command here.
What to expect next

• If bcdboot reports “Boot files successfully created” — reboot to firmware, set Boot Mode = UEFI (CSM disabled), make “Windows Boot Manager (Samsung …)” first, Secure Boot OFF for the first try. Boot to Windows and report back.
• If bcdboot again returns an error (c000000f or access denied), paste the exact full error and the dir outputs you produced above. I’ll interpret them and give the next action (usually unloading/loading the SYSTEM hive and fixing Start values for storage drivers, or using gdisk if the partition table must be converted).

If you prefer to skip straight to the more aggressive driver-fix path (offline SYSTEM hive edits) I can guide that next — but let’s try the bcdboot/rename approach first since it’s simplest and least invasive.

@ChatGPT

okay, at step 5, got "Boot files successfully created."

It is still giving error 0xc0000001 at boot.

Thanks — good progress (bcdboot succeeded). The 0xC0000001 / INACCESSIBLE_BOOT_DEVICE now strongly points to Windows not loading the storage driver it needs at boot. The next safe step is to enable common storage/NVMe drivers in the offline SYSTEM hive so Windows will load them at boot. This is non‑destructive and commonly fixes this BSOD after restores to different hardware.
Before you run anything — one last safety check

• Do you have a fresh Macrium image of the NVMe (the Windows disk) on your 12 TB files drive? (yes / no)
  If not, please make that image now if you can. The steps below are standard and safe, but it’s always best to have a recent image.

Run these commands in the WinPE / Hiren’s command prompt (copy/paste exactly). I’ll wait for the outputs you produce at the marked steps.
1) Mount the offline SYSTEM hive and find the current ControlSet
(reg commands assume Windows is on E: — change letter if your Windows partition letter is different)
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current

• Paste the full output of the reg query here. It will show a number (usually 1 or 2). Suppose it shows 1 — the path we will edit becomes HKLM\TEMP_SYSTEM\ControlSet001...

2) Add Start=0 for the common storage drivers
(Replace 00X below with the ControlSet number from step 1, for example use ControlSet001 if Current = 1)
reg add "HKLM\TEMP_SYSTEM\ControlSet00X\Services\storport" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet00X\Services\storahci" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet00X\Services\msahci" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet00X\Services\iaStorV" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet00X\Services\nvme" /v Start /t REG_DWORD /d 0 /f

• Run each line. If any returns an error about a missing key, paste that error but continue with the rest — missing keys are OK.

3) Unload the hive
reg unload HKLM\TEMP_SYSTEM
4) Ensure the ESP is still assigned and boot files are present (repeat just in case)
diskpart
list vol
select vol 2 (or the volume number of your ESP shown by list vol)
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI

• Paste the bcdboot output.

5) Reboot and test

• Reboot, go into BIOS and set Boot Mode = UEFI (CSM disabled), make Windows Boot Manager (Samsung) first, Secure Boot OFF for the first boot. Try to boot.

If it still BSODs

• Paste the exact error messages you see during the attempted boot (if you see the same CODE, and/or any stop text).
• If it still fails we will:
  a) verify the driver keys actually exist under the ControlSet you edited (I can give reg query commands), and/or
  b) run gdisk to write GPT headers (if firmware seems strict about partition table) and re-run bcdboot, or
  c) fall back to the quick rescue: enable CSM/Legacy and run bootrec to temporarily boot MBR while we debug.

If you want the fastest path back to desktop right now

• Say “Fallback to Legacy” and I’ll give the exact bootrec steps (enable CSM/Legacy in BIOS, run the bootrec commands). That usually gets a restored MBR image booting quickly; we can convert to UEFI later.

Tell me:
1) Did you make that Macrium image (yes/no)?
2) Paste the output of step 1’s reg query (or if you already ran it, paste the Current value).
I’ll interpret it and then tell you the next exact reg add commands with the correct ControlSet path, and wait for the outputs.

@ChatGPT

okay, the output of req query HKLM\TEMP_SYSTEM\Select /v Current is:

HKEY_LOCAL_MACHINE\EMP_SYSTEM\Select
Current REG_DWORD 0x1

Thanks — Current = 1, so the ControlSet to edit is ControlSet001. Good.
Before we run the registry edits: do you have a fresh Macrium image of the NVMe right now? (yes / no)
If no, stop and make the image first. The registry edits below are standard and low‑risk, but please make the image if you can.
When ready, run these exact commands in your WinPE / Hiren’s command prompt (copy/paste line by line). I’ll wait for the outputs you paste back if anything errors.
1) (Load the SYSTEM hive — you already did this, but safe to re-run)
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
2) (Optional: confirm Current again)
reg query HKLM\TEMP_SYSTEM\Select /v Current
3) Add the storage drivers with Start=0 (use ControlSet001 because Current = 1)
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\storport" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\storahci" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\msahci" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\iaStorV" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
Notes:

• If any command returns “The system cannot find the specified registry key” that just means that driver key isn’t present in the image — that’s fine, continue with the rest.
• If any command returns an unexpected error, paste the full error text here.

4) Unload the hive
reg unload HKLM\TEMP_SYSTEM
5) Recreate the UEFI boot files (ensure ESP letter is S
diskpart
list vol
select vol 2 (or the volume number of your ESP shown by list vol)
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
Paste the full bcdboot output here.
6) Reboot and test

• Reboot into BIOS/UEFI: set Boot Mode = UEFI (CSM disabled), set “Windows Boot Manager (Samsung …)” first, Secure Boot = Disabled for the first test.
• Try to boot.

If you still get 0xC0000001 / INACCESSIBLE_BOOT_DEVICE after this:
A) Paste the bcdboot output + any BSOD stop text you see.
B) We’ll then:

• Verify the registry changes actually applied (I’ll give reg query commands),
• If necessary run gdisk to write GPT headers (non‑destructive) and recreate the ESP + bcdboot, or
• If you need immediate desktop now, fallback to Legacy/CSM and run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  (then boot Windows in Legacy; convert to UEFI later)

Which do you want to try now — run the registry edits (A), or go straight to the Legacy bootrec fallback (B) for a fast temporary desktop?

@ChatGPT

Did everything up through step 6

still saying inaccessible boot device, error 0xc0000001

Thanks — you got this far and did the right things (created an ESP, ran bcdboot, and tried the offline SYSTEM edits). bcdboot succeeded earlier, so the boot files exist now; the remaining problem is Windows failing to load the storage/NVMe driver at boot (INACCESSIBLE_BOOT_DEVICE 0xC0000001).
I’ll keep this short and practical: two parallel paths you can take now. First I’ll give a short set of diagnostic commands to run in Hiren’s WinPE so we know exactly what’s missing; then the two options (A = try to fix the offline image so it will boot in UEFI, B = fallback to Legacy/quick desktop). Tell me which you want to do (I recommend A if you have time; B if you must be back on desktop immediately).
Step 0 — one last safety question

• Do you have a fresh Macrium image of the NVMe (the Windows disk) on the 12 TB files drive? (yes / no)
  If “no”, stop now and make that image. Don’t proceed until you have it.

Diagnostics to run now (copy/paste these exact commands in Hiren’s CMD; paste the outputs back here)
1) Re‑mount the SYSTEM hive and confirm Current (you already did this but run again so I can read exact output):
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
2) List storage‑related service keys and their Start values (this shows whether drivers are enabled to load at boot):
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\storport /v Start
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\storahci /v Start
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\msahci /v Start
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\iaStorV /v Start
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme /v Start
reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme /v Start
(If any key doesn’t exist you’ll get an error — that’s OK; paste the output anyway.
3) Check which storage driver files actually exist in the offline OS:
dir E:\Windows\System32\drivers*nvme 2>nul
dir E:\Windows\System32\drivers\stor.sys 2>nul
dir E:\Windows\System32\drivers\iaStor* 2>nul
4) List installed drivers in the offline image (this shows drivers Windows knows about):
dism /image:E:\ /Get-Drivers
5) Unload the hive when you’re done:
reg unload HKLM\TEMP_SYSTEM
Why these matter

• If the Start values for the NVMe / stor drivers are 0 (SERVICE_BOOT_START) they’ll be loaded at boot. If they’re not 0 (e.g. 3 = demand), Windows won’t load them early and you get INACCESSIBLE_BOOT_DEVICE. The registry edits we did earlier were intended to set Start=0; these checks confirm whether they actually applied and whether the corresponding driver files exist in E:\Windows\System32\drivers. (This is the same approach I suggested earlier when bcdboot completed but the system still BSOD’d.

What to do next depending on the diagnostic results
A — If driver keys exist but Start ≠ 0 OR driver files are missing

• If Start values are not 0, run the reg add commands I gave earlier to set Start=0 for the present keys (storport, storahci, msahci, iaStorV, nvme, stornvme). Example (after reg load):
  reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
• If driver files are missing (DISM or dir shows no NVMe driver), download the OEM NVMe driver (Samsung NVMe driver for the 980 PRO is common) on another machine and copy the driver folder to a USB. Then from WinPE inject it into the offline image:
  dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  (Adjust X: path; use the folder that contains the .inf). Then re-run:
  bcdboot E:\Windows /s S: /f UEFI
  Reboot to UEFI (CSM disabled) and test.

B — If driver keys look correct and drivers exist but it still BSODs

• Convert the disk to GPT (gdisk) and ensure the ESP is correct, then bcdboot again. Use gdisk to write GPT non‑destructively and create the ESP if needed, then bcdboot — I outlined this earlier and can walk you through it step‑by‑step.

C — Quick fallback to get you back on desktop now (fast)

• If you need the old system back immediately and don’t care about UEFI, switch BIOS to enable CSM/Legacy, boot the Windows Repair CD (legacy mode) and run these commands from the recovery Command Prompt:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  (or bcdboot E:\Windows)
  That usually gets an MBR image booting quickly. We can convert to UEFI cleanly later. (This was the “get back to desktop fast” option I suggested earlier.

Which path do you want to take now?

• If you want me to continue trying to fix the UEFI boot (recommended), run the diagnostic commands (1–4 above) and paste all outputs here. I’ll interpret them and give the exact registry edits or driver‑injection command you need.
• If you want the quick desktop fallback, say “Fallback to Legacy” and I’ll give the exact bootrec steps and BIOS notes and stay with you while you run them.

I’ll wait for your choice and/or the diagnostic outputs.

@ChatGPT

reg query HKLM\TEMP_SYSTEM\Select /v Current
yields:

HKEY_LOCAL_MACHINE\TEMP_SYSTEM\Select
Current REG_DWORD 0x1

the rest of them yield 0x0 at the end

all the 2>nul stuff are showing some variation on:

Volime in drive E is Windows C
Volume Serial Number is E346-1425

Directory of E:\Windows\System32\drivers

...except forthe last one which also includes:

12/07/2019 05:07 AM 884,752 iaStorAVC.sys
12/07/2019 05:07 AM 412,176 isStorV.sys
2 file(s) 1,296,928 bytes
0 Dir(s) 321,779,830,784 bytes free

when invoke dism /image:E:\ /Get-Drivers, I get:

Deploypent Image Servicing and Managemet tool
Version 10.0.19041.3636

Obtaining list of 3rd part drivers from driver story...

Error: 32

An error occurred. The driver store for the image could not be opened,
The DISM log file can be found at X:\Windows\Logs\DISM\dism.log

At this juncture, I'm very close to the point where I need to give up for the day and revert back to the other backup.

You’ve done a lot of the right work — thanks for sticking with it and for the detailed outputs. Short summary of where we are, then two clear choices (revert to backup now, or try one more targeted repair). Tell me which you want and I’ll walk you through it step‑by‑step.
Short summary (what your outputs show)

• Disk/volumes: Samsung NVMe is the small disk (the one you want to boot). You successfully created an ESP (FAT32) and bcdboot reported “Boot files successfully created.”
• The BCD and ESP are present, so UEFI boot files exist.
• The boot failure now is INACCESSIBLE_BOOT_DEVICE (0xC0000001) — that usually means Windows can’t load the storage/NVMe driver early enough at boot.
• You checked the offline SYSTEM hive: Current = 1 and the storage-service Start values you inspected show 0x0 (i.e. Start = 0) — that means the registry flags we wanted are present. The IAStor files are present in the driver folder. DISM gave Error 32 when trying to read the offline driver store (Windows PE / Hiren’s limitation or a file lock), so we couldn’t easily enumerate/inject drivers from there.

You’re understandably fed up. Two practical options now.
Option 1 — QUICK: revert to the other backup / get back to desktop fast (recommended if you must be working immediately)
What it does: restore the other image that you know boots, get you into Windows quickly (in Legacy/CSM if needed). We can do a UEFI conversion properly later.
Steps (copy/paste from a WinPE / Macrium Rescue environment):
1) Confirm disks (VERY important; don’t touch the 12 TB):
diskpart
list disk
exit
2) Restore the alternate Macrium image:

• In Macrium Rescue → Restore → select the other backup image on your files drive → Choose the Samsung as target → restore partitions (overwrite existing) → Apply.
  3) If that image was legacy/MBR and your BIOS is set UEFI: either
• Enable CSM/Legacy in BIOS and boot the machine normally, or
• After restore use Windows Repair CD (boot in Legacy) → Troubleshoot → Advanced → Command Prompt and run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  (If /fixboot says “Access is denied” run: bcdboot E:\Windows — replace E: if a different letter in WinPE.
  4) Reboot and test. If it boots, make a new Macrium image immediately (so you have a known working fallback).
  If you choose Option 1 now, say “Fallback — restore other image” and I’ll guide you through any dialog or repair commands you hit.

Option 2 — LAST ATTEMPT: try to get this restored January image to boot in UEFI by injecting the correct NVMe driver (or verify driver presence), then boot
What it does: tries to fix the actual cause (missing/incorrect early NVMe driver). This can work but requires either the correct OEM NVMe driver package (Samsung NVMe driver for 980 PRO is typical) or using gdisk to force GPT if the firmware is refusing to use the ESP (you already have ESP + bcdboot so driver is the likely cause).
Steps (I’ll help you do exactly one of these):
A — Try to inject Samsung NVMe driver into the offline image
You’ll need the Samsung NVMe driver package (folder with .inf/.sys). If you can download it now on another PC and copy to a USB, do that. Then, from WinPE (Hiren’s) command prompt:
1) Mount image & confirm letters:
diskpart
list vol
exit
(Confirm Windows is E: and target ESP is S: as you had)
2) Load the SYSTEM hive (we already did this previously but OK to run):
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
(reg unload later)
3) Inject drivers (example — replace X:\Drivers with the USB path):
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
(If dism errors, capture the dism.log at X:\Windows\Logs\DISM\dism.log and paste the relevant errors.
4) Ensure Start values are 0 (we did this already, but re-run reg add for nvme/storport if you want):
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
reg unload HKLM\TEMP_SYSTEM
5) Re-run bcdboot (assign S: if needed):
bcdboot E:\Windows /s S: /f UEFI
6) Reboot to UEFI (CSM disabled) and test.
If you want to try Option 2A I will wait while you get the driver package and paste the results of the DISM command; I’ll interpret errors.
B — If driver injection is not possible or fails: write GPT with gdisk and recheck
(You already created ESP so this is less likely to help, but sometimes firmware is picky.
1) Put gdisk.exe on a USB
2) In WinPE:
gdisk .\physicaldrive0
type p (inspect) then w to write GPT
3) Create/assign ESP if missing and rerun bcdboot
4) Reboot to UEFI
I can guide step‑by‑step and interpret output.
My recommendation

• If you need to work today: Option 1 (restore the other backup and get back to desktop). We can come back to the UEFI conversion / driver injection tomorrow.
• If you want one last try on this January image: Option 2A (inject Samsung NVMe driver into the offline image). It’s the most likely “last chance” cure without restoring.

Tell me which you want to do now:

• “Fallback — restore other image” (I’ll walk you through Macrium + bootrec if needed), or
• “Try driver injection” (I’ll wait while you get the Samsung NVMe driver on a USB and then I’ll give the exact DISM command and interpret results), or
• “Try gdisk” (I’ll guide you through writing GPT non‑destructively).

Also confirm: do you have a current Macrium image of the NVMe right now? (yes / no) — if not, I still strongly recommend making that image before any more write operations.

@ChatGPT

I am going to revert to the other, more recent, backed up image, which also means the machine needs to boot to it the way it was before we started trying to get the older image up and running.

OK — understood. Good call to revert to the more‑recent image so you can get back to work. Below I’ll give a safe, step‑by‑step restore + boot checklist you can follow now (Macrium Rescue + firmware + quick repairs). I’ll include the exact commands to run if the restored image does not boot, and how to choose Legacy vs UEFI repair depending on the restored image type.
Before you start — absolute musts

• Make sure the 12.73 TB files drive (your backup repository) stays connected — but double‑check you do NOT select it as the restore target.
• Confirm you have a good Macrium image labeled “the recent image” on the 12 TB drive.
• If you have time, create a fresh Macrium image of the current NVMe state (optional but safest). If you don’t have time, proceed — we’re restoring a known good image anyway.

Restore the “other” image (Macrium Rescue — UEFI boot)
1) Boot Macrium Reflect Rescue media (UEFI boot entry). Use the one you used previously.
2) In Reflect → Restore:

• Browse to the recent image on the 12 TB files drive.
• Select the image and click Restore Image.
• For Target Disk choose the Samsung NVMe (confirm by model and ~1863 GB size). VERY IMPORTANT: confirm the disk number / model in the target area — do NOT pick the 12 TB drive.
• If the image covers the whole disk, simply map the image partitions to the target. If you must change sizes, leave defaults.
• Apply / run the restore. Wait for completion.
  3) After Restore finishes, do NOT reboot yet. We’ll ensure the firmware/boot mode matches the image.

Decide firmware boot mode for the restored image

• We need to know whether the restored image is Legacy/MBR or UEFI/GPT. To check quickly from Rescue before rebooting, open Command Prompt and run:
  diskpart
  list disk
  exit
  Look at the GPT column: if the restored disk shows an asterisk (*) under GPT it’s GPT/UEFI; if not it’s MBR/Legacy.

If the restored image is MBR/Legacy (most likely if the shop previously installed Legacy)
A — Set BIOS to allow Legacy/CSM:

• Reboot into BIOS; set:
  • Storage = AHCI (leave this)
  • Launch CSM = Enabled (allow Legacy)
  • Secure Boot = Disabled
• Save & exit.

B — Repair MBR/BCD (if necessary)
If the machine does not boot naturally into the restored Windows, boot the Windows Repair CD (legacy/CSM entry) and choose Troubleshoot → Advanced → Command Prompt and run these commands (copy/paste):
diskpart
list disk
exit
Then:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If you get “Access denied” on /fixboot, then run:
bcdboot C:\Windows
(Use the Windows drive letter as shown by list vol in WinRE if it differs.
If the restored image is GPT/UEFI
A — Set BIOS to pure UEFI:

• Reboot into BIOS; set:
  • Launch CSM = Disabled
  • Secure Boot = Disabled (first boot)
  • Storage = AHCI
• Save & exit.

B — If it fails to boot, rebuild the UEFI boot files:
Boot Windows Repair USB (UEFI entry) → Repair → Command Prompt, then:
diskpart
list vol ← find the small FAT32 ESP (usually ~100–260 MB) and the Windows volume
select vol <ESP#>
assign letter=S
exit
bcdboot C:\Windows /s S: /f UEFI
(Replace C: with the Windows volume letter if WinRE shows something else.
If bcdboot says BCD template error or cannot create store

• Ensure the ESP is FAT32, writable and not read‑only:
  diskpart
  select disk <NVMe disk#>
  attributes disk clear readonly
  select vol <ESP#>
  format fs=fat32 quick label=ESP
  assign letter=S
  exit
• Rerun bcdboot.

If you’re unsure whether the image is MBR or GPT, tell me the output of:
diskpart → list disk
(or paste it here) and I’ll give the exact repair commands.
If boot still fails with INACCESSIBLE_BOOT_DEVICE (0xC0000001)
That indicates Windows can’t load the storage driver at boot. Quick options:

• Enable Legacy boot and use bootrec as above to get back to desktop quickly (fastest). Then we can troubleshoot UEFI conversion later.
• Or, try the driver fix path: from WinPE load the offline SYSTEM hive and set stor/NVMe drivers to Start=0 and/or inject the Samsung NVMe driver into the offline image using DISM, then run bcdboot and test. I can walk you through that if you want one more attempt.

After you get back to Windows

• Make a fresh Macrium image of the working state (so you have a usable fallback).
• If you want the long‑term UEFI/GPT setup for NVMe, we can schedule the safe conversion (mbr2gpt or gdisk) later once you’re back on a working desktop.

Do you want me to:
A) Walk you through restoring the image now step‑by‑step (I’ll wait while you do each action), or
B) Give the exact one‑shot commands to run after you restore (depending on whether your restored disk is MBR or GPT)?
If B, please paste the output of diskpart → list disk right after the restore so I can choose the right repair commands.

Grrr... forgot to address @ChatGPT on this: I am reverting to the known-good boot image, and I need to have that working like before.

@ChatGPT

Pretty sure the image I'm reverting to is gpt boot.

Understood — you want the known‑good image restored and to get the machine back to the desktop as it was (GPT/UEFI). Below is a compact, safe, step‑by‑step checklist you can follow now. I’ll give exact commands to run in WinPE / Macrium Rescue and what to do in BIOS. If anything fails, paste the full command output and I’ll tell you the next command.
Important safety reminders before you start

• Confirm the image you’re restoring is the “known‑good” image and is on your 12 TB files drive.
• Double‑check disk numbers before any diskpart/disk commands — Disk 0 = Samsung NVMe (~1.86 TB), Disk 1 = your 12 TB files drive. Do NOT select Disk 1.
• If you have time, make one quick Macrium image of the current NVMe state to the 12 TB drive (optional but safest).

Step 1 — Restore the known‑good image (Macrium Rescue)

1. Boot Macrium Rescue (UEFI entry).
2. In Reflect → Restore:
   • Select the known‑good image on the 12 TB drive.
   • Set the target disk to the Samsung NVMe (confirm model/size).
   • Restore the image (restore the partitions as provided in the image). Use default sizes (do not intentionally shrink).
   • Apply and wait for completion.
3. When restore finishes, do NOT reboot yet. Proceed to Step 2 for verification and repair.

Step 2 — Verify partition table & ESP, then recreate UEFI boot files
Boot the Rescue environment’s Command Prompt (or Windows install USB → Repair → Command Prompt) and run these commands — paste outputs if anything looks different:
A — Confirm disks & volumes
diskpart
list disk
list vol
exit
Check that:

• The Samsung NVMe is the ~1.86 TB disk (note its disk number).
• There is a small FAT32 partition (ESP). Note its Volume number and the Windows partition letter (in WinPE the Windows partition often shows as E: or similar).

B — If an ESP exists: assign letter S and create UEFI boot files
(Adjust the Windows drive letter if list vol shows something other than E: for the Windows partition; replace <ESPvol#> with the number you saw.
diskpart
select vol <ESPvol#>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
Expected: “Boot files successfully created.” If so, go to Step 3.
C — If bcdboot errors (access denied or c000000f)
Run:
diskpart
select disk <nvmedisk#>
attributes disk clear readonly
select vol <ESPvol#>
format fs=fat32 quick label=ESP
assign letter=S
exit
Then rerun:
bcdboot E:\Windows /s S: /f UEFI
Step 3 — Set firmware & first boot

• Reboot into UEFI/BIOS (Del or F2).
• Set:
  • Storage = AHCI
  • Launch CSM = Disabled (pure UEFI)
  • Secure Boot = Disabled for the first boot
• In Boot Option Priorities place “Windows Boot Manager (Samsung SSD 980 PRO …)” first (or use one‑time boot to pick it).
• Save and reboot.

If Windows boots — great. After a stable boot you can re‑enable Secure Boot if desired.
If you still get a BSOD INACCESSIBLE_BOOT_DEVICE (0xC0000001) after bcdboot succeeded
This means Windows is missing the driver it needs at early boot (NVMe/AHCI driver mismatch). Two quick options:
Option Quick (get desktop now)

• Temporarily enable CSM/Legacy in BIOS, boot the Windows Repair CD (legacy entry) and run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  (or run bcdboot C:\Windows)
• This usually gets an MBR/legacy image booting fast. You can convert to UEFI later.

Option Proper (fix drivers / keep UEFI)

• We must ensure Windows has the NVMe driver available at boot:
  1) Download the Samsung NVMe driver package (980 PRO) on another PC and copy to USB.
  2) In WinPE:
  • reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
  • reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
    (repeat for storport, storahci, msahci, iaStorV if present)
  • reg unload HKLM\TEMP_SYSTEM
  • dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • bcdboot E:\Windows /s S: /f UEFI
    3) Reboot to UEFI and test.

If mbr2gpt is needed (only if you must convert MBR→GPT) or gdisk

• If you later want to convert to GPT non‑destructively, use mbr2gpt from Windows install USB or gdisk in WinPE; I can walk you through this when you are back on desktop.

What I recommend you do right now

• Since you said you’re reverting to the known‑good GPT image, follow Steps 1 → 2 → 3 above in order.
• If any command prints an error (especially for bcdboot or diskpart), copy the full output and paste it here.
• If boot still fails with 0xC0000001 after these steps, tell me whether you prefer:
  • Quick fallback (Legacy/bootrec) so you get back to work immediately, or
  • Try the driver injection path so the image boots in UEFI properly (takes longer but cleaner).

I’ll stay with you. Tell me:
1) You’re ready and have the Macrium image selected (yes), and
2) Will you run the exact commands above and paste outputs for any errors, or do you want me to give the quick Legacy command sequence first?

Okay — let’s get you back to the known‑good image and booting the way it was. Below is a short, safe checklist you can follow right now (exact commands to paste), plus troubleshooting branches depending on whether the restored image is Legacy/MBR or UEFI/GPT. I’ll stay with you step‑by‑step if you want.
Important safety first

• If you can, make one quick fresh Macrium image of the NVMe right now to the 12TB files drive (so you have a snapshot of the state we’ve been working on). Don’t proceed without a backup if you can.
• Double‑check disk numbers before any diskpart/select commands — your 12TB files drive is important and must not be selected.

Step 1 — Restore the known‑good image with Macrium Reflect Rescue
1) Boot the Macrium Rescue USB/DVD (use the Rescue environment you used earlier).
2) In Reflect → Restore:

• Browse to the recent known‑good image on the 12TB files drive.
• Select that image and choose Restore Image.
• Target: select the Samsung NVMe (confirm model & ~1863 GB size) — do NOT select the 12TB drive.
• Restore the partitions from that image to the NVMe (overwrite the existing partitions). Apply the restore and wait for it to finish.
  (If you’d prefer the GUI steps listed earlier, see the restore outline in the guidance.

After the restore finishes, DO NOT immediately panic if it doesn’t boot — follow Step 2 below.
Step 2 — Confirm whether the restored disk is MBR (legacy) or GPT (UEFI)
Boot the Rescue environment (or stay in Macrium Rescue) and open Command Prompt, then run:
diskpart
list disk
exit

• Look at the GPT column for the NVMe disk:
  • If GPT column has a * → disk is GPT (UEFI). Proceed to 3A.
  • If GPT column is blank → disk is MBR (Legacy). Proceed to 3B.
    (You must confirm this before running boot repair commands.

3A — If the restored image is GPT (UEFI): rebuild UEFI boot
(Exact commands to run in Rescue Command Prompt — replace drive letters as shown by list vol.
diskpart
list vol ← note the small FAT32 EFI volume number and the Windows partition letter
select vol <EFI#>
assign letter=S ← only if it has no letter
exit
bcdboot C:\Windows /s S: /f UEFI

• Expect: “Boot files successfully created.” Then reboot to firmware:
  • Set Boot Mode = UEFI (CSM disabled), Secure Boot OFF for the first attempt.
  • Put “Windows Boot Manager (Samsung …)” first in the boot order and try to boot.

If bcdboot fails with template / c000000f, reformat/repair the ESP and retry (only if you confirmed the ESP is the correct partition):
diskpart
select disk <NVMe disk#>
attributes disk clear readonly
select vol <EFI#>
format fs=fat32 quick label=ESP
assign letter=S
exit
bcdboot C:\Windows /s S: /f UEFI
(If you get repeated errors, tell me the exact bcdboot output and dir S:\ contents.
3B — If the restored image is MBR (Legacy): restore legacy boot quickly
Quick route (fastest) — enable Legacy/CSM and run bootrec:
1) Reboot into BIOS and set:

• Launch CSM = Enabled (allow Legacy/CSM)
• Storage = AHCI
• Secure Boot = Disabled
  2) Boot the Windows Repair CD (choose the non‑UEFI / legacy boot entry) → Troubleshoot → Advanced → Command Prompt
  Run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd

If bootrec /fixboot reports “Access is denied”, run:
bcdboot C:\Windows

• Reboot — you should return to your previously working Legacy boot. This is the fastest way to get you back to desktop, and you can convert to UEFI later if desired.

If you still get INACCESSIBLE_BOOT_DEVICE (0xC0000001) after the above
That error usually means Windows can’t load the storage driver at boot (driver mismatch for the new controller). Two options:
A) Quick fallback: leave BIOS set to Legacy/CSM and use bootrec / bcdboot as above until you’re back on desktop (recommended if you must work immediately).
B) Try to fix drivers in the offline image (one more, targeted attempt): inject the correct NVMe driver (Samsung NVMe driver for 980 PRO) into the offline Windows image and ensure the start value for storage drivers is set to load at boot (reg load + reg add). This is a bit more work but can fix INACCESSIBLE_BOOT_DEVICE. See guidance here for the exact reg and DISM commands.
If you want that driver injection path now I will walk you step‑by‑step (you’ll need the OEM NVMe driver package on a USB so we can run dism /Image:E:\ /Add‑Driver /Driver:X:\ …).
Final checklist (quick)

• Restore known‑good image with Macrium Rescue (target = Samsung NVMe).
• Check disk type (diskpart → list disk) → pick UEFI or Legacy branch.
• UEFI branch: assign ESP letter + bcdboot C:\Windows /s S: /f UEFI → BIOS: UEFI/CSM disabled.
• Legacy branch: enable CSM → Windows Repair CD → bootrec /fixmbr /fixboot /rebuildbcd (or bcdboot).

Do you want me to:

• A — walk you through the restore now (I’ll wait for the Macrium Rescue screens / outputs), or
• B — give only the repair commands after you finish the restore and paste the diskpart list disk output?

Say A or B and I’ll stay with you step‑by‑step.

@ChatGPT

Okay, I did approach 3B on that last, and after bootrec /rebuildbcd it gave:

Successfully scanned Windows installations.
Total identified Windows installations: 1
[1] G:Windows
Add installation to boot list? Yes(Y)/No(N)/All(A):

I entered Y, and it said:

The requested system device cannot be found.

What next?

That “The requested system device cannot be found” after answering Y means the Recovery environment found a Windows install but couldn’t add it into the BCD store — usually because the recovery environment is looking at the wrong disk/letters, the EFI/BCD area is inaccessible or corrupt, or the boot files/drivers it needs aren’t available. Don’t panic — try the checklist below, in order. I’ll give exact commands to run from WinRE / your rescue WinPE (what you used before). Each step explains why and what to paste back if it fails.
Quick plan (order)
1) Confirm the recovery environment is seeing the correct Windows + EFI volumes.
2) Recreate the UEFI boot store with bcdboot (the most reliable fix for a UEFI/GPT system).
3) If bcdboot fails, make the ESP writable / rename the old BCD and retry.
4) If it still fails, check for driver / storage‑access issues (rare after bcdboot succeeds) or fall back to repairing as Legacy (quick temporary rescue).
Do this now (copy/paste these one block at a time)
A — Identify volumes and confirm Windows installation (very important)
diskpart
list disk
list vol
exit
What to look for:

• Which disk is the NVMe (~1.86 TB) — make sure you will operate on that, not the 12 TB files drive.
• Which volume is the Windows install (largest NTFS; note the drive letter shown by list vol in WinRE — often E: in WinPE).
• Which volume is the small FAT32 EFI (ESP) and its volume number.

If the Windows folder might be on a different letter than you expect, verify:
dir <WinLetter>:\Windows
(e.g. dir E:\Windows). If you don’t see the Windows folder, post the list vol output here and don’t proceed further.
B — Recreate UEFI boot files (best next attempt)
(Replace <WinLetter> with the letter for your Windows partition shown above; replace <ESPvol> with the ESP volume number.
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot <WinLetter>:\Windows /s S: /f UEFI
What this does and why: bcdboot copies winload.efi + supporting files to the ESP and rebuilds the BCD; it’s the recommended fix when /rebuildbcd fails on UEFI systems.

• If you get “Boot files successfully created” → reboot to firmware, set Boot Mode = UEFI (CSM disabled), make “Windows Boot Manager” first, Secure Boot OFF for first test, and try to boot.
• If bcdboot fails with an error (c000000f, access denied, etc., proceed to step C.

C — If bcdboot fails (ESP inaccessible / BCD locked) — clear readonly / rename existing BCD and retry
(Only do these if bcdboot failed previously.
diskpart
select disk 0 <-- confirm it’s the NVMe disk (check list disk output)
attributes disk clear readonly
select vol <ESPvol>
format fs=fat32 quick label=ESP <-- only if you decide to reformat (see note)
assign letter=S
exit
(If there was a BCD in S:\EFI\Microsoft\Boot rename it instead of formatting
ren S:\EFI\Microsoft\Boot\BCD BCD.old
Then rerun:
bcdboot <WinLetter>:\Windows /s S: /f UEFI
Notes:

• Formatting the ESP will remove any existing EFI data. Prefer renaming BCD.old first; only format if the EFI was badly corrupted and you have a backup or can recreate files.
• If you get “Access denied” on format/assign, paste the exact error.

D — If bcdboot succeeds but machine still BSODs 0xC0000001 (INACCESSIBLE_BOOT_DEVICE)
That usually means Windows can’t load the NVMe/storage driver early. Two things to check:
1) Make sure firmware storage setting is AHCI (or correct mode for your controller) and not switched to RAID/IRST unexpectedly. Changing mode can require registry driver tweaks.
2) If needed, load the offline SYSTEM hive and set storage drivers to boot start so Windows loads them early (storport, storahci, nvme). Example (only if you need it — I can walk these through):
reg load HKLM\TEMP_SYSTEM <WinLetter>:\Windows\System32\config\SYSTEM
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
(reg add for storport / storahci / msahci / iaStorV similarly)
reg unload HKLM\TEMP_SYSTEM
Then reboot and test. This is a common fix for inaccessible boot device after moving images between different NVMe/SATA controllers.
E — If you prefer a quick temporary rescue (fallback to Legacy/MBR) — get desktop back fast
If you urgently need to boot right now and don’t care about UEFI:

• In BIOS, enable CSM / Legacy boot and disable Secure Boot.
• Boot Windows Repair media (legacy/CSM).
• Run:
  bootrec /fixmbr
  bootrec /fixboot
  bootrec /scanos
  bootrec /rebuildbcd
  If rebuildbcd still fails with “The requested system device cannot be found,” do the diskpart/list vol checks and then run:
  bcdboot <WinLetter>:\Windows
  This often gets an MBR/Legacy restore running quickly; you can convert to UEFI later.

Extra troubleshooting notes (common gotchas)

• WinRE/WinPE uses temporary drive letters — the Windows partition letter in WinPE often isn’t C:. Always verify with diskpart/list vol and dir <letter>:\Windows before running bcdboot or bootrec.
• If DISM /Get-Drivers errors (Error 32) you saw earlier, that can mean WinPE couldn’t read the offline driver store — but bcdboot + ensuring the ESP is good is usually enough to fix boot first; driver injection is next if device driver mismatch remains.
• If multiple Windows installations or multiple system partitions exist, you may need to explicitly target the correct partition with bcdboot (use the Windows letter found in WinPE).

What I need from you now
1) Paste the output of diskpart → list disk and list vol (so I can confirm the Windows and ESP volume numbers/letters).
2) If you already ran bcdboot, paste its exact output (or paste the exact error you saw when you tried to add the install earlier).
3) Tell me whether you want me to continue trying to fix this UEFI boot (bcdboot + driver / registry steps) or you want the fast Legacy fallback to get back to the known‑good boots immediately.
I’ll stay with you and interpret the outputs. References: community guidance on recreating the EFI and using bcdboot as the reliable fix for UEFI systems, and posts describing the exact “requested system device cannot be found” cases and remedies.