Navigation section

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

Got through step B, rebooted, and got INACCESSIBLE BOOT DEVICE, followed by error 0xc000001
 

Okay — you’re at the point where bcdboot succeeded but Windows still bluescreens INACCESSIBLE_BOOT_DEVICE (0xC0000001). That strongly indicates Windows isn’t loading the storage/NVMe driver early enough. We’ll try the safe, standard offline fixes (non‑destructive) in this order:
1) confirm volumes and letters in WinPE (so we operate on the correct volumes)
2) load the offline SYSTEM hive and make sure the storage drivers are set to boot start (Start=0) — this is the usual fix after imaging to different hardware.
3) if driver files are missing, inject the correct NVMe/Samsung driver into the offline image with DISM, then re-run bcdboot and test.
Follow these exact steps now (copy/paste one block at a time). Stop and tell me the output if anything errors.
A — Confirm which letters WinPE has assigned (VERY important)
diskpart
list disk
list vol
exit
  • Note the Windows partition letter (I’ll assume it’s E: as before) and the EFI/ESP volume number (I’ll assume it’s the small FAT32 volume you earlier assigned as S: or C:). If the letters differ from E: and S: below, substitute the correct letters.
B — Mount the offline SYSTEM hive and confirm the ControlSet
(reg uses the Windows volume letter you confirmed)
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
  • Paste the reg query output here. It will say Current = 0x1 (ControlSet001) most likely — if different I’ll adjust the commands.
C — Set Start=0 for the common storage/NVMe drivers (non‑destructive)
(Replace 001 with the ControlSet number from the step above if needed. Run each line; missing keys are OK.)
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
D — Unload the hive
reg unload HKLM\TEMP_SYSTEM
E — Verify the driver files exist in the offline image and show them
(If Windows volume letter is E:)
dir E:\Windows\System32\drivers*.sys
dir E:\Windows\System32\drivers*nvme 2>nul
dir E:\Windows\System32\drivers\iaStor 2>nul
  • If you see an NVMe driver INF/SYS (e.g., stornvme or vendor nvme .sys) or iaStor files, good. If the NVMe driver is missing, proceed to step F to inject.
F — (Only if the NVMe driver is missing) Inject the correct Samsung NVMe driver into the offline image
  • On another PC download the Samsung NVMe driver package (the INF + .sys files for the 980 PRO). Put them on a USB and note the USB letter in WinPE (say X:).
  • Run:
    dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • If DISM complains, capture the DISM log at X:\Windows\Logs\DISM\dism.log and paste the relevant lines.
G — Recreate UEFI boot files (use the ESP letter you assigned earlier — S: used earlier)
(If you assigned the ESP letter S:)
bcdboot E:\Windows /s S: /f UEFI
H — Reboot and set firmware to UEFI, AHCI, CSM Disabled, Secure Boot Off for first test
  • Enter BIOS → Storage = AHCI, Launch CSM = Disabled, Secure Boot = Off. Put “Windows Boot Manager (Samsung …)” first.
  • Reboot and try.
If it still bluescreens
  • Paste the outputs of the commands above (reg query, dir lines, DISM result, and bcdboot output). I will interpret them and tell you the next step.
  • If driver files were present and Start values are 0 but you still get 0xC0000001, we can either:
    • try converting/writing a proper GPT header with gdisk and reapply bcdboot (non‑destructive), or
    • temporarily enable Legacy/CSM and run bootrec to get you back to desktop quickly (fast fallback) — tell me if you want to use the fallback now.
One quick sanity check before you run the registry edits: confirm you have a current Macrium image of the NVMe (yes/no). If you don’t, pause and make one now — these steps are safe but it’s always best to have a known working backup before changing the offline registry or injecting drivers. fileciteturn4file16turn4file19
Tell me:
1) whether you have a current Macrium image (yes/no) and
2) paste the diskpart list vol output you just ran (or run it now and paste) — then I’ll give any adjusted commands (if letters differ) and wait for the reg query output.
 

@ChatGPT

After step B above, it said:

Current REG_DWORD 0x1

I got through step E, but the NVMe drives and the iaStor files don't seem to have shown up, or any of the files mentioned.

Is there an automated, bootable, free (or very cheap) mechanism to boot into that will acquire and install the SamsungNVMeDriver onto the boot drive?
 

Short answer: there isn’t a single “one‑click, fully automated” tool I trust to both download the correct Samsung NVMe driver and inject it safely into an offline Windows image. The reliable, cheap/free approach is to boot a WinPE environment you already have (Hiren’s PE or the Windows Repair media), download the official Samsung NVMe driver (one small zip) to a USB, then inject it into the offline image with DISM and recreate the UEFI boot files. That’s what most pros do — it’s fast, repeatable and safe.
I’ll give the exact, minimal procedure you can run in Hiren’s PE (you already have it). If you want, I’ll stay with you step‑by‑step while you do it.
Summary of steps (what you’ll do)
1) On another machine, download the Samsung NVMe driver package for the 980 PRO (official Samsung site). Put the extracted driver folder on a USB stick.
2) Boot Hiren’s PE and confirm Windows/E: and ESP/S: letters.
3) Inject the driver into the offline image with DISM.
4) Ensure storage drivers are set to boot (Start=0) in the offline SYSTEM hive.
5) Recreate UEFI boot files with bcdboot and test.
Exact commands and guidance
A — Get the driver
  • On any working PC go to Samsung support and download the “Samsung NVMe Driver” (the zip that contains .inf and .sys files) for your 980 PRO. Extract that zip to a folder on a USB stick (e.g. X:\SamsungNVMeDriver). Use the official Samsung download so you get the correct INF(s) for the model.
B — Boot Hiren’s PE, open Command Prompt, confirm volumes
(You already did this earlier; repeat to be sure letters haven’t changed)
diskpart
list disk
list vol
exit
From the output note:
  • The Windows volume letter (I’ll assume E: from your earlier runs).
  • The ESP volume number and whether it has a letter. If it doesn’t have one you’ll assign S:.
C — Inject the driver into the offline image
(Assume Windows is on E: and USB driver files are on X:\SamsungNVMeDriver\ — change letters to match your environment)
1) Mount the offline SYSTEM hive (we use it later too):
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
(You’ll see Current = 0x1 → use ControlSet001 below.)
2) Add the Samsung NVMe driver into the offline image:
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
Notes:
  • DISM may print success or errors. If it fails with an error, copy the DISM log: X:\Windows\Logs\DISM\dism.log (paste any relevant lines here).
  • If DISM returns Error 32 previously, ensure you are running Hiren’s PE as Administrator (Command Prompt elevated) and that E:\ is the correct Windows image path.
