Is for v6

So scenario first.

Imaged whilst in windows installed on SATA SSD.
In rescue media restored image to NVME drive.

On bootup boot is detecting drive, I get windows boot menu loading, I boot but then after a few seconds of loading a BSOD regarding unable to use boot device.

My initial reaction was to go into macrium and try and fix redeploy when I discovered a whole host of problems.

Firstly.  If you go through the redeploy process even without touching anything it will disable intelppm.  Once it does this I have found no way to enable it again.
Second a lot of options seem to not work e.g. if enable on screen driver loading text it doesnt work.
When searching for drivers it fails to find nvme driver via documented method.  However I can point to the specific driverstore path and it finds it, but on the redeploy action screen it reports a failure to activate the driver.  (doesnt state reason).  Apparently this bug was fixed in v7, is v6 not getting backported fixes?
Also if I use the boot fix wizard, interestingly it makes the windows unbootable, this is regardless if BCD is broken or not and if its SATA or NVME, simply it breaks it.  In addition if I try to install macrium boot menu from within windows macrium boot app it also breaks BCD.  For reference this is on windows 8.1.

So what was the fix?

Credit to macrium on one of their knowledge base pages this was mentioned.  I had previously installed a intel RST driver (AHCI not raid driver, not using RAID mode).  I didnt think for one moment this would affect NVME as they different protocols and controllers.  Because intel refuse to support anything other than windows 10 on anything made in the past few years, the newest driver they made that works on Windows 8.1 is the one before they added NVME driver support.  It seems if this intel RST driver is installed it prevents the microsoft NVME driver from been used.

So the fix was right after the image restore, boot into windows safe mode.  Uninstall/deactivate the intel RST driver and reboot.  Thats it.  If I was using msachi driver, it probably would have just booted right up after the image restore.

I did migrate to the samsung nvme driver after tho due to the FUA issues in the stornvme driver.

Interesting, I wouldn't have guessed that having the Intel AHCI driver installed would be an issue either, although one other fix might have been to at least temporarily switch your system to RAID mode and run ReDeploy so that the Intel RST RAID driver could be used and would be "valid" for the hardware configuration.  I thought there were some RST driver versions that supported both NVMe and versions of Windows prior to 10, but maybe they're tough to find now.  Anyhow, Macrium's support policy is that a given major release reaches end of support one year after the next major release arrives.  Reflect V7 launched in February 2017, so V6 support ended February 2018.  Macrium has opted to issue two V6 updates since then to address Windows changes made by Microsoft that created major problems for Reflect, but V6 is still technically no longer supported.