Inaccessible boot device on Optiplex 3050 after restoring image to new NVMe M.2 SSD

In my own experience Acronis is not reliable when making clone images.  I suggest using a product such as Clonezilla instead.

https://clonezilla.org/downloads.php

Note that Clonezilla is easier to use on a BIOS machine.  It will boot UEFI but only one version can be used -- the "AMD64 (X86-64) version (either Debian-based or Ubuntu-based) of Clonezilla live."

And don't forget to change the default boot device to the SSD.

Storage Controller driver missing ?

I will check with Dell.  I have seen some systems that need the NVMe driver installed.  Forgot about that.
As far as Acronis goes, have been using them for several years and the most reliable software on the market.  Not every customer runs them, but we have excellent success rate.  Just trying to avoid a support fee for the call to them.  I think Andrew probably is probably right on this one.

what is happening is that windows boot manager is trying to load from the disk guid of the older drive. boot from recovery media, go into repair options command prompt and run
bcdboot x:\windows (replace x with the drive letter of the current windows installation (the nvme drive)  It could be any drive letter use diskpart and  list volume to see what drive letter 

neither of those fixed things.

if you can access the drive from recovery media/install disk then it is not a driver problem. The NVME driver will just speed things up.
you may not have imaged over the boot block  so from recovery media cmd prompt

bootrec.exe /fixmbr 

Select allOpen in new window

will fix it.

now it fails with error 0xc0000000e

it's not a bsod error screen.  never seen this one before.

if it's not bsod - what is it then?
anyway, i suggest to repair the original installation first - then move to the NVMe drive
you can run chkdsk

also did youimage the whole drive?  and were there other drives in the system?  one may hold the boot partition

the original HDD makes a total image of all partitions.  No other drives connected.  Then restore process shrinks the data partition since the ssd is smaller,  but leaves the others the same.  I will verify again the sizes.  No other drives are connected during restore, just  the NVMe.  The process completes successfully.   we have close a hundred
 clients using this software and no problems.  however this is the first one who has attempted restoring to an NVMe drive.

The process completes successfully.

it didn't complete the process successfully if your computer does not boot.

however this is the first one who has attempted restoring to an NVMe drive.

So what does that tell you?

NVMe Storage Controller access is different from SATA.

Have you restored SATA (M.2 SATA ) to a machine with NVMe!

This is known as restore to dissimilar hardware, as the original "image/computer does not have an NVMe driver installed" in will BSOD with a Stop 0x7B - Inaccessible Boot Drive. Because initial BOOT is handled by BIOS until Kernel is loaded which then needs to load a driver to continue (the NVMe driver).

Do you have the Acronis option with Restore to Dissimilar hardware, this used to be a separately licensed option.

in this option Acronis allows you to add a driver for Storage Controller.

OR does Acronis allow you to create a recovery CDROM/IMAGE which should use this driver and perform a restore to bare metal.

If all you have done is a CLONE from A to B (different hardware) <--- this will not work.

yes using dissimilar hardware restore.  

the completed successfully is only the response from the restore.  vs restore failed, like when to many bad problems in the backup.

I am running chkdsk on the original drive and then will run a backup again.

no specific driver was found for nvme only.

plugged in the old hdd to my system to run chkdsk and found it is encrypted with bit locker but suspended.  I will work on the original a bit and update.  please keep the ideas rolling in.

I will also reinstall it last step into the original system and make sure they have bios, drivers, and so updated like they said was done.

if you want to give another method a test ???

I'll let you know how...

it's also odd, because Windows 10, you can move OS around different platforms, and most of the time, plug and play, detect new devices and work.

I am assuming things were good before.  I come into the picture, remove the HDD and install the NVMe.  Boot to DVD Acronis media to begin the restore image, and all seemed good.  I suspect something is wrong with the original.  Everyone has been great help with their thoughts.  What other clone software do you suggest?  Not a fan of free software for this in the past.  Usually more trouble and little success.  But if my second attempt fails, I will try option B.

UPDATE:  I have not seen the HDD boot the computer.  The computer was off when I arrived, and I pulled the drive.  I have the drive in my possession, and ran CHKDSK on it from another computer to also run diagnostics.  It passes, but upon connecting to the computer (with NVMe removed)... Inaccessible boot device!

I think my client left something out of the story.  Grrrr

you best update ALL the drivers before upgrading from : https://www.dell.com/support/home/en-us/product-support/product/optiplex-3050-desktop/drivers 

The backups run full backups every night.  The user is responsible for their own backups.  No one had complained about the computer ever.  So they said they were installing all driver and OS updates that day before the backups ran.  I can see the windows old folder from the upgrade, and they said they did not restart after that.  They shut the computer down for me before arrival to go straight to installing ssd.  To their knowledge nothing was wrong.    They say the computer had been running slow, and that is why they wanted the upgrade.  The drive now fails diagnostics, so we know the root cause now.   I have already installed the OS clean, restored data and updated the BIOS.  which means they may not have installed new drivers.  I only have myself to blame for time lost, as I took their word.

Thanks for all the great help.  Sorry it turned out to be a totally different problem.  Possibly the OS update broke something.  Not going to attempt to fix that.