D — Make sure the boot‑time drivers will load
(If you’ve already run these registry edits earlier, repeating is safe.)
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
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
Then unload:
reg unload HKLM\TEMP_SYSTEM
E — Recreate UEFI boot files
  • Make sure the ESP has a letter (I’ll use S:):
    diskpart
    select vol <ESPvol> (replace <ESPvol> with the ESP volume number from list vol)
    assign letter=S
    exit
  • Run:
    bcdboot E:\Windows /s S: /f UEFI
Expected: “Boot files successfully created.”
F — Firmware and test
  • Reboot into UEFI. Set: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled (first test). Set “Windows Boot Manager (Samsung …)” first. Boot.
If it still bluescreens INACCESSIBLE_BOOT_DEVICE
  • Paste:
    • the output you got from the DISM command
    • reg query HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme /v Start (if you re‑mount the hive)
    • the exact bcdboot output
      I’ll interpret them and we’ll either:
  • try gdisk to write GPT headers non‑destructively and retry, or
  • fall back to Legacy/CSM (quick), using bootrec to get back to desktop, then plan a proper UEFI conversion later.
Alternative: “Automated” tools
  • There are GUI driver packs (Snappy Driver Installer Origin, DriverPack) that can auto‑download drivers and install into a running Windows, but they are not recommended for injecting drivers into an offline image reliably and can be large. They’re helpful if you can boot into a temporary Windows environment and let the tool install the NVMe driver to the running system — then capture a good image. SDI is free but not a substitute for the DISM injection route above when working offline.
Bottom line
  • The fastest, reliable route is what I listed: download Samsung’s official NVMe driver to USB, boot Hiren’s PE, run DISM to add the driver into the offline image, set Start=0 for the relevant services, rerun bcdboot, and boot in UEFI mode. That’s free (only your time) and robust.
If you want, I’ll wait while you:
1) confirm you have the Samsung NVMe driver on a USB and tell me the USB drive letter in Hiren’s, and
2) paste the outputs of the diskpart list vol you get now (so I can confirm Windows & ESP letters) — then I’ll give the exact DISM/reg/bcdboot commands tailored to your letters and interpret any errors.
 

@ChatGPT

What is the exact link to get the Samsung NVMe driver, bearing in mind this is a 2TB drive? Come to that, is there a way to acquire or extract the driver off the bootloader of the other, bootable drive, the Win10 Home installed system, and then put that onto a thumbdrive? Anyway, I have given up for the night and am restoring the other drive image, the Win10 Home system.
 

Short answers up front:
  • Official Samsung NVMe driver (the one most people install) is the “Samsung NVM Express Driver” (example file name Samsung_NVM_Express_Driver_3.3.exe). You can get it from Samsung’s Download Center (search for NVMe driver). Example Samsung support page that lists the NVMe driver package.
  • Yes — you can extract the exact driver used on the working Win10 Home system and copy it to a USB, then inject it into the offline (non‑booting) image. That is often the safest approach because it uses the exact driver that worked on your machine.
Below are short step‑by‑step instructions for both options (download from Samsung, or extract from the working system) and then how to inject that driver into the offline image in WinPE/Hiren’s and rebuild UEFI boot files.
A — Download the official Samsung NVMe driver (quick)
  1. On any working PC, go to Samsung’s Download Center / SSD support. Look for “NVMe Driver” (Samsung NVM Express Driver). The Samsung download pages list a package (example: Samsung_NVM_Express_Driver_3.3.exe).
    • If Samsung shows regional pages, pick your region (or the global download center). Download and extract that package to a folder on a USB drive (X:\SamsungNVMeDriver).
  2. Boot your rescue WinPE (Hiren’s) and confirm the Windows and ESP letters (diskpart → list vol). Then inject the driver into the offline image (exact commands below).
B — Extract the working driver from the running Win10 Home system (recommended if you want the exact driver)
This is useful if the working system already has the correct NVMe driver installed.
On the working Win10 Home PC (run as Administrator):
Option 1 — Export drivers with PowerShell (easy)
  • Plug in a thumb drive (e.g. X:). Open an elevated PowerShell and run:
    Export-WindowsDriver -Online -Destination X:\ExportedDrivers
  • After it finishes, open X:\ExportedDrivers and look for folders/INF files that contain “nvme”, “stornvme”, “storport”, “Samsung”, or “iaStor”. Copy the relevant driver folder(s) to the USB root so you can use them on the rescue system.
Option 2 — Use pnputil to list and export specific driver(s)
  • In an elevated CMD:
    pnputil /enum-drivers > C:\drivers-list.txt
  • Inspect drivers-list.txt to find the Published Name / Provider for the Samsung/NVMe driver (look for Samsung or stornvme/iaStor). Then export that driver:
    pnputil /export-driver oemXXXX.inf X:\ExportedDrivers\
    (Replace the oem*.inf name found in the enum list.)
Either way you end up with a folder on USB containing the .inf/.sys/.cat files for the Samsung/NVMe driver.
C — Inject the driver into the offline Windows image in WinPE/Hiren’s
On your rescue environment (you already used Hiren’s), follow these exact commands (change letters to match your environment — Windows offline image on E:, USB driver on X:, ESP on S:):
1) Confirm volumes and letters in WinPE:
diskpart
list disk
list vol
exit
2) (Optional) mount the offline SYSTEM hive if you plan to set Start values later:
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
(You’ll see Current = 0x1 typically; later we’ll use ControlSet001.)
3) Add the driver into the offline image using DISM:
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • If DISM reports success — good. If it errors, save and paste the dism log (X:\Windows\Logs\DISM\dism.log) or the DISM output.
4) Ensure the storage/NVMe driver(s) are set to load at boot (if you haven’t already):
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
5) Recreate UEFI boot files (assign S: to ESP if needed):
diskpart
select vol <ESPvol> ← use the actual vol number for the small FAT32 partition
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
  • Expected: “Boot files successfully created.” If it errors, paste the exact error text.
6) Reboot to firmware and test:
  • In BIOS: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled for first test.
  • Set “Windows Boot Manager (Samsung …)” first and boot.
D — If DISM / driver injection fails (common pitfalls)
  • DISM may fail if the USB/files are not accessible or if file permissions are wrong. Ensure the driver folder contains the INF files and associated .sys files (not just an installer EXE). If you only have an EXE installer, extract it on a working Windows (run the EXE or use 7‑Zip to extract contents), then copy the extracted driver folder to the USB.
  • If Export-WindowsDriver produced many drivers, pick the folder(s) containing Samsung or nvme/stornvme/iaStor and try DISM with that specific path.
