Windows 10 fails to boot after HDD clone to SSD
I have been trying to migrate a laptop from a HDD to an SSD. I initially cloned the drive with the latest version of TODO Backup and then tried with Macrium Reflect. Both have the same problem. The drive clones fine and all the files appear to be present, but Windows 10 won't boot.
I have booted from a recovery disk, loaded a command prompt and run:
bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot
bootsect /nt60 SYS
It still doesn't boot. If I load the Windows 10 recovery disk and boot from the CD I can then select to load Windows it will load. Likewise, if I select reboot rather than shutdown, the machine loads.
This is how the SSD drive looks in drive manager:
When trying to start the system after shutdown, it permanently sits on a black screen with a flash _
.
The partitioning on the source disk is MBR. I am cloning to an Integral P Series 2.5 inch Solid State Drive (120 GB, 4 SSD, SATA III Drive).
boot windows-10 bootloader
|
show 2 more comments
I have been trying to migrate a laptop from a HDD to an SSD. I initially cloned the drive with the latest version of TODO Backup and then tried with Macrium Reflect. Both have the same problem. The drive clones fine and all the files appear to be present, but Windows 10 won't boot.
I have booted from a recovery disk, loaded a command prompt and run:
bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot
bootsect /nt60 SYS
It still doesn't boot. If I load the Windows 10 recovery disk and boot from the CD I can then select to load Windows it will load. Likewise, if I select reboot rather than shutdown, the machine loads.
This is how the SSD drive looks in drive manager:
When trying to start the system after shutdown, it permanently sits on a black screen with a flash _
.
The partitioning on the source disk is MBR. I am cloning to an Integral P Series 2.5 inch Solid State Drive (120 GB, 4 SSD, SATA III Drive).
boot windows-10 bootloader
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
2
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31
|
show 2 more comments
I have been trying to migrate a laptop from a HDD to an SSD. I initially cloned the drive with the latest version of TODO Backup and then tried with Macrium Reflect. Both have the same problem. The drive clones fine and all the files appear to be present, but Windows 10 won't boot.
I have booted from a recovery disk, loaded a command prompt and run:
bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot
bootsect /nt60 SYS
It still doesn't boot. If I load the Windows 10 recovery disk and boot from the CD I can then select to load Windows it will load. Likewise, if I select reboot rather than shutdown, the machine loads.
This is how the SSD drive looks in drive manager:
When trying to start the system after shutdown, it permanently sits on a black screen with a flash _
.
The partitioning on the source disk is MBR. I am cloning to an Integral P Series 2.5 inch Solid State Drive (120 GB, 4 SSD, SATA III Drive).
boot windows-10 bootloader
I have been trying to migrate a laptop from a HDD to an SSD. I initially cloned the drive with the latest version of TODO Backup and then tried with Macrium Reflect. Both have the same problem. The drive clones fine and all the files appear to be present, but Windows 10 won't boot.
I have booted from a recovery disk, loaded a command prompt and run:
bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot
bootsect /nt60 SYS
It still doesn't boot. If I load the Windows 10 recovery disk and boot from the CD I can then select to load Windows it will load. Likewise, if I select reboot rather than shutdown, the machine loads.
This is how the SSD drive looks in drive manager:
When trying to start the system after shutdown, it permanently sits on a black screen with a flash _
.
The partitioning on the source disk is MBR. I am cloning to an Integral P Series 2.5 inch Solid State Drive (120 GB, 4 SSD, SATA III Drive).
boot windows-10 bootloader
boot windows-10 bootloader
edited Jun 27 '16 at 8:57
psych
asked Jun 24 '16 at 21:55
psychpsych
71114
71114
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
2
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31
|
show 2 more comments
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
2
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
2
2
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31
|
show 2 more comments
7 Answers
7
active
oldest
votes
Since you have a way of booting into Windows on the SSD, you can do a
Repair install of Windows 10 by performing an in-place upgrade without
losing anything.
You should first verify the partition alignment as described here.
add a comment |
The solution that worked at first try for me:
Windows 10
Fix Error After Cloning HDD SSD - Error in file winload.efi
With Windows 10 installation/recovery media open the command prompt in advanced tools
Diskpart
list volume (take note of boot partition volume and windows partition letter)
select volume X (X partition responsible for booting the system, hidden partition in fat32)
assign letter w (to be able to recover the boot files)
exit (exit diskpart)
bcdboot X:Windows /s w: /f UEFI (X partition letter that contains the Windows folder)
reeboot system (select the new boot option if more than one)
msconfig (Boot - delete the Windows options and leave only the c:Windows option)
Hope this helps many of you!
add a comment |
I think there is some problem with boot files or boot order.
The first thing you can do is disable fast startup by going to power options.
As fast startup uses a kind of hibernation techniques.
If it doesn't work perform an in-place upgrade without loosing your data. This will create new boot files and settings.
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
add a comment |
I struggle with similar problem with Windows 8.1.
When cloning from HDD to SSD, partitions serial and GUID kept intact.
But I not want to remove original HDD from system. So I needed to change GUID (in GPT for FAT EFI partition) and remove windows system partition from original HDD after cloning and before boot recovery.
When partition ID is non unique windows work strange, for example PE recovery unable to detect both HDD and SSD.
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
add a comment |
I had this same problem, just create windows installation usb drive from official site, boot up from installation usb, then go to troubleshooting, start CMD there and copy all files (and folders) that start with boot* and efi* from installation usb to root directory of cloned SSD drive, after doing that my cloned SSD was able to boot. Also check your boot settings in bios.
add a comment |
I ran into this same issue cloning my OS drive to a new SSD and was able to resolve it.
I noticed I had two Windows Boot Manager listed that pointed to the original drive.
1: I downloaded BootIce v1.3.4 by Pualy.
2: I went to the UEFI tab>> Edit boot entries button
3: There were two Windows Boot Manger listed in the listbox on the left, they both pointed to the same hard drive.
4: I selected one of them and changed it to point to my new SSD>> Click Save current boot entry button.
5: When I rebooted and went into the BIOS i was able to change the boot priority to the Windows Boot Manager of the new drive.
Success! I am now typing this from the Windows 10 loaded from the new SSD.
I plan on formatting the old one for secondary storage once I feel comfortable this is stable.
add a comment |
just met the same problem, actually a small mistake on 2nd clone of 2nd new laptop.
1st laptop clone, connect alone and boot up ok, the default hard disk connect on 2nd boot and formatted without problem.
But on 2nd laptop clone, connect newly clone SSD and original hard disk still with win10 in it, although choose boot with SSD, then wipe the hard disk OS, next time failed.
Solution: use Macrium Reflect bootable disc, go to restore > fix Windows Boot problem, it auto fix the boot manager.
Remind next time after clone, boot the cloned disk alone without original source disk, connect after 1st boot.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1093305%2fwindows-10-fails-to-boot-after-hdd-clone-to-ssd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since you have a way of booting into Windows on the SSD, you can do a
Repair install of Windows 10 by performing an in-place upgrade without
losing anything.
You should first verify the partition alignment as described here.
add a comment |
Since you have a way of booting into Windows on the SSD, you can do a
Repair install of Windows 10 by performing an in-place upgrade without
losing anything.
You should first verify the partition alignment as described here.
add a comment |
Since you have a way of booting into Windows on the SSD, you can do a
Repair install of Windows 10 by performing an in-place upgrade without
losing anything.
You should first verify the partition alignment as described here.
Since you have a way of booting into Windows on the SSD, you can do a
Repair install of Windows 10 by performing an in-place upgrade without
losing anything.
You should first verify the partition alignment as described here.
answered Jun 29 '16 at 10:56
harrymcharrymc
254k14265565
254k14265565
add a comment |
add a comment |
The solution that worked at first try for me:
Windows 10
Fix Error After Cloning HDD SSD - Error in file winload.efi
With Windows 10 installation/recovery media open the command prompt in advanced tools
Diskpart
list volume (take note of boot partition volume and windows partition letter)
select volume X (X partition responsible for booting the system, hidden partition in fat32)
assign letter w (to be able to recover the boot files)
exit (exit diskpart)
bcdboot X:Windows /s w: /f UEFI (X partition letter that contains the Windows folder)
reeboot system (select the new boot option if more than one)
msconfig (Boot - delete the Windows options and leave only the c:Windows option)
Hope this helps many of you!
add a comment |
The solution that worked at first try for me:
Windows 10
Fix Error After Cloning HDD SSD - Error in file winload.efi
With Windows 10 installation/recovery media open the command prompt in advanced tools
Diskpart
list volume (take note of boot partition volume and windows partition letter)
select volume X (X partition responsible for booting the system, hidden partition in fat32)
assign letter w (to be able to recover the boot files)
exit (exit diskpart)
bcdboot X:Windows /s w: /f UEFI (X partition letter that contains the Windows folder)
reeboot system (select the new boot option if more than one)
msconfig (Boot - delete the Windows options and leave only the c:Windows option)
Hope this helps many of you!
add a comment |
The solution that worked at first try for me:
Windows 10
Fix Error After Cloning HDD SSD - Error in file winload.efi
With Windows 10 installation/recovery media open the command prompt in advanced tools
Diskpart
list volume (take note of boot partition volume and windows partition letter)
select volume X (X partition responsible for booting the system, hidden partition in fat32)
assign letter w (to be able to recover the boot files)
exit (exit diskpart)
bcdboot X:Windows /s w: /f UEFI (X partition letter that contains the Windows folder)
reeboot system (select the new boot option if more than one)
msconfig (Boot - delete the Windows options and leave only the c:Windows option)
Hope this helps many of you!
The solution that worked at first try for me:
Windows 10
Fix Error After Cloning HDD SSD - Error in file winload.efi
With Windows 10 installation/recovery media open the command prompt in advanced tools
Diskpart
list volume (take note of boot partition volume and windows partition letter)
select volume X (X partition responsible for booting the system, hidden partition in fat32)
assign letter w (to be able to recover the boot files)
exit (exit diskpart)
bcdboot X:Windows /s w: /f UEFI (X partition letter that contains the Windows folder)
reeboot system (select the new boot option if more than one)
msconfig (Boot - delete the Windows options and leave only the c:Windows option)
Hope this helps many of you!
answered Nov 14 '18 at 22:59
ZinomZinom
111
111
add a comment |
add a comment |
I think there is some problem with boot files or boot order.
The first thing you can do is disable fast startup by going to power options.
As fast startup uses a kind of hibernation techniques.
If it doesn't work perform an in-place upgrade without loosing your data. This will create new boot files and settings.
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
add a comment |
I think there is some problem with boot files or boot order.
The first thing you can do is disable fast startup by going to power options.
As fast startup uses a kind of hibernation techniques.
If it doesn't work perform an in-place upgrade without loosing your data. This will create new boot files and settings.
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
add a comment |
I think there is some problem with boot files or boot order.
The first thing you can do is disable fast startup by going to power options.
As fast startup uses a kind of hibernation techniques.
If it doesn't work perform an in-place upgrade without loosing your data. This will create new boot files and settings.
I think there is some problem with boot files or boot order.
The first thing you can do is disable fast startup by going to power options.
As fast startup uses a kind of hibernation techniques.
If it doesn't work perform an in-place upgrade without loosing your data. This will create new boot files and settings.
answered Jun 29 '16 at 9:37
Rohit kumarRohit kumar
31918
31918
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
add a comment |
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
I have tried an in place upgrade, but I still see the same problem.
– psych
Jun 29 '16 at 15:44
add a comment |
I struggle with similar problem with Windows 8.1.
When cloning from HDD to SSD, partitions serial and GUID kept intact.
But I not want to remove original HDD from system. So I needed to change GUID (in GPT for FAT EFI partition) and remove windows system partition from original HDD after cloning and before boot recovery.
When partition ID is non unique windows work strange, for example PE recovery unable to detect both HDD and SSD.
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
add a comment |
I struggle with similar problem with Windows 8.1.
When cloning from HDD to SSD, partitions serial and GUID kept intact.
But I not want to remove original HDD from system. So I needed to change GUID (in GPT for FAT EFI partition) and remove windows system partition from original HDD after cloning and before boot recovery.
When partition ID is non unique windows work strange, for example PE recovery unable to detect both HDD and SSD.
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
add a comment |
I struggle with similar problem with Windows 8.1.
When cloning from HDD to SSD, partitions serial and GUID kept intact.
But I not want to remove original HDD from system. So I needed to change GUID (in GPT for FAT EFI partition) and remove windows system partition from original HDD after cloning and before boot recovery.
When partition ID is non unique windows work strange, for example PE recovery unable to detect both HDD and SSD.
I struggle with similar problem with Windows 8.1.
When cloning from HDD to SSD, partitions serial and GUID kept intact.
But I not want to remove original HDD from system. So I needed to change GUID (in GPT for FAT EFI partition) and remove windows system partition from original HDD after cloning and before boot recovery.
When partition ID is non unique windows work strange, for example PE recovery unable to detect both HDD and SSD.
answered Jun 29 '16 at 11:20
Mikhail MoskalevMikhail Moskalev
1,4871112
1,4871112
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
add a comment |
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
I don't believe this will help me. I am removing the old HDD from the system so it shouldn't be a problem.
– psych
Jun 29 '16 at 15:26
add a comment |
I had this same problem, just create windows installation usb drive from official site, boot up from installation usb, then go to troubleshooting, start CMD there and copy all files (and folders) that start with boot* and efi* from installation usb to root directory of cloned SSD drive, after doing that my cloned SSD was able to boot. Also check your boot settings in bios.
add a comment |
I had this same problem, just create windows installation usb drive from official site, boot up from installation usb, then go to troubleshooting, start CMD there and copy all files (and folders) that start with boot* and efi* from installation usb to root directory of cloned SSD drive, after doing that my cloned SSD was able to boot. Also check your boot settings in bios.
add a comment |
I had this same problem, just create windows installation usb drive from official site, boot up from installation usb, then go to troubleshooting, start CMD there and copy all files (and folders) that start with boot* and efi* from installation usb to root directory of cloned SSD drive, after doing that my cloned SSD was able to boot. Also check your boot settings in bios.
I had this same problem, just create windows installation usb drive from official site, boot up from installation usb, then go to troubleshooting, start CMD there and copy all files (and folders) that start with boot* and efi* from installation usb to root directory of cloned SSD drive, after doing that my cloned SSD was able to boot. Also check your boot settings in bios.
answered Dec 24 '16 at 11:53
user3749233user3749233
1
1
add a comment |
add a comment |
I ran into this same issue cloning my OS drive to a new SSD and was able to resolve it.
I noticed I had two Windows Boot Manager listed that pointed to the original drive.
1: I downloaded BootIce v1.3.4 by Pualy.
2: I went to the UEFI tab>> Edit boot entries button
3: There were two Windows Boot Manger listed in the listbox on the left, they both pointed to the same hard drive.
4: I selected one of them and changed it to point to my new SSD>> Click Save current boot entry button.
5: When I rebooted and went into the BIOS i was able to change the boot priority to the Windows Boot Manager of the new drive.
Success! I am now typing this from the Windows 10 loaded from the new SSD.
I plan on formatting the old one for secondary storage once I feel comfortable this is stable.
add a comment |
I ran into this same issue cloning my OS drive to a new SSD and was able to resolve it.
I noticed I had two Windows Boot Manager listed that pointed to the original drive.
1: I downloaded BootIce v1.3.4 by Pualy.
2: I went to the UEFI tab>> Edit boot entries button
3: There were two Windows Boot Manger listed in the listbox on the left, they both pointed to the same hard drive.
4: I selected one of them and changed it to point to my new SSD>> Click Save current boot entry button.
5: When I rebooted and went into the BIOS i was able to change the boot priority to the Windows Boot Manager of the new drive.
Success! I am now typing this from the Windows 10 loaded from the new SSD.
I plan on formatting the old one for secondary storage once I feel comfortable this is stable.
add a comment |
I ran into this same issue cloning my OS drive to a new SSD and was able to resolve it.
I noticed I had two Windows Boot Manager listed that pointed to the original drive.
1: I downloaded BootIce v1.3.4 by Pualy.
2: I went to the UEFI tab>> Edit boot entries button
3: There were two Windows Boot Manger listed in the listbox on the left, they both pointed to the same hard drive.
4: I selected one of them and changed it to point to my new SSD>> Click Save current boot entry button.
5: When I rebooted and went into the BIOS i was able to change the boot priority to the Windows Boot Manager of the new drive.
Success! I am now typing this from the Windows 10 loaded from the new SSD.
I plan on formatting the old one for secondary storage once I feel comfortable this is stable.
I ran into this same issue cloning my OS drive to a new SSD and was able to resolve it.
I noticed I had two Windows Boot Manager listed that pointed to the original drive.
1: I downloaded BootIce v1.3.4 by Pualy.
2: I went to the UEFI tab>> Edit boot entries button
3: There were two Windows Boot Manger listed in the listbox on the left, they both pointed to the same hard drive.
4: I selected one of them and changed it to point to my new SSD>> Click Save current boot entry button.
5: When I rebooted and went into the BIOS i was able to change the boot priority to the Windows Boot Manager of the new drive.
Success! I am now typing this from the Windows 10 loaded from the new SSD.
I plan on formatting the old one for secondary storage once I feel comfortable this is stable.
edited Nov 4 '17 at 0:19
mic84
2,29721817
2,29721817
answered Nov 3 '17 at 23:27
PhilipPhilip
1
1
add a comment |
add a comment |
just met the same problem, actually a small mistake on 2nd clone of 2nd new laptop.
1st laptop clone, connect alone and boot up ok, the default hard disk connect on 2nd boot and formatted without problem.
But on 2nd laptop clone, connect newly clone SSD and original hard disk still with win10 in it, although choose boot with SSD, then wipe the hard disk OS, next time failed.
Solution: use Macrium Reflect bootable disc, go to restore > fix Windows Boot problem, it auto fix the boot manager.
Remind next time after clone, boot the cloned disk alone without original source disk, connect after 1st boot.
add a comment |
just met the same problem, actually a small mistake on 2nd clone of 2nd new laptop.
1st laptop clone, connect alone and boot up ok, the default hard disk connect on 2nd boot and formatted without problem.
But on 2nd laptop clone, connect newly clone SSD and original hard disk still with win10 in it, although choose boot with SSD, then wipe the hard disk OS, next time failed.
Solution: use Macrium Reflect bootable disc, go to restore > fix Windows Boot problem, it auto fix the boot manager.
Remind next time after clone, boot the cloned disk alone without original source disk, connect after 1st boot.
add a comment |
just met the same problem, actually a small mistake on 2nd clone of 2nd new laptop.
1st laptop clone, connect alone and boot up ok, the default hard disk connect on 2nd boot and formatted without problem.
But on 2nd laptop clone, connect newly clone SSD and original hard disk still with win10 in it, although choose boot with SSD, then wipe the hard disk OS, next time failed.
Solution: use Macrium Reflect bootable disc, go to restore > fix Windows Boot problem, it auto fix the boot manager.
Remind next time after clone, boot the cloned disk alone without original source disk, connect after 1st boot.
just met the same problem, actually a small mistake on 2nd clone of 2nd new laptop.
1st laptop clone, connect alone and boot up ok, the default hard disk connect on 2nd boot and formatted without problem.
But on 2nd laptop clone, connect newly clone SSD and original hard disk still with win10 in it, although choose boot with SSD, then wipe the hard disk OS, next time failed.
Solution: use Macrium Reflect bootable disc, go to restore > fix Windows Boot problem, it auto fix the boot manager.
Remind next time after clone, boot the cloned disk alone without original source disk, connect after 1st boot.
answered Dec 29 '18 at 5:27
gl7gl7
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1093305%2fwindows-10-fails-to-boot-after-hdd-clone-to-ssd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I ran into similar issues attempting to clone my Win 10 SSD (40GB) to my new one (256GB) using Acronis. I spent a good week on it before I gave up and reinstalled it on the new drive completely.
– Thebluefish
Jun 24 '16 at 22:48
I don't normally recommend software, but the program I am going to suggest has never failed me, paragon-software.com/technologies/components/migrate-OS-to-SSD up to you if it's worth a try or not though
– Ramhound
Jun 24 '16 at 23:07
2
one lazy way , is to install the system normal, which gets all the mbr/gpt stuff set, then drop the partition clone in overwriting the partition, which has all your additions and customisations. That trick worked with most of the windows systems.
– Psycogeek
Jun 25 '16 at 4:54
What is your source disk partitioning MBR or GPT howtogeek.com/193669/… ? How old is your cloning software? What is your SSD type?
– Vojtěch Dohnal
Jun 27 '16 at 8:44
And what is the type/brand of computer you are trying to run it on? Some laptops have BIOS limitations.
– Vojtěch Dohnal
Jun 27 '16 at 9:31