How to clone/migrate O/S system disk sata ssd over too a new NVME M2 SSD without data loss
Ok, i have made a start, i have downloaded the acronisbootable media iso, and rufus ver 3.0, before they dropped vista support i think (vista &win7 are similar kernals or something like that ) so downloaded a older version to play it safe,
But i do have 1 question regarding creating the bootable media this way ,If have makedthe radio button, it was selected to MBR you have the choice of GPT or MBR should this be changed to GPT as i want the usb to boot in uefi mode certainly to recover the full system disk backup/ image .tib file onto the nvme, i also want to use it to create that backup , rather then instal ATI on my system disk, So GPT or leave as is MBR in rufus?
Dave,
Your wasting your time with this. Everything discussed to this point has been based on using WinPE as the host OS for the True Image bootable recovery media. The ISO that you downloaded is NOT WinPE. It is a Linux based variant of the True Image bootable media. The problem here is that if you proceed to use this media you will find that your NVMe drive will not be detected using it.
You need to use a WinPE based media to perform this task. To achieve that you will need to install True Image on your computer. In addition, you will also need to install the Win 10 ADK package to build a WinPE media. These are necessary pieces to the puzzle you have here. If you do not wish to do that then I have no confidence that you will achieve your goal.
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
1, or both of these in the link, i notice there is a win 7 pe version in the list, ?? does this s/w fully uninstall without problems ?
Ok I found some info on this on what i need to do excactly once i have installed the Windows ADK/AIK to add this to the ATI bootable media if i read this right if what this is achieves,
I resumably would then create a full system image /backup in the normal way and store that on what will be the new source disk,
I would then set the boot order so the usbstick boots 1st and restart booting into the usb with acronis containing the win pe that i created using acronis ?
https://kb.acronis.com/content/59184
So long as those features and options haven't changed since the 2017 version
Dave, I would recommend installing the Windows 10 ADK which works fine with Windows 7 for the purpose that you need it for. Once it is installed, then create the MVP Custom ATIPE version of the rescue media which uses the ADK and will allow you to inject any additional device drivers.
You may not need to change the boot order in the BIOS is your system provides you with a Boot override key, i.e. F12 for Dell, F9 for HP, other keys for different makes - this should allow you to select to boot from the USB rescue media in UEFI mode.
See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media which has some screen shots showing boot menu options you may see.
See KB 61632: Acronis True Image 2019: how to create bootable media - for the latest document on this topic using the Acronis Rescue Media Builder tool.
You do not store the backup image on the "what will be new source drive" You will not write anything to the NVMe drive yourself. The WinPE media you create will do all that is required for you.
Your backup image should be written to and stored on another drive. You probably have room for the backup file on another of your internal disk. I would recommend that you use a disk other than your current Win 7 disk to store the backup image file.
No, you miss understand me, I will need to make a full disk backup of my system disk , and that image will need to be stored somewhere, which will be the new unused 500gb 860 sata ssd which i will install , not the NVME is what i was meaning, rather than have to start moving data around, and creating partitions ect,
Btw i did try the Samsung migration tool, which although could see the nvme, failed ,hung at 99% verifying for over 3hrs, so i have uninstalled that , (they did they that my scenario should work) i guess they haven't a clue
Just a quick one do i need the Win PE ADD ON for the ADK as well or just the WIN10 ADK
Steve Smith wrote:Dave, I would recommend installing the Windows 10 ADK which works fine with Windows 7 for the purpose that you need it for. Once it is installed, then create the MVP Custom ATIPE version of the rescue media which uses the ADK and will allow you to inject any additional device drivers.
You may not need to change the boot order in the BIOS is your system provides you with a Boot override key, i.e. F12 for Dell, F9 for HP, other keys for different makes - this should allow you to select to boot from the USB rescue media in UEFI mode.
This Box is not a shop prebuilt system, i built it myself nearley 3 yrs ago, So no override keys here,
You just need the Win 10 1803 ADK. The add on is only for Win 10 version 1809.
Thanks for clearing up my misunderstanding..
When you get the WinPE built and your necessary drives installed, etc. start the PC and boot into your bios (F2 or Delete key). Go to the Advanced setup - Boot tab and insure that your WinPE media is selected to boot first in the boot order list. To insure UEFI boot look for UEFI in front of the name of your WinPE media. Of course UEFI must be enabled and Secure Boot disabled.
Example:
UEFI Sandisk cruzer or similar.
Once you have that set Save and Exit. The PC should boot into the WinPE at this point allowing you to perform the recovery.
No, Probs and thank's for your patients, i have d/loaded the ADK do i install as per pre selected by default as in ss, or do i need some of the other parts of it too 
Dave, looking at the size shown in your screen image above, you do not have the full ADK yet!
See forum topic: Important change for Advanced Acronis Media Builder starting with Windows 10 1809 - and the screen images shown there as posted by MVP Karl.
You only need the Deployment Tools for the panel you have shown, but you also need the separate WinPE components for the ADK which is over 3GB in size.
Steve Smith wrote:Dave, looking at the size shown in your screen image above, you do not have the full ADK yet!
See forum topic: Important change for Advanced Acronis Media Builder starting with Windows 10 1809 - and the screen images shown there as posted by MVP Karl.
You only need the Deployment Tools for the panel you have shown, but you also need the separate WinPE components for the ADK which is over 3GB in size.
Would this be the one?
Dave, see webpage: Download and install the Windows ADK - where it shows the 2 separate ADK components since Windows 10 -1809 version as per the image below:
So for the above, you need to download both parts but only install the Deployment Tools from the top download, and all the WinPE function from the lower download.
Alternatively, if you scroll down the page a little further, you will see links to download the older version of the Win 10 ADK as suggested by Enchantech.
Dave,
The link you PM to me I replied to. In that link under Other you will find the 1803 version which does require the add on
So which version is best to use 1803 or 09, or either of them ? just re readthe ms page and
Starting with Windows 10, version 1809, Windows Preinstallation Environment (PE) is released separately from the Assessment and Deployment Kit (ADK). To add Windows PE to your ADK installation, download the Windows PE Addon and run the included installer after installing the ADK., So any of them the earlier 1803 has it included?
Doesn't matter, the 1803 version includes the WinPE add on all In one package, one download one install.
Thanks for confirming this
Ok, i have downloaded and installed ATI 2019 and win10 adkand the PE addon , To create bootable recovery media on to the usb stick are there step by step instructions to do this ? also in ATI to make a full backup of the system disk do i select full pc back up option?
Use the "disk" option and select the appropriate drive. That will backup the entire drive as is. Full pc is similqr but can backup other unintended disks as well so thats whybi always choose just the disk that's intended.
Instructions are here...
So in my case i need to choose advanced then select win PE ? Another question i installed the win pe adk on to a different hdd than my system disk (ssd) saving writes will this be ok?
Also where does the MPV ATI PE builder come into this i thought it was part of ATI ?
I have Dloaded the mpv tool and here's a screen grab of what i see when i run it, what does this actually do, as ATI creates the back up, is this for the restore?
Yes, use that option for creating default Acronis media using ADK.
The MVP tool is extra that has a much more friendly end product with other fratures like file explorer and a web browser baked in. There is a link in the main application, but the KB article is at
https://kb.acronis.com/content/59335
And thecurrent (and signed version) of the MVP tool is on our Google Drive folder
https://drive.google.com/drive/folders/0B8uZDIFmupY7TE1QU2VoZ01ZaFE
This tool works best with the ADK. I think youll be ok with installing it elsewhere, but I generally recommwnd installing apps on the OS drive.
Also sorry for the typing... Using a phone at the moment and I'm all thumbs.
No probs, they need bigger keys,lol Right i'll make the back up , and then i'll need to know just how in steps how to create this recovery media using ATI MPV tool To i presume build the recovery image instead of using ATI to do that ?This should find the adk/pe files needed , or have i got that wrong?
Yes sir. Create the backup first. Always a sound idea as it's key for recovery. If/when possible always try to remove the original OS drive and restore to a new or different drive. Not required but helps limit the possibility of overwriting the original data which could be another failsafe (just in case).
The MVP tool is pretty straight forward. Download and extract it. Typically works best from the root of a drive or somewhere not in your user profile. It's standalone and doesn't need to be installed.
There are prompts along the way once it's started. Choose the ADK option and 64 bit. The rest is pick and choose as the prompts come up throughout the build. I recommend adding custom drivers because it includes IRST for NVMe and RAID by default when you do, but you can add others as well if you want. Other than IRST and possibly a unique NIC, winpe built with win 10 ADK works out of yhe box for almost anything these days. So adding extra drivere isn't all that necessary.
Bobbo_3C0X1 wrote:Yes sir. Create the backup first. Always a sound idea as it's key for recovery. If/when possible always try to remove the original OS drive and restore to a new or different drive. Not required but helps limit the possibility of overwriting the original data which could be another failsafe (just in case).
The MVP tool is pretty straight forward. Download and extract it. Typically works best from the root of a drive or somewhere not in your user profile. It's standalone and doesn't need to be installed.
There are prompts along the way once it's started. Choose the ADK option and 64 bit. The rest is pick and choose as the prompts come up throughout the build. I recommend adding custom drivers because it includes IRST for NVMe and RAID by default when you do, but you can add others as well if you want. Other than IRST and possibly a unique NIC, winpe built with win 10 ADK works out of yhe box for almost anything these days. So adding extra drivere isn't all that necessary.
Thank's, i'llbe putting the full disk backup onto a different ssd,(empty) and that will become the source disk for recovery, to the NVME SSD i have already installed the nvme driver to my system which is on another sata ssd,i also have the intel IRST installed on this o/s The samsung driver is contained in a installer , i realise that i can unpack it, but i have no clue which files are needed or used
The IRST driver from Intel works for the samsung drives in winpe just fine. Just build with the MVP tool and say yes to add custom drivers and they'll be added automatically.
Just to clarify as your note concerned me that you may have potential data loss. Don't store backup files on any drive you intend to use to migrate your OS to . An OS restore to the same drive where backup files are taken from would wipe them out. You shouldnt be allowed to restore to the same Drive the backup is on anyway, but just in case. Not worth the risk if you cant kive without that data.
No, I wasn't going to, copy or restore the back up to the same drive, I currently have 3 drives in my pc, the sddthat my os is on, and 2 mechancal drives , I am going to add a new SSD (sata) to write the back up, .tib file to, after i create the bootable recovery media onto a flash drive,
i will disconnect my current os drive, and the other mechanical drives, install the NVME drive which will be the target drive for the revovered O/S that boots in Uefi /gpt instead of MBR legacy ,
If the Intel RST and Samsung Nvme Drivers are already installed on my active o/s what i don't understand is why i would need to mess about installing them to this recovery media as well, not that i would know how to install them to this media RE samsung nvme controller driver ?
Dave,
You can unpack the Samsung driver files and point the MVP tool to them when prompted to add custom files. The tool will pick out the ones needed and add them to the media.
I know you said that you installed the IRST drivers to the OS. Just to double check, that this included the RAID drivers as well? If you can post a driver version number that would help.
the Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller is version 15.8.1.1007 from 2017
Ok, the 15 series drivers include the RAID drivers and a SCSI driver filter. Since these are installed in your system can you verify that Windows Device Manager now shows an entry for Storage Controllers rather than one for IDE ATA/ATAPI Controller?
This should be the case for you. The latest IRST driver in the 15.8 series driver is 15.8.2.1009 dated 9/15/2017. The corresponding OPROM mobo driver is 15.8.0.3109.
I am providing a link for you for this Windows driver. The link will take you to a download page where you can download the driver package in an rar file. Unpack it and point Device Manager to the unpack location to install.
dave wrote:
No, I wasn't going to, copy or restore the back up to the same drive, I currently have 3 drives in my pc, the sddthat my os is on, and 2 mechancal drives , I am going to add a new SSD (sata) to write the back up, .tib file to, after i create the bootable recovery media onto a flash drive,
i will disconnect my current os drive, and the other mechanical drives, install the NVME drive which will be the target drive for the revovered O/S that boots in Uefi /gpt instead of MBR legacy ,
If the Intel RST and Samsung Nvme Drivers are already installed on my active o/s what i don't understand is why i would need to mess about installing them to this recovery media as well, not that i would know how to install them to this media RE samsung nvme controller driver ?
Awesome.
Your want to include the drivers in recovery media so that it can detect your pcie NVMe drive for recovery. IRST drivers and NIC drivers are typically the ones people sometines still have trouble with in winpe. I still have to add my Killer Ethernet drivers even in win10pe.
IRST works fine in windows 10 winpe usually, but good ro ensure you have ones for your board. Of course you could try withoutwadding anything and hopefully it just works, but if not then you can rebuild the recovery media and slip in custom drivers as needed.
Enchantech wrote:Ok, the 15 series drivers include the RAID drivers and a SCSI driver filter. Since these are installed in your system can you verify that Windows Device Manager now shows an entry for Storage Controllers rather than one for IDE ATA/ATAPI Controller?
This should be the case for you. The latest IRST driver in the 15.8 series driver is 15.8.2.1009 dated 9/15/2017. The corresponding OPROM mobo driver is 15.8.0.3109.
I am providing a link for you for this Windows driver. The link will take you to a download page where you can download the driver package in an rar file. Unpack it and point Device Manager to the unpack location to install.
A storage controller for the Samsung NVME drive appeared when it was installed below the asMedia controller
Ok,havedone a disk back up of my system disk ( Samsung SSD 850 PRO 256GB_full_b1_s1_v1.tib) Won't the newer driver cause a conflict with the older one already installed on my os RE:( Intel RST driver ) ?
As for the internet i only have the standard lan connection, So shouldn't have issues with that, just this Intel rst and the samsung nvme i think
The WimPE media that you are going to create needs to be thought of as a standalone OS environment that hosts the True Image application. What the drivers you are adding to WinPE will do is provide the support for the WiinPE environment for your NVMe drive just like the ones installed in your current Win 7 OS install on your 850 PRO SSD. So when the WinPE environment is booted it will detect and work with your NVMe drive just like your Win 7 installation does. The simple answer to your question is No, the drivers will not conflict with each other.
I would not worry at all about your NIC, you will not be needing it in this scenario.
Ok thank you, for all your help so far, all of you who have been helping me, I'm grateful to you for your time, and patience, I have just installed an EK nvme cooler to the drive, as yesterday when i benchmarked it the max temp hit 71 c and according to the specs on Samsungs site the operating temp is what ever the lower end is to 70 c so entering thermal throttling territory maybe,
another thing i noticed with that magician s/w you can only have rapid mode cache on 1 SATA SSD , also once my current os SSD is removed as that will be the back up drive, if i at a later point wanted to back up the nvme to that the SATA SSD would it be a straight forwards back up or clone a restore as it would be the same boot uefi to uefi (once it was formatted of course)
I may build that recovery bootable media tonight, but i think I'll leave the actually reinstall of the nvme and recovery operation till tomorrow as i'm feeling somewhat tired,
If you intend to remove your current SSD and not re-purpose it for use say as a secondary user data drive in your PC but rather store it in a safe place to serve as a sort of emergency replacement drive if need be then that will be fine.
Your only obstacle to using the drive as a boot drive is the boot mode enabled in the bios. if you need for example to use that drive because of your NVMe drive failing you would simply pull the NVMe drive, install the SSD, disable UEFI boot which by default should enable Legacy/MBR boot, change SATA boot mode from RAID back to AHCI, Save and Exit to reboot to the SSD. If you try that and get an Inaccessible boot device error then your problem is in the boot order in the bios. Changing the boot order to the SSD being first in order should clear the error and boot the PC.
If you wish to make your current SSD UEFI boot ready by using the NVMe drive as a source image I would suggest using the Clone tool function of True Image from the WinPE media to clone the working Win 7 install from the NVMe drive to the SSD. If you do that a word of caution, when you setup the clone process at the end of the setup you will have the option to shutdown the computer when finished. Make sure you select that option and once the computer shuts down, remove the SSD from the computer before you start up the PC again. This will avoid having what is called a drive signature crash which can be a real BIG problem.
Ok, thanks for that, Just running though things a little ie building the PE image is it an image? we have disgusdadding the nvme driver and the intel rst driver, one thing just occured to me , although i'm not sure if this will affect anything or not,
In case you didn't know, win7 has not native support for usb 3 so installing win 7 on systems with z170 and above chipsets can be problematic in particluar if installing win7 iso from USB stick , even installing it via a sata odd, is problematic in that there is only one ps2 port So no mouse available during install (even usb2) iirc ,
the question is will i need to also add the usb 3 drivers to the PE or not, as we aren't actually re installing win 7 ?
No you will not need drivers for USB as your Windows 7 Image file you are restoring will already have those. All driver files currently installed in your Win 7 system will be carried over in the restore process to the NVMe drive as True Image copies those when it creates the backup image file.
WinPE is not an image file. It is a number of files including boot files written to a storage device (USB thumb drive most popular) that when attached to a computer can boot the computer and run like a typical operating system would.
Think of it this way, you boot the WinPE OS so that you can use True Image to unpack your backup image .tib file and copy it to your target (NVMe) drive. When finished you shutdown the computer, remove the WinPE drive and boot the NVMe drive with the newly copied files of your current operating system and all installed applications.
Ok, Has the issue with the acronis anti ransomware causing issues been fixed or is it best to disable this when building the pe os,?
Enchantech wrote:If you intend to remove your current SSD and not re-purpose it for use say as a secondary user data drive in your PC but rather store it in a safe place to serve as a sort of emergency replacement drive if need be then that will be fine.
Your only obstacle to using the drive as a boot drive is the boot mode enabled in the bios. if you need for example to use that drive because of your NVMe drive failing you would simply pull the NVMe drive, install the SSD, disable UEFI boot which by default should enable Legacy/MBR boot, change SATA boot mode from RAID back to AHCI, Save and Exit to reboot to the SSD. If you try that and get an Inaccessible boot device error then your problem is in the boot order in the bios. Changing the boot order to the SSD being first in order should clear the error and boot the PC.
If you wish to make your current SSD UEFI boot ready by using the NVMe drive as a source image I would suggest using the Clone tool function of True Image from the WinPE media to clone the working Win 7 install from the NVMe drive to the SSD. If you do that a word of caution, when you setup the clone process at the end of the setup you will have the option to shutdown the computer when finished. Make sure you select that option and once the computer shuts down, remove the SSD from the computer before you start up the PC again. This will avoid having what is called a drive signature crash which can be a real BIG problem.
What i may do to ensure i have a working back up that is Uefi, bootable, is after i have a bootable working installation of win7 on the NVME, is wipe the image.tib file off it and either 1, clone using the nvme as a source to that empty 860 ssd,
Then after testing (with the nvme removed ) that it boots ok, then clone from 860 to 850pro , or write a full disk image if it will fit , if not clean /format the disk and clone to it i suppose the advantage to cloning is you know 100% you have a working back up should the os drive fail , ect where as you don't really know this with a image of the disk, although i may at some point buy a external ssd,that utilises the 3.1 usb on my mobo for faster transfare speeds an store back ups on that as image files, or use something like this https://www.amazon.co.uk/General-Drive-HDD-Adapter-CADDY/dp/B00F3QFKNS, i belive there is a setting in my bios for hot plugging drives, but not sure if having an installed nvme affects this or not , but it will fit in my case i have 1 spare 5.5 inch bay
As long as you run the MVP tool as Admin you should not have issue with AAP. If you do for some reason just temporarily disable AAP.
The drive caddy you link to is fine. I am not a fan of hot swap or plug as you call it. I do not see the need in a consumer devise for do it. This is best for servers that need to be on 24/7.
The advantage of cloning a disk is that you get an exact copy of the entire disk. As long as you choose Porportional mode to run the clone it will expand partitions accordingly as well. If you have an image file to restore takes a bit longer but you end up with a working disk. If you want to have a disk ready to go to just pop in and run a clone is what you want.
Again, DO NOT run the machine with the cloned drive and the original installed, it is a recipe for disaster.
Enchantech wrote:As long as you run the MVP tool as Admin you should not have issue with AAP. If you do for some reason just temporarily disable AAP.
The drive caddy you link to is fine. I am not a fan of hot swap or plug as you call it. I do not see the need in a consumer devise for do it. This is best for servers that need to be on 24/7.
The advantage of cloning a disk is that you get an exact copy of the entire disk. As long as you choose Porportional mode to run the clone it will expand partitions accordingly as well. If you have an image file to restore takes a bit longer but you end up with a working disk. If you want to have a disk ready to go to just pop in and run a clone is what you want.
Again, DO NOT run the machine with the cloned drive and the original installed, it is a recipe for disaster.
Thank's for that vital info about running the system with a clone, Is this proportional mode found in ATI or in the MVP tool? I'm guessing the MVP pe tool ,as ATI only has two choices auto or manual
ATI, auto = proportional. The same DO NOT warning stands for recovered backup images to a disk as well.
Ok, So once i have recovered the image that is on the 860 (new sata ssd) to the NVME ssd and set the bios to boot in uefi mode the original ssd which i'm using now with Win 7 on it which is booting in legacy mbr bios mode shouldn't conflict ?as it won't be seen by the boot loader anymore, but if it's best to remove it, i shall do this prior to recovering the saved image on the 860
Then once that is completed and it's working as it should ,. could either clone that to the 860 or the 850 the os is currently on , remembering to power off after the cloning has finnished and remove the source, in order to verify the cloned image boots ok before i remove it and store as a back up disk, and then re install the nvme, the only other thing is i currenlty have my games installed to 1 of my mechancical hdd's so will be moving those folders onto the 860 , i'm not sure about changing the drive letter, as i can always make new shortcuts to the new MVME drive from the 860 regardless of the drive letter,
Another thing i did notice after running the Samsung migration tool my oldest sata2 disk somehow changed from basic to dymamic,i certainly didn't change,it strange why the samsung migration tool would cause that when that disk wasn't the source or destination disk
Dave,
The drivers are needed for booting on specific hardware and aren't embedded for PCIE NVME on Windows 7 as it's not considered by Microsoft is a "modern" OS.
Yes, you are copying the OS from one system to the next, but the new system motherboard and bios have to interact with the Operating System as it does a hardware compatibility and driver check during POST. If the appropriate drivers are not already in the OS when it's time to boot on the new hardware, Windows 7 typically ends up with a driver compatibility error blue screen.
Now, why it's saying the driver is bad/corrupt from the restored backup image (copy of the OS to new machine), I'm not sure - other than the existing driver that is installed in the OS (on the old and working machine) is not compatible with the hardware/motherboard on the new system.
Typically, with Windows 8, 8.1 and 10, drivers are not longer much of an issue (especially Windows 10). But Windows 7, still suffers from needing more specific drivers that aren't in the default installation media like they are with Windows 10.
I think the hope is that by running the hotfix in the current OS, it will be preparing it for the new hardware so that it no longer gives you this bad driver error.
---------------------------
If all else fails, you can try running Universal Restore (separate Acronis tool) which is meant to generalize all drivers on the system and allow Windows to boot (in most cases). However, as PCI-E is not part of Windows 7, you'd have to also supply the correct PCI-NVE driver package into the OS after running UR and hope that it no longer shows as corrupted. If it does, awesome, but then be prepared to update all the drivers for your graphics card and other devices again.
Bobbo_3C0X1 wrote:Dave,
The drivers are needed for booting on specific hardware and aren't embedded for PCIE NVME on Windows 7 as it's not considered by Microsoft is a "modern" OS.
Yes, you are copying the OS from one system to the next, but the new system motherboard and bios have to interact with the Operating System as it does a hardware compatibility and driver check during POST. If the appropriate drivers are not already in the OS when it's time to boot on the new hardware, Windows 7 typically ends up with a driver compatibility error blue screen.
Now, why it's saying the driver is bad/corrupt from the restored backup image (copy of the OS to new machine), I'm not sure - other than the existing driver that is installed in the OS (on the old and working machine) is not compatible with the hardware/motherboard on the new system.
Typically, with Windows 8, 8.1 and 10, drivers are not longer much of an issue (especially Windows 10). But Windows 7, still suffers from needing more specific drivers that aren't in the default installation media like they are with Windows 10.
I think the hope is that by running the hotfix in the current OS, it will be preparing it for the new hardware so that it no longer gives you this bad driver error.
---------------------------
If all else fails, you can try running Universal Restore (separate Acronis tool) which is meant to generalize all drivers on the system and allow Windows to boot (in most cases). However, as PCI-E is not part of Windows 7, you'd have to also supply the correct PCI-NVE driver package into the OS after running UR and hope that it no longer shows as corrupted. If it does, awesome, but then be prepared to update all the drivers for your graphics card and other devices again.
Some of this is confusing, re the part about copying the os to another system,?? same system, and hardware, with the exception of the NVME ssd i only have the 1 PC i don't understand what you mean ?
My bad - going back and forth on the forums. Was thinking this one was going to new hardware, not just a new drive into the same hardware.
Regardless, hopefully the hotfix helps resolve the driver issue when it tries to boot on the new drive.
Sorry, also... since the thread is so long and couldn't find this...are/were you able install the new PCIE NVME drive into the system while booted to the current drive's OS? If so, I'd use disk manager to initialize the PCIE drive and format it as GPT already. Then, I'd apply the hotfix and reboot back into the OS once for good measure.
After that, take your full "disk" backup from the Acronis application in Windows (which will ensure there is no encryption at play).
Can't hurt to do all this and might help get pack this corrupted driver hiccup. I've never seen this before and I tested moving from an SSD to a PCIE NVME drive a ton back in 2016, 2017 and 2018. Most with Windows 10 though as I started fresh with Windows 10 back when it was a free upgrade from Microsoft.
Bobbo_3C0X1 wrote:My bad - going back and forth on the forums. Was thinking this one was going to new hardware, not just a new drive into the same hardware.
Regardless, hopefully the hotfix helps resolve the driver issue when it tries to boot on the new drive.
Sorry, also... since the thread is so long and couldn't find this...are/were you able install the new PCIE NVME drive into the system while booted to the current drive's OS? If so, I'd use disk manager to initialize the PCIE drive and format it as GPT already. Then, I'd apply the hotfix and reboot back into the OS once for good measure.
After that, take your full "disk" backup from the Acronis application in Windows (which will ensure there is no encryption at play).
Can't hurt to do all this and might help get pack this corrupted driver hiccup. I've never seen this before and I tested moving from an SSD to a PCIE NVME drive a ton back in 2016, 2017 and 2018. Most with Windows 10 though as I started fresh with Windows 10 back when it was a free upgrade from Microsoft.
Ok, no worries, Yes i installed the NVME SSD into the slot, on booting win7 gave an error about it not being installed correctly, this was without the Samsung nvme driver being installed on the system disk or the hotfix from MS, as the Samsung driver won't install if it can't detect the NVME drive, once i installed the driver and restarted no errors,
i formatted it and gave it a drive letter, ran a few benchmarks and it performed within spec's temp shot up to 71c so i purchased an EK nvme cooler and attached that to it,
i still haven't put it back in the slot yet, as i will give the machine a cleaning (dust) with the electric blower i have, and then dig out the screw that secures the nvme, from the mobo box as it now weighs quite a bot more than it did on its own with this heatsink on it,
So i'm at the stage of building the PE bootable recovery media and copying it to a flash/thumb drive, then once that's done, instal the nvme drive (destination disk) and remove or disconnect the current os boot SSD, i may also disconnect the other data HDD to, then I'll try recovering the full disk backup image that is on a new 860 (source) data SSD
Hopefully, i have installed the correct PE software i have the win 10 adk and something called windows system image manager in the start menu i think installed the correct part of the PE the default choice of the 2 available choices, the other choice made a reference about deploying images to other machines etc
Dave,
Your plan sounds good. Your WinPE should build fine as it sounds like you have the correct components of the ADK installed. Please take the time to read the readme file for the MVP tool, you can get that in the same place you got the tool download, it will help you understand the build process and you chould have it handy during the building of the media for reference.
I would encourage you to disconnect all unneeded drives from your machine when you perform this process of restoring the backup image to your NVMe drive. Way less to go wrong if you do. In addition, I have seen some strange things happen when extra drives are attached to a computer when restoring or even during Windows installs. It pays dividends to do the extra steps.