

I could install a SATA M2 drive, if it doesn't work, but don't think there would be much of a speed advantage over the internal SSD drive.

I have a fresh NVME 512GB installed along with the SSD drive and will try a fresh install on the NVME to see if it will boot and function normally. He claims he's had issues with NVME drives not working in HP laptops, even with a fresh Windows install He installed a M2 SATA, rather than NVME.

Looked for more info on just doing a fresh install on an M2 drive and came across this video. Installed in place of the spinning drive and it booted flawlessly. Decided to forgo the NVME drive and try the internal SATA Samsung 1TB SSD that I'd been cloning periodically for over a year. Trying to run System Restore resulted in a never ending wait at the "Please Wait Here" screen. Ran System Diagnostics and things looked fine. The PC became locked in a Blue Screen loop trying to auto repair from a Kmode not handled exception. Huffer, have you successfully tried any UEFI cloning? I suspect my next step is to contact Macrium Reflect support, unless I get a reply from this forum from someone with a similar experience. This appears to be what is happening with my machine, only with 2 different boot "types". No solution was suggested, only contact MR support, who had not responded in the thread. Looking at Macrium Reflects forum, I found folks having an issue cloning from UEFI to UEFI drives, where despite changing the boot order, the machine would boot to the previous UEFI boot drive. It appears to be using the original BIOS legacy boot sector(which of course is cloned to the new UEFI drive). The SSD, however, was shown as the C:drive on both Explorer and Disk Manager. On a later clone and boot try, I removed the HD and it would not boot. When I changed the boot order to point to the cloned SSD, and booted, it still booted to the original HD (the HD spinning was audible and the boot was at the HD speed(slow)). Forgive me, if I misstate terms, I'm 12 years removed from being a SW engineer and things have definitely moved on. The SSD is UEFI and would boot based on that "protocol". My original 1TB spiinning drive is SATA and would use legacy BIOS Windows boot. Thanks for the reply, that's exactly what the video suggests, and what I did. Huffer replied: You have to manually move partitions other than the big C:\ drive partition at their original size and then resize the big partition to whatever is left over. Business PCs, Workstations and Point of Sale Systems.

Printer Wireless, Networking & Internet.DesignJet, Large Format Printers & Digital Press.Printing Errors or Lights & Stuck Print Jobs.Notebook Hardware and Upgrade Questions.
