50
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Aug 2024
50 points (100.0% liked)
techsupport
2470 readers
34 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS
Did you try running the repair to see if it fixes it?
The reason is the boot drive now has a different ID, so Windows can't boot from it. So it assumes (rightly so) that the boot drive has changed and launches into repair to fix it. This is something repair can fix for you normally.
Another way is to open up a command prompt in the repair environment (or from a Windows USB stick). Then use the bcdtool to edit the boot options and tell it to use the correct drive. There are plenty of instructions on this found with a simple Google search.
The cloning probably went fine, so don't assume it has anything to do with that. Just a completely different ssd which trips up the boot.
Notably on Linux device ID are also normally used, so you would have the same kind of issue. Ignore all the Linux fanboys that go Windows bad Linux good and don't actually help you.