Did some research. Apparently that N22 may be twitchy about what m.2 drives it will work with. The BIOS limits the maximum m.2 drive size to 256gb. Their forums and documentation also list only these drives as being compatible:
128GB LiteonCV3-8D128 M.2 part number 2280128G
128GB Samsung PM871a
5SD0J21066 Liteon CV1-8B128
5SD0H43484 HY HFS128G39MND-3310A M.2
5SD0L07408 Hynix HFS128G39TND-N210A
5SD0H00094 Samsung MZNLN128HCGR M.2
16200609 SS MZNTE128HMGR 128G
5SD0H29265 HY HFS128G38MNB-2200A M.2
5SD0H12051 Ramaxel RTHMB128VBM4EWDL
5SD0L14643 SS MZNTY128HDHP-000L2 128G
5SD0F65755 Liteon L8T-128L9G 128GB M.2
16200483 Liteon LGT-128M6G M.2
16200587 Samsung MZNTD128HAGM 128G
5SD0M61137 Ramxel S121 128GB M.2 2280 SSD
5SD0L82503 RTITF128PCA1MADL 128G M.2 SSD
Interesting that those drives listed are all 128 GB, yet Windows Disk Management reports this Samsung 256 GB drive is healthy, reports full capacity, and copy / paste operations to / from it (or opening files on it) work fine.
I’m almost tempted to copy / paste the entire contents of the C: drive over to the M.2 drive just to see if any errors crop up, even though I know the OS won’t boot correctly.
But, if I’m gonna do THAT, I might as well see if I can extract the Windows product key and then try to download & install a new copy of the OS from Microsoft onmto the M.2 drive.
Thanks for the info.!
So, if you had a Micro SD card with the Image file on it that Macrium Reflect can get to and browse it, then you could try again and ENLARGE THE C: Volume at the same time (else you have the same problem you have with the eMMC).
But to actually work, you have to be able to get into the BIOS first anyway. Try holding down the NOVO key or FN+F2 Solid and powering up. Then be ready to change the BIOS to point to the M.2 first after this whole thing.
I'm also not sure what windows will do if it sees the old OS on the eMMC as I physically remove the old drive in the process (but yours is soldiered in). But one step at a time...