Hello,
I am having a pretty large problem with a boot issue on my PC. Yesterday, I attempted to clone the files on my previous SSD, a 120GB OCZ Vertex Plus R2, to a larger Samsung EVO 250GB. However, the Samsung SSD did not boot, and soon after, the OCZ SSD stopped booting as well. It would either say that it wasn't connected, that there was a problem with winload.efi, or get stuck in a loop of automatic repair-->diagnosis-->drive repair-->BSOD almost as soon as repair starts. I formatted the Samsung drive, and now it appears that the OCZ drive is not set as bootable. I have attempted to fix errors with Macrium Reflect, and attempted to use bootrec and bcdboot, however nothing has changed. When I checked the drive with diskpart, it was listed as not bootable. Is there anything that can be done to solve this issue? Thank you!
Another issue: I just tried running bcdboot /scanos, bcdboot /rebuildbcd, bcdboot /fixmbr just now, and it said that there were no Windows installations found, even though I could access all of my files from the recovery environment.
I am having a pretty large problem with a boot issue on my PC. Yesterday, I attempted to clone the files on my previous SSD, a 120GB OCZ Vertex Plus R2, to a larger Samsung EVO 250GB. However, the Samsung SSD did not boot, and soon after, the OCZ SSD stopped booting as well. It would either say that it wasn't connected, that there was a problem with winload.efi, or get stuck in a loop of automatic repair-->diagnosis-->drive repair-->BSOD almost as soon as repair starts. I formatted the Samsung drive, and now it appears that the OCZ drive is not set as bootable. I have attempted to fix errors with Macrium Reflect, and attempted to use bootrec and bcdboot, however nothing has changed. When I checked the drive with diskpart, it was listed as not bootable. Is there anything that can be done to solve this issue? Thank you!
Another issue: I just tried running bcdboot /scanos, bcdboot /rebuildbcd, bcdboot /fixmbr just now, and it said that there were no Windows installations found, even though I could access all of my files from the recovery environment.