E — If you prefer I guide you live (recommended)
Tell me:
1) Do you want the official Samsung download or to extract from the working Win10 Home system? (If working system is available, extracting is usually best.)
2) If extracting, tell me whether you can run PowerShell on the working Win10 Home now so I can give the precise Export-WindowsDriver command sequence and what to copy to the USB.
3) If you prefer downloading: I can give the exact Samsung download URL for the NVMe driver I found (the Download Center entry for the NVMe driver package). Example Samsung NVMe driver package page is listed on Samsung’s site (it’s the “Samsung NVM Express Driver” package).
If you want the Samsung direct download link now, I can paste the URL to the Samsung Download Center NVMe Driver package (region copies exist). Would you like the official Samsung driver link or step‑by‑step extraction from the working system?
 

@ChatGPT

As it happens, I also have the free edition of Disk Genius on a bootable USB thumbdrive. Presumably I could put the Samsung driver on that somewhere, then install from that, either by pointing Hirem PE to it, or by booting from Disk Genius and installing from that.
 

Yes — that will work and is a good plan. You can put the Samsung NVMe driver files on the same USB you use for DiskGenius, then boot Hiren’s PE (or Windows install USB) and inject the driver into the offline Windows image. DiskGenius itself isn’t needed for the driver injection step — use Hiren’s/WinPE + DISM (or pnputil from a running Windows) because those tools install drivers into an offline image reliably.
Below are the exact, practical steps (two extraction options + what to run from WinPE). Read the safety notes and follow the commands exactly, substituting letters/volume numbers from your system.
Quick summary
  • On a working PC: get the Samsung NVMe driver files (INF + SYS) onto USB (either download official Samsung package and extract it, or export the installed driver from your working Win10 Home).
  • Boot Hiren’s PE, confirm the Windows/ESP letters, then run DISM to inject the driver into the offline image, set the storage drivers to boot start, rebuild UEFI boot files with bcdboot, reboot to UEFI.
Step 0 — driver package on USB
Option A — Download official Samsung NVMe driver and extract
  • On a working PC download the official “Samsung NVM Express Driver” package for the 980 PRO from Samsung’s Support / Download Center. Extract the package (run the EXE or use 7‑Zip) to a folder on your USB stick, e.g. X:\SamsungNVMeDriver\ — that folder must contain .inf files (not only an installer exe).
Option B — Export the exact driver from the working Win10 Home (recommended if available)
  • On the working Win10 Home machine (Admin PowerShell), plug your USB (X:), then run:
    Export-WindowsDriver -Online -Destination X:\ExportedDrivers
  • Inspect X:\ExportedDrivers for a folder containing the Samsung/NVMe INF and SYS files (look for names containing nvme, stornvme, Samsung, iaStor). Copy that folder to X:\SamsungNVMeDriver\ (or use it as-is).
Either option gives you a folder on USB with the .inf/.sys you need.
Step 1 — boot Hiren’s PE and confirm volumes
  • Boot Hiren’s PE and open an elevated Command Prompt. Run:
    diskpart
    list disk
    list vol
    exit
    Note the Windows offline volume letter (we used E: before) and the small FAT32 ESP volume number (we used S: or vol 2 earlier). Use the letters/vol numbers you see.
Step 2 — inject driver into the offline image with DISM
  • Assuming Windows offline is E: and your USB is X: and driver folder is X:\SamsungNVMeDriver\ :
    dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • If DISM reports success, good. If it errors, copy the DISM log (X:\Windows\Logs\DISM\dism.log) and paste the relevant lines; common problems are using an installer EXE instead of extracted INF files.
Step 3 — ensure the drivers will load at boot (offline SYSTEM hive edits)
  • Mount SYSTEM hive and set boot start:
    reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
    reg query HKLM\TEMP_SYSTEM\Select /v Current
    (If Current = 0x1, the control set is ControlSet001 — adjust if different.)
    reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
    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 unload HKLM\TEMP_SYSTEM
  • Missing keys are OK — you’ll see an error if a key doesn’t exist; continue.
Step 4 — recreate UEFI boot store
  • Make sure ESP has a drive letter (use the ESP vol number you noted above). Example:
    diskpart
    select vol <ESPvol>
    assign letter=S
    exit
  • Then:
    bcdboot E:\Windows /s S: /f UEFI
  • Expected: “Boot files successfully created.”
Step 5 — firmware settings and test
  • Reboot -> enter BIOS:
    • Storage = AHCI
    • Launch CSM = Disabled
    • Secure Boot = Disabled (first test)
    • Boot order: put “Windows Boot Manager (Samsung …)” first
  • Save & boot. If it still BSODs INACCESSIBLE_BOOT_DEVICE, paste the bcdboot output and any error messages you saw.
If DISM is not available in your WinPE
  • Use a Windows install USB (the official Windows installer WinPE includes DISM). Or boot a temporary Windows (if you can) and use pnputil or Export‑WindowsDriver to install the driver to the running OS, then image that working system.
If you prefer DiskGenius for copying files
  • DiskGenius can copy the extracted driver files into the offline Windows folders (E:\Windows\System32\drivers and related INF locations), but copy alone doesn’t register drivers into the offline driver store — DISM is preferred because it updates the offline driver store properly. If you must use DiskGenius, copy the extracted driver folder to the Windows image (e.g. E:\TempDrivers) and then run DISM from WinPE pointing at that folder.
Notes / pitfalls
  • Make sure the driver you use is the driver package (INF + SYS). An EXE installer must be extracted first. Use 7‑Zip or run the EXE on a working Windows to extract the driver files.
  • Use the exact driver architecture (x64) that matches your Windows.
  • If DISM errors with access or lock issues, run it from WinPE after ensuring E: is the offline Windows volume and you’re running an elevated prompt.
If you want live help now
Tell me:
1) Do you want to extract the driver from the Win10 Home system (I can give the exact Export-WindowsDriver command to run there), or do you want to download the official Samsung NVMe driver package and I’ll give the link?
2) While you have Hiren’s PE booted, paste the diskpart → list vol output (so I can verify Windows letter and ESP vol) and tell me the USB drive letter where you placed the driver files (in Hiren’s). I’ll then give the exact DISM/reg/bcdboot commands using your letters and wait for your outputs.
If you want the Samsung download link now, tell me your preferred region and I’ll provide the official Samsung Download Center link to the NVMe driver package.
 

@ChatGPT

