As far as allocating the unused portion of the new disk - I'm having trouble with that part - but will read some more to make sure I'm doing it correctly. I installed the new drive in my MB M2 slot and then launched windows and. The current drive is a corsair 250G SDD and the newer drive is a Western Digital 1TB SN750 NVMe - WDS100T3X0C. Hello there, first time on forum and first time that I've transfered my win10 from my current SSD drive to a larger SSD. I will follow your advice above and make a rerun the clone and read the documentation carefully. My cloned drive will not boot windows 10.
After completing that, I tried to boot from the new windows 10 volume but it still doesn't work. BTW, I created a rescue media and chose the option "Windows Boot Menu" restarted and ran the Fit boot program at startup. I'd recommend disconnecting the original disk before running those and when first attempting to boot from the new disk, even if you want to reconnect it to use it for another purpose later. Same goes for the Fix Boot Problems wizard. And if you've moving from SATA to NVMe or vice versa, you might have to run ReDeploy afterward, which can be accomplished from Rescue Media.
#Create boot partition on cloned drive how to
See Steps 4 and 5 of this page from Macrium's documentation covering how to clone a disk for how to stage that type of restore. The fact that you have a Recovery partition between that partition and your unallocated space will make it harder to do that after the fact. Biasotti Unless you plan to use that 700GB+ of unallocated space to create one or more new partitions, you should rerun the clone and this time stage it in a way that causes that space to be allocated to the Windows partition.
0 kommentar(er)
