In my desktop i7 machine, Windows 10 1909:
I just bought an SSD and then cloned my C: hard drive to the SSD.
The SSD boots (very fast) and functions perfectly - only if I have the HDD also connected. It won't boot on the SSD alone, I get a 'PC needs repair' message.
(If I disconnect the HDD while it's running, the system fails. But while the HHD was running the system, I was able to hot-add the SSD with no problem.)
What's up?
1) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of
2) Download and install Minitool Partition Wizard > post an image of the results into this thread
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com
3) Open administrative command prompt and copy and paste (all at one time)
Code:bcdedit /enum all bcdedit | find "osdevice" reagentc /info diskpart lis dis lis vol sel dis 0 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel par 6 det par sel dis 1 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par sel par 6 det par
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) Post an image of the BIOS boot order
Cloning has probably resulted in both drives having the same disk ID which can cause problems and the PC may be booting from the active boot partition still on the HDD. You need to change the disk ID of the SSD, configure the boot configuration using bcdedit to boot from the SSD and change the status of all partitions on the HDD to inactive (e.g. using Partition Magic). I use imaging rather than cloning to move an installation to avoid the disk ID conflict.
For possible disk signature collision see this link:
https://docs.microsoft.com/en-us/arc...ure-collisions
Thanks Zbook and Steve C. The explanations given and the link most likely explain the problem. The fix suggested looks complex; so I 'd prefer to find a way to avoid the conflict and reclone the disk if that's possible.
I periodically clone my HDD to another HDD and have never had this issue before. I wonder if this happened because of cloning to an SSD.
Is there a switch or other way to prevent this conflict when cloning?
When available please update the thread with the results from post #2.
Imaging as compared to cloning should be free from signature collisions.
If the results indicate a cloning problem it may be able to be fixed using command line.
Last edited by zbook; 01 Mar 2020 at 04:37.
My objective was and is to clone the HDD to the SSD and then use the SSD as the working drive.
I need the SSD to boot independently for that.
I periodically clone the working drive (I've had problems with restoring images) and the cloned drive has always booted independently.
But this time, my first attempt to clone to an SSD - and with this conflict.
Is this an issue with SSDs?
When available please post results from administrative command prompt.
Quote