I ran the export-windowsdriver command, and it gave me a bunch of folders, but none of them seem to have anything like nvme, stornvme, Samsung, or iaStor in them.

I have attached a textfile with the full output of the command.

I have also downloaded Samsung_NVM_Express_Driver_3.3.exe but there doesn't seem to be a way to simply extract the drivers to a folder from inside it.
 

Attachments

Thanks — that helps. Short summary: you didn’t find an NVMe driver in the exported driver set (not unusual — Windows may be using a Microsoft built‑in NVMe driver), and you’ve got Samsung_NVM_Express_Driver_3.3.exe available. The easiest reliable next step is to extract the actual .INF/.SYS driver files from that EXE (or export the exact driver from the working Win10 Home if it’s present there) and then inject them into the offline image via DISM from WinPE (Hiren’s). Below I give concrete extraction methods (pick one you can do), then the exact injection and repair commands to run in Hiren’s PE. I’ll stay with you step‑by‑step if you want.
Option A — Extract the driver from Samsung_NVM_Express_Driver_3.3.exe (recommended)
1) On a working Windows PC, get 7‑Zip portable (free) if you don’t already have it:
  • Download 7‑Zip and install, or copy 7z.exe (portable) to a folder.
2) Extract the EXE’s contents with 7‑Zip (GUI or CLI):
  • GUI: right‑click Samsung_NVM_Express_Driver_3.3.exe → 7‑Zip → Open archive → Extract to X:\SamsungNVMeDriver.
  • CLI (if you have 7z.exe):
    7z x Samsung_NVM_Express_Driver_3.3.exe -oX:\SamsungNVMeDriver\
You want a folder that contains .inf files and .sys files (the driver package). If the EXE only contains an installer MSI, 7‑Zip should still extract the MSI; open the MSI with 7‑Zip and extract its contents to get the .inf/.sys. If the EXE unpacks to a temporary folder during a normal run, you can run it on a working PC and watch %TEMP% for an extracted folder (copy that folder to USB).
Option B — Export the driver from the working Win10 Home machine (works when the working system actually has the driver)
1) On the working machine, plug in your USB (X:). Open an elevated PowerShell and run:
Export-WindowsDriver -Online -Destination X:\ExportedDrivers
2) Inspect X:\ExportedDrivers for a folder containing Samsung / NVMe / stornvme / iaStor INF files. If you find it, that folder is what you’ll use to inject into the offline image. If you don’t find anything NVMe‑related, use Option A (Samsung EXE extraction).
Option C — Identify driver names on the working system (if you need to find which driver to export)
1) In elevated CMD on the working PC:
pnputil /enum-drivers > C:\drivers.txt
2) Open drivers.txt and search for “nvme”, “stor”, “Samsung”, “stornvme”, or “iaStor” to find the published name (oemXX.inf). Then export that driver:
pnputil /export-driver oemXX.inf X:\ExportedDrivers\
After you have a folder on USB (X:\SamsungNVMeDriver\ or X:\ExportedDrivers), continue on the rescue machine.
Injecting the driver into the offline image (Hiren’s PE / WinPE)
Boot Hiren’s PE, open an elevated Command Prompt and do these steps (replace letters with what your environment shows — verify with diskpart/list vol before running):
1) Confirm disks/volumes (so you know the Windows letter and ESP volume number)
diskpart
list disk
list vol
exit
Note the Windows volume letter (I’ll call it E: below) and the ESP volume number (I’ll call <ESPvol>).
2) (Optional) Mount offline SYSTEM hive (we use it later to set Start values if needed)
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
— note the Current value (usually 0x1 → ControlSet001)
reg unload HKLM\TEMP_SYSTEM
3) Inject the extracted Samsung driver into the offline image:
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • If DISM returns success, good. If it errors, copy the DISM log (X:\Windows\Logs\DISM\dism.log) and paste any relevant errors here.
4) Ensure the NVMe/storage drivers are set to boot start (to load early)
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
(If any registry add reports “key not found,” that’s okay — just continue.)
5) Rebuild UEFI boot files onto the ESP
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
Expected: “Boot files successfully created.”
6) Reboot to UEFI firmware
  • BIOS: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled (first boot)
  • Set Windows Boot Manager (Samsung…) first and boot.
If it still fails (INACCESSIBLE_BOOT_DEVICE)
  • Paste the exact DISM output from step 3 and the bcdboot output. If the driver injection succeeded and Start=0 applied but Windows still fails, we can:
    • run gdisk to ensure the disk has a proper GPT (non‑destructive), then reapply bcdboot, or
    • fallback to Legacy boot for immediate use (enable CSM, run bootrec /fixmbr etc.), then plan a clean UEFI conversion later.
Notes and tips
  • The key thing is the folder you pass to DISM must contain the .inf files. If the Samsung EXE doesn’t extract easily, use 7‑Zip to extract it or run it temporarily on a working Windows and copy the extracted files from %TEMP% or from the unpacked MSI.
  • If Export-WindowsDriver produced many folders but none looked like NVMe, that simply means the working Win10 is using Microsoft’s in-box driver. Using Samsung’s package is still OK; Samsung’s driver can be injected even if Win10 uses MS driver currently.
  • If you want, paste here the diskpart list vol output from Hiren’s now and the USB drive letter (X:) so I can give the exact DISM/reg/bcdboot commands tailored to your letters.
Would you like:
A) The exact Samsung download link for your region (I can paste it), or
B) Step‑by‑step help extracting the EXE with 7‑Zip (I can give the exact 7z command), or
C) Live step‑through while you plug the USB into the rescue system (tell me the drive letters shown by list vol) so I provide the precise commands to run?
 

@ChatGPT

Upon extracting the exe with 7-zip, all I see is a file named 0 and some files named u0 through u40
 

Good — thanks for the info. The u0…u40 fragments are exactly what I expected: the Samsung EXE is a self‑extracting installer that didn’t present plain INF/.SYS files to 7‑Zip. The fastest, most reliable way to get the actual INF/.SYS driver files you need is to run that Samsung installer on a working Windows machine (or extract its MSI/temp unpack folder) and then export the installed driver to your USB. Below are two safe, practical routes — pick the one you prefer and I’ll stay with you step‑by‑step.
Important safety note
  • Do this on a working Windows machine (your Win10 Home machine). Make a System Restore point or a quick image before you install the Samsung driver if you’re worried about changing that system. The operations below are reversible but it’s good to have a backup.
Option 1 — Recommended (install the Samsung package on the working Win10 Home, then export the driver)
1) On the working Win10 Home machine:
  • Run Samsung_NVM_Express_Driver_3.3.exe and install the driver. If the installer asks whether to “Install” or “Extract,” choose whichever gives you an extraction path; otherwise run the installer to install the driver. If it requires a reboot, reboot.
  • (Optional but recommended) Create a restore point or a Macrium image of that working system before you install.
2) After install (or after reboot if required), export the driver to your USB:
  • Plug your USB (assume it becomes X:).
  • Open an elevated PowerShell and run:
    Export-WindowsDriver -Online -Destination X:\ExportedDrivers
  • Wait for it to finish.
3) Find the NVMe/Samsung driver folder on the USB:
  • Open X:\ExportedDrivers in Explorer. Look for folders whose contents include .inf files and names that contain Samsung, nvme, stornvme, stornvme, stornvme.sys, or iaStor*. If you find one, copy that folder (or the whole ExportedDrivers folder) to X:\SamsungNVMeDriver\ (so you have X:\SamsungNVMeDriver\INFfiles...).
If you don’t see any NVMe/Samsung driver in ExportedDrivers, it means the Samsung installer either failed to register the driver into the driver store or the working system is still using the Microsoft in‑box NVMe driver. In that case proceed to Option 2.
Option 2 — Extract files from the EXE if you don’t want to install
1) Use 7‑Zip on the working PC to extract the EXE. If 7‑Zip gives you u0..u40, try extracting the embedded MSI:
  • 7‑Zip may show the MSI inside. If you see .msi, extract that and open it in 7‑Zip and extract the DriverFiles folder (INF/.SYS).
  • If 7‑Zip does not show an MSI and only shows u0..u40 fragments, run the EXE once; it usually unpacks to a temp folder (e.g., C:\Users\<you>\AppData\Local\Temp\<random>). After running the EXE (don’t finish installation) check %TEMP% for a folder named similar to the driver package, copy that folder to the USB, and cancel the install (or finish then uninstall if you don’t want it on that machine).
If extraction fails, Option 1 (install then export) is the simpler path.
Once you have the driver files on the USB (folder with .inf/.sys)
(Assume offline Windows image = E:, USB = X:, driver folder = X:\SamsungNVMeDriver\, ESP volume number = <ESPvol> — adjust letters to match your environment)
Boot Hiren’s PE and run these exact commands (I’ll explain each):
1) Confirm volumes (so we use correct letters)
diskpart
list disk
list vol
exit
2) Inject the driver into the offline image with DISM
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
  • If DISM reports success, proceed. If it errors, copy the DISM log (X:\Windows\Logs\DISM\dism.log) and paste the relevant lines here.
3) Ensure the NVMe/storage drivers load at boot (offline registry edits)
reg load HKLM\TEMP_SYSTEM E:\Windows\System32\config\SYSTEM
reg query HKLM\TEMP_SYSTEM\Select /v Current
(If Current = 0x1 then ControlSet001 is the one to edit)
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\nvme" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
(If any “key not found” error appears, that driver simply isn’t present — continue with the others.)
4) Recreate UEFI boot files (ensure the ESP has a letter)
diskpart
select vol <ESPvol> <-- replace <ESPvol> with the ESP volume number you saw from list vol
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
Expected: “Boot files successfully created.”
5) Reboot to UEFI and test
  • BIOS: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled initially.
  • Put “Windows Boot Manager (Samsung …)” first, save and reboot.
If it still bluescreens 0xC0000001
  • Paste the DISM output and the bcdboot output and I’ll interpret. If driver injection succeeded but Windows still fails, we can:
    • run gdisk to write GPT headers non‑destructively and reapply bcdboot, or
    • as a fallback enable Legacy/CSM and use bootrec to get you back on desktop immediately.
If you want, I’ll wait while you:
  • run the Samsung installer on the working machine and export drivers (I can give exact PowerShell command again), or
  • run the extraction (7‑Zip) and tell me what files you found (paste the folder listing), or
  • boot Hiren’s now and paste diskpart → list vol plus the USB drive letter so I can give the exact DISM/reg/bcdboot commands for your letters.
Which do you prefer:
A) I guide you to install the Samsung EXE on the working Win10 and export the driver (recommended & simplest), or
B) I guide you to extract the EXE contents and find the INF/.SYS files without installing, or
C) you want the direct Samsung download link for the driver package (I can paste it for your region)?
Tell me which and I’ll give the exact next command(s).
 

@ChatGPT

Made an incremental backup of my Win10 Home.

Clicked the exe, it tells me:

Samsung NVM Express Device is not connected. Connect the Device and try again.

What now?
 

That “Samsung NVM Express Device is not connected” message simply means the installer didn’t find a Samsung NVMe device in that PC (or it expects the drive on the machine you ran it on). It doesn’t mean the installer can’t give you the .INF/.SYS files — the installer normally unpacks them first. Because 7‑Zip showed u0…u40 fragments, the EXE is a self‑extracting package; you still can get the actual driver files (INF/SYS) by one of these reliable methods.
Pick one of these two practical options (A is usually easiest) — I’ll stay with you step‑by‑step if you want.
Option A — Run the Samsung EXE on the working PC and copy the unpacked driver files from the temp folder
1) Run the installer once on the working Windows machine (elevated). It will probably fail with the “device not connected” message but it usually unpacks to a temp folder first.
2) Immediately open %TEMP% and sort by Date Modified. Look for a folder whose name looks like Samsung, NVMe, or a random GUID that appeared just now.
  • Open that folder; you’re looking for .inf and .sys files (or an MSI). Copy the whole folder to your USB (e.g. X:\SamsungNVMeDriver).
    If you can’t find the folder in %TEMP%, try this quick command in an elevated CMD right after running the installer to find recently changed folders:
    • powershell -command "Get-ChildItem $env:TEMP -Directory | Sort-Object LastWriteTime -Descending | Select-Object -First 20 | Format-List FullName,LastWriteTime"
      That will show the most recent temp folders; check the top entries for the Samsung unpack.
Option B — Extract the EXE contents (7‑Zip / MSI extraction / Universal Extractor)
Try these in order on the working PC:
1) Use 7‑Zip to list contents (in an elevated command prompt or GUI):
  • 7z l Samsung_NVM_Express_Driver_3.3.exe
    If it shows an .msi or .cab, extract that:
  • 7z x Samsung_NVM_Express_Driver_3.3.exe -oC:\temp\SamsungDriver
  • If you see a .msi inside, extract it: 7z x setup.msi -oC:\temp\SamsungDriverMSI
    Then open the extracted folder for .inf/.sys files.
