Thanks for the respons
For drivers, first of all, understand that ReDeploy only concerns itself with boot-critical drivers, so it's entirely possible that Windows 10 will include the necessary drivers for your new PC. That might simplify things for you, although it does mean that you'll need to deal with any other drivers after you get into Windows. If your PC vendor includes an app to help with that, e.g. Dell Update or Lenovo Vantage, that's usually the easiest way to go. And it might also be appropriate to uninstall drivers/utilities that were only relevant to your old PC.
But if you're not quite that lucky, building Rescue Media on the target PC can help in the way you surmise, but you can also just download appropriate drivers for the new PC and copy them onto your Rescue Media flash drive. In that case though, you will need to have drivers that can be extracted to raw INF file format. EXE installers don't work in the Rescue environment, although many PC vendors now provide EXE installers that give you an option to extract their contents rather than installing them. But if that option isn't available or desirable, then if you need to temporarily install Reflect on the new PC, you'll have to remove your Reflect license on your current PC (under the Help menu), then install it on the new one to be able to create Rescue Media that includes ReDeploy, and THEN remove that license from the temporary Reflect installation on the new PC before you blow away its Windows environment with the image you'll be restoring.
As to your other question, yes that's the correct process. Restore the image and then run ReDeploy. No need to reboot beforehand. You may also need to run Fix Boot Problems, but you can also try just booting your PC first. If it doesn't work, you can always return to Rescue Media to run that, no need to rerun the restore.
Thanks for the response, I did as you suggested but I am running into issues. At the final step, I'm getting a BSOD with an "Inaccessible Boot Device" error.
First to recap, I made an image of the source laptop through Macrium Reflect. The Source PC's OS is Windows 10 and it has a M.2 SSD (Samsung Pm871a Mznln256hmhq-000h1). I also made an image of the Target PC's Windows 11 OS (the stock Windows 11 image that shipped with the laptop from Dell). The drive in the target PC is an NVMe drive (WDC SN810).
I transferred the Macrium Reflect license to the Target PC to create the Rescue Media and during the Rescue Media creation it detected several drivers and I selected all of them for inclusion. Unfortunately I did not make note of them but if necessary I can restore the original stock image to the target PC (i.e. Dell's stock WIndows 11 image) to make note of them. I'm not sure if it's an issue that I'm pulling drivers from a Windows 11 install for use on a Windows 10 PC. The Rescue Media was created successfully and I booted from it.
While booted from the Rescue Media, I applied the restore to the Target PC and then I applied the ReDeploy. While configuring the ReDeploy, I noticed that it wasn't detecting any drivers for the Target PC even though I created the Rescue Media on the Target PC. In particular, it only listed one device (as opposed to several as when the Rescue Media was created on the Target PC) and moreover it wasn't finding a driver for "Intel RST VMD Controller 467F". Therefore, I mounted/attached the image of the Target PC's Windows 11 OS and added it as a search path and then it found the "Intel RST VMD Controller 467F" driver. Nevertheless, only this one driver is listed--all of those other drivers that were detected during the Rescue Media creation on the Target PC are not listed. I'm not sure if this is a problem.
In addition, while configuring the ReDeploy I also selected the "Display boot drivers as they load" and "Enable boot logging" options. I applied the ReDeploy.
After the PC restarted, it did not display boot drivers as they loaded and I got a BSOD with the error "INACCESSIBLE BOOT DEVICE". I rebooted from the Rescue Media and applied the Fix Boot Problems, but still got the same error. In addition, on the Target drive I searched for the log file for the boot in \Windows\ntblog.txt (as indicated by the "Enable boot logging" option) but there was no such file created.
Should I try restoring the default Windows 11 installation that was originally on the Target PC back to the Target PC, recreate the Rescue Media on the Target PC and make note of all of the drivers it detects, and then redo the entire process but manually add all of the detected drivers during the ReDeploy? Or perhaps I should try a clean Windows 10 installation (as opposed to a Windows 11 install) on the Target PC and recreate the Rescue Media from there instead? Any help would be appreciated, thanks