2) If 7‑Zip only shows u0..uNN files:
  • Try extracting the u* pieces with 7‑Zip (sometimes they are nested cabs):
    7z x u0 -oC:\temp\SamsungDriver
    7z x u1 -oC:\temp\SamsungDriver
    … (do for the files you see)
  • Or use Universal Extractor or lessmsi (free) to extract any MSI if present:
    • lessmsi GUI: open extracted .msi and extract files.
    • Universal Extractor: open the EXE and let it extract all resources.
If any of these yield a folder containing .inf and .sys files, copy that folder to your USB (X:\SamsungNVMeDriver).
Direct Samsung download (if you prefer to re‑download)
Once you have the extracted driver folder (INF + SYS) on USB, inject it into the offline image in Hiren’s PE:
In Hiren’s (exact commands; replace letters as needed)
1) Confirm volumes:
diskpart
list disk
list vol
exit
2) Inject driver:
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
(Replace E: with your offline Windows letter, X: with your USB letter.)
3) Make the driver load early (if not already done):
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
4) Rebuild UEFI boot files:
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
5) Reboot to UEFI (CSM disabled), set Windows Boot Manager first and test.
If DISM gives errors or you can’t extract the INF/SYS, tell me:
  • Which OS you have on the working machine and whether you can run the Samsung installer there (it failed before) — confirm you ran it as admin.
  • The exact 7‑Zip listing output (paste the 7z l output or the %TEMP% listing) and I’ll parse it and tell you which u* to extract or which MSI to pull out.
If you prefer, I’ll wait while you run the installer on the working PC, then run the PowerShell temp‑folder listing I gave and paste the top few results — I’ll tell you exactly which folder to copy to USB and then we’ll inject it into the offline image. Which approach do you want to try now?
 

@ChatGPT

Running the Samsung exe does not seem to be placing the relevant folder into Temp, it just goes directly to the message that it can't find the drive, and no new folders show up in Temp. I downloaded and unpacked Universal Extractor, but I must be using it wrong because I'm not getting anywhere with pointing it at the u0 through u40 stuff, or pointing it at the driver exe, either. I did try opening some of the u0 through u40 files via 7zip, but I don't see the right elements showing up in the ones I examined. I tried having Universal Extractor extract the whole exe contents, but it then threw an error that it ran out of memory and so couldn't continue.
 

Thanks — that rules out the easy extract. The Samsung EXE you have is a self‑extracting installer that in some builds unpacks into nested u0..uNN pieces or an MSI; if 7‑Zip only shows u0..u40 and running the EXE immediately fails with “device not connected,” you still have three reliable ways to get the real .INF/.SYS files you need. Pick whichever fits you and I’ll walk you through it.
Short options (pick one)
  • Option 1 (recommended): Run the Samsung installer on the working Win10 Home PC, let it unpack, then export the installed driver to USB with Export‑WindowsDriver. This usually finds the INF/.SYS you need.
  • Option 2: Extract the EXE/MSI manually: use 7‑Zip, lessmsi or Universal Extractor to pull the embedded MSI or .cab and extract the driver files. If 7‑Zip showed only u0..u40, you likely need to extract the embedded MSI from the EXE or inspect %TEMP% after running the EXE.
  • Option 3: If those fail, download the official Samsung NVM Express driver package (Samsung site) on a working PC, run/extract it there and copy the extracted driver folder to USB. That package is the same driver you need.
Detailed step‑by‑step for each option
Option 1 — Install then Export (simplest / most reliable)
1) On the working Win10 Home PC (make an incremental image / restore point first — you already did that): run Samsung_NVM_Express_Driver_3.3.exe (right‑click → Run as administrator). If it refuses to install because it doesn’t detect the Samsung device, it will usually still unpack files first.
2) Immediately after launching the installer (if it returns the “device not connected” message), open an elevated PowerShell and run:
Export-WindowsDriver -Online -Destination X:\ExportedDrivers
(where X: is your USB drive)
3) Inspect X:\ExportedDrivers for folders whose contents include .inf and .sys and names like Samsung / nvme / stornvme / iaStor. Copy that entire folder to a simple path on the USB, e.g. X:\SamsungNVMeDriver.
Notes: if Export‑WindowsDriver didn’t include any NVMe/Samsung driver, it means Windows is using the MS in‑box driver on that machine — you’ll still be able to use the official Samsung package (Option 3) to get vendor driver files.
Option 2 — Extract the EXE/MSI without installing
1) Try to extract the EXE with 7‑Zip (GUI or CLI). In an elevated CMD where 7z.exe is available:
7z l Samsung_NVM_Express_Driver_3.3.exe ← lists contents
7z x Samsung_NVM_Express_Driver_3.3.exe -oC:\temp\SamsungDriver
2) If 7‑Zip shows an MSI inside (or a cab) extract that MSI and open it with 7‑Zip:
7z x setup.msi -oC:\temp\SamsungDriverMSI
then inspect C:\temp\SamsungDriverMSI for a DriverFiles or similar folder with .inf/.sys.
3) If 7‑Zip only shows u0..uNN fragments:
  • Run the EXE once (as admin) and immediately run this PowerShell to list the most recently modified temp folders:
    powershell -command "Get-ChildItem $env:TEMP -Directory | Sort-Object LastWriteTime -Descending | Select-Object -First 20 | Format-List FullName,LastWriteTime"
  • Check the top results for a Samsung or similarly named folder and copy it to USB.
    4) If you find an MSI, you can also use lessmsi (free) to extract it:
    lessmsi x installer.msi C:\temp\SamsungDriver
    5) If Universal Extractor throws memory errors, try extracting just one u* file at a time with 7‑Zip (7z x u0 -oC:\temp\u0) — sometimes the MSI parts are split and appear inside specific fragments. It’s slower but often succeeds.
Option 3 — Download official Samsung driver and extract on working PC
1) On a working PC download the Samsung NVM Express Driver package (Samsung Download Center). (If you want I can paste the Samsung page link for your region.)
2) Use 7‑Zip to extract the EXE or MSI as in Option 2, or run the installer on the working PC (it may allow “Extract” or will unpack files to %TEMP%). Copy extracted INF/SYS to USB.
What to do once you have a driver folder on USB (this is where we get the offline image fixed)
Boot Hiren’s PE (or Windows install USB) and run these exact commands — I’ll tailor the drive letters if you paste your diskpart → list vol first.
A) Verify volumes:
diskpart
list vol
exit
B) Add the driver into the offline image (replace letters as appropriate; example uses E: = offline Windows, X: = USB):
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
C) Set storage/NVMe drivers to load early (if needed):
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
D) Recreate UEFI boot files (assign S: to ESP if needed):
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
E) Reboot to BIOS/UEFI: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled (first test). Put Windows Boot Manager first and test.
If DISM errors or bcdboot still fails, paste the DISM log (X:\Windows\Logs\DISM\dism.log) and the bcdboot output and I’ll interpret.
If you want live help now
  • Say which option you want (1, 2 or 3). If Option 1 or 2, tell me:
    • whether you can run the Samsung EXE on the working machine right now, and
    • if you can, paste the PowerShell temp folder listing after you run it (the command I gave), or paste the 7‑Zip list output for the EXE.
  • If you prefer I give the direct Samsung download URL for your region I can paste that next (I found the official Samsung package reference on Samsung’s download pages).
Which route do you want to try next?
 

@ChatGPT

I right-clicked the Samsung exe and selected run as administrator, it still is not giving me a folder in Temp, I do notice a textfile named Samsung_NVM_Express_Driver_20251025174746.log and another named 323e4671-27cc-436a-b4f3-21b731e08e63.tmp dated from a moment ago, I tried opening the tmp file in Notepad but it couldn't read it, and now the tmp file shows as 0 bytes with a newer datestamp than before.

I have attached the Samsun log file.
 

Attachments

Thanks — that explains why 7‑Zip looked useless: the Samsung SFX unpacker has split the payload into numbered fragments (u0…u40) or uses a packaged MSI that the installer refuses to unpack unless it thinks the device is present. You can still get the driver files. Below I give the most reliable, ordered options (from least invasive → more manual). Try them in order until you extract a folder that contains .INF/.SYS files. I’ll include exact commands you can copy/paste.
You already made an incremental backup — good.
Option 1 — Try the installer with extraction switches (fast)
Some Samsung/InstallShield SFX packages accept extract switches even when the device isn’t present.
1) Open an elevated Command Prompt where Samsung_NVM_Express_Driver_3.3.exe sits and run these (one at a time) until one produces an extracted folder:
Samsung_NVM_Express_Driver_3.3.exe /extract "C:\Temp\SamsungDriver"
Samsung_NVM_Express_Driver_3.3.exe /x "C:\Temp\SamsungDriver"
Samsung_NVM_Express_Driver_3.3.exe /e "C:\Temp\SamsungDriver"
Samsung_NVM_Express_Driver_3.3.exe -x "C:\Temp\SamsungDriver"
Samsung_NVM_Express_Driver_3.3.exe /? (to show supported args)
If any of those create C:\Temp\SamsungDriver containing .inf/.sys files, copy that folder to your USB and skip to the DISM injection step below.
Option 2 — Let the EXE unpack to TEMP (run then quickly inspect %TEMP%)
If running the EXE immediately exits (shows “device not connected”) it may still have briefly unpacked files and removed them. Try this sequence:
1) In an elevated PowerShell, open the TEMP folder listing so you can see new folders (run this, then immediately run the Samsung EXE):
powershell -command "Get-ChildItem $env:TEMP -Directory | Sort-Object LastWriteTime -Descending | Select-Object -First 20 | Format-List FullName,LastWriteTime"
2) Right after launching the EXE (Run as Admin), rerun the above PowerShell command and look for new folders with recent timestamps. If you see one that looks Samsungish or new, copy it to USB.
If you find nothing, proceed to Option 3.
Option 3 — Concatenate u0..u40 fragments and attempt extraction
If 7‑Zip shows the fragments u0..u40, they may be parts of a single archive. Concatenate them in order and try to extract.
On a working Windows machine or in the folder with the u* files, run (PowerShell recommended to preserve byte order):
powershell -Command "
$out = [IO.File]::Create('C:\Temp\combined.bin');
Get-ChildItem -Path . -Filter 'u*' | Sort-Object Name | ForEach-Object {
$in = [IO.File]::OpenRead($_.FullName);
$in.CopyTo($out);
$in.Close();
};
$out.Close();
"
Then try to extract combined.bin with 7‑Zip:
"C:\Program Files\7-Zip\7z.exe" x C:\Temp\combined.bin -oC:\Temp\SamsungDriver
If that produces a usable folder with .inf/.sys, copy to USB and proceed to DISM steps. If 7‑Zip fails, try:
"C:\Program Files\7-Zip\7z.exe" l C:\Temp\combined.bin (to list contents)
Option 4 — Extract embedded MSI using lessmsi (if present)
If 7‑Zip shows an .msi inside the EXE (or you can get the combined.bin to reveal an MSI), use lessmsi to extract:
lessmsi x installer.msi C:\Temp\SamsungDriver
Option 5 — Install on another machine that has a Samsung NVMe (or attach the drive)
If you have another machine that contains a Samsung NVMe (or if you can temporarily connect the 980 PRO to your working PC), run the Samsung EXE there normally — it will install and place the driver into the Windows driver store. Then on that PC run:
Export-WindowsDriver -Online -Destination X:\ExportedDrivers
Find the Samsung/NVMe driver folder inside X:\ExportedDrivers and copy it to your USB.
Option 6 — Download the vendor package and/or use alternative official link
If you prefer to re-download: go to Samsung’s Download Center and search for “Samsung NVM Express Driver” (the package you already have). If extraction still fails, try downloading on a working machine and use one of the extraction methods above there. (I can paste an official Samsung download URL for you if you want.)
Once you have a folder on USB that contains .INF files and .SYS files (the driver payload), do this from Hiren’s PE to inject it and rebuild UEFI boot:
Inject driver and rebuild UEFI boot (exact commands)
Boot Hiren’s PE, open elevated Command Prompt, then:
1) Confirm letters
diskpart
list disk
list vol
exit
Note the Windows offline letter (e.g. E:) and the ESP volume number (e.g. 2). Adjust the letters in the next commands as needed.
2) Inject driver (assume E: = offline Windows, X: = USB with folder X:\SamsungNVMeDriver)
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
3) Make sure NVMe/storage drivers are set to boot start
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
4) Assign ESP letter and run bcdboot (replace <ESPvol> and E: as appropriate)
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
5) Reboot and set BIOS to: Storage = AHCI, Launch CSM = Disabled, Secure Boot = Disabled (first test). Put Windows Boot Manager first.
If that still produces INACCESSIBLE_BOOT_DEVICE 0xC0000001:
  • Paste here the output of the DISM command (it will say success or print errors),
  • Paste the bcdboot output,
  • If DISM failed, paste the DISM log lines (X:\Windows\Logs\DISM\dism.log).
If you want, I’ll stay connected and walk you through whichever option you pick:
  • Try first: re-run the Samsung EXE and then run the PowerShell TEMP listing command to see if any temp folder appeared (paste the top few results). If nothing appears, try Option 3 concatenation approach (PowerShell concatenation) and then 7‑Zip extraction — I can provide the one‑line PowerShell concatenation again if you want to try it now.
Which do you want to try next? I recommend:
  • If you can run the Samsung EXE on the working machine: run it then run the PowerShell temp listing and paste the top results (I’ll tell you which folder to copy).
  • If that fails, I’ll give the PowerShell concatenation + 7‑Zip commands to try extracting the u0..u40 pieces.
 

@ChatGPT

I try to invoke the first command from Option 1, and it throws an error about the samsung exe is not a recognized command or script. I have attached the shell output in a text file.
 

Attachments

Thanks — that makes sense. The Samsung installer you have is an SFX that’s packaging its payload into fragments (u0..u40) and/or an MSI; some builds refuse to unpack unless they detect the Samsung device. You still have good options. Pick one and I’ll walk you through it — I’ll stay with you step‑by‑step if you want.
Short plan (try in this order):
1) Try the installer extraction switches (fast, non‑destructive).
2) Run the EXE and immediately inspect %TEMP% for an unpack folder (PowerShell helper).
3) If only u0..u40 exist, concatenate them into one file and try extracting that with 7‑Zip.
4) If none of the above work, install the EXE on a machine that actually has a Samsung NVMe (or temporarily attach the 980 PRO to a working PC), then run Export‑WindowsDriver to capture the real INF/SYS files.
5) Once you have the extracted driver folder (INF + SYS), inject it into the offline image with DISM, set the driver Start=0 in the offline SYSTEM hive and run bcdboot (I gave the exact DISM / registry / bcdboot commands earlier).
Commands and exact steps you can run now
A — Try the installer extraction switches (run from an elevated CMD inside the folder that holds the EXE)
Open cmd.exe as Administrator, change to the folder with the EXE, then try each of these (one at a time):
"C:\path\to\Samsung_NVM_Express_Driver_3.3.exe" /extract "C:\Temp\SamsungDriver"
"C:\path\to\Samsung_NVM_Express_Driver_3.3.exe" /x "C:\Temp\SamsungDriver"
"C:\path\to\Samsung_NVM_Express_Driver_3.3.exe" /e "C:\Temp\SamsungDriver"
"C:\path\to\Samsung_NVM_Express_Driver_3.3.exe" -x "C:\Temp\SamsungDriver"
"C:\path\to\Samsung_NVM_Express_Driver_3.3.exe" /?
If any of these create C:\Temp\SamsungDriver that contains .inf and .sys files, copy that folder to your USB and skip to the DISM injection step below. (If the EXE isn’t in your PATH you must use the full path — that’s why you saw “not recognized”.)
B — If running the EXE returns quickly, inspect TEMP immediately
1) Open an elevated PowerShell BEFORE you run the EXE, run this to capture the last 20 temp folders:
powershell -command "Get-ChildItem $env:TEMP -Directory | Sort-Object LastWriteTime -Descending | Select-Object -First 20 | Format-List FullName,LastWriteTime"
2) Now run the Samsung EXE (Run as admin). Immediately re-run the PowerShell command above and compare the top entries for a new folder. If you see a new folder created during the run, copy it to USB (that’s the unpacked driver). If you find it, you’re done with extraction.
C — If you only have u0..u40 fragments: concatenate and extract
On the working Windows PC, in the folder that contains u0..u40 run this PowerShell snippet to concatenate them in filename order into one file, then try to extract with 7‑Zip:
powershell -Command "
$out = [System.IO.File]::Create('C:\Temp\combined.bin');
Get-ChildItem -Path . -Filter 'u*' | Sort-Object Name | ForEach-Object {
$in = [System.IO.File]::OpenRead($_.FullName);
$in.CopyTo($out);
$in.Close();
};
$out.Close();
"
Then (if 7‑Zip is installed):
"C:\Program Files\7-Zip\7z.exe" x C:\Temp\combined.bin -oC:\Temp\SamsungDriver
If 7‑Zip lists or extracts an embedded MSI, extract that MSI (7z x installer.msi -oC:\Temp\SamsungDriver) and look inside for .inf/.sys.
D — If extraction still fails: install on a PC that has a Samsung NVMe (recommended if possible)
If you can temporarily attach the 980 PRO to any working Windows PC (or run the installer on a different machine that has a Samsung NVMe), the installer will succeed and place the driver in the Windows driver store. Then export the driver:
1) On that working PC (Admin PowerShell):
Export-WindowsDriver -Online -Destination X:\ExportedDrivers
2) Inspect X:\ExportedDrivers for folders with .inf/.sys for Samsung or NVMe and copy that folder to X:\SamsungNVMeDriver\ on your USB.
E — If you have a driver folder (INF + SYS) on USB, inject it into the offline image (Hiren’s PE)
Boot Hiren’s PE, open an elevated command prompt and run (adjust letters to match your environment — confirm with diskpart → list vol first):
diskpart
list vol
exit
dism /Image:E:\ /Add-Driver /Driver:X:\SamsungNVMeDriver\ /Recurse
(registry edits to ensure driver loads early)
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
reg add "HKLM\TEMP_SYSTEM\ControlSet001\Services\stornvme" /v Start /t REG_DWORD /d 0 /f
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 unload HKLM\TEMP_SYSTEM
(assign S: to the ESP and rebuild UEFI BCD)
diskpart
select vol <ESPvol>
assign letter=S
exit
bcdboot E:\Windows /s S: /f UEFI
Reboot to UEFI with Storage=AHCI, CSM disabled, Secure Boot off for first test.
(Those steps and the rationale are the same approach I recommended earlier.)
If you’d like me to continue now
  • Tell me which option you want to try next (A, B, C, D, or E).
  • If you want A or B, paste the PowerShell temp listing output after you run the EXE so I can point to the right folder to copy.
  • If you want C I’ll provide the one‑line concatenation again and the 7‑Zip extraction command to run.
  • If you want D I’ll give the exact Export‑WindowsDriver command to run on the machine where you install the driver.
If you’d rather stop and keep the Win10 Home restore for now, that’s fine — but if you want to continue tonight, tell me which option and I’ll walk you through the exact commands and watch your outputs.
 

You must log in or register to reply here.

Similar threads

ChatGPT
  • Featured
  • Article Article
How to Transfer Windows to a New Drive: Complete Guide for Safe Migration
Replies
0
Views
2K
ChatGPT
ChatGPT
Back
Top