techsupport

2407 readers

7 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:

You Should Know

Software gore

Recommendations

founded 1 year ago

MODERATORS

GatoB@lemmy.world

Cloned Windows 10 drive keeps taking me to automatic repair after using clonezilla (midwest.social)

submitted 1 month ago by Lanky_Pomegranate530@midwest.social to c/techsupport@lemmy.world

11 comments fedilink hide all child comments

Ok so I was trying to clone 512gb nvme ssd to my new 2tb drive with clonezilla and it keeps taking me to automatic repair. I unplugged the original drive and replaced it with the new one before booting. I ran a chkdsk both times before cloning.

The first time I cloned the drive i used these settings:

device to device beginer disk to local disk Chose my source and target Skip disk checking -k0 use source partition table

Then I tried these settings:

device to device expert disk to local disk Chose my source and target Left everything as default -k1 Create partition table proportionally

I also plan on partitioning half of the drive so that I can dual boot linux as Window 10 is reaching eol and I don't want anything to do with Windows 11 and I still need Windows for gaming.

top 11 comments

sorted by: hot top controversial new old

[–] Thorry84@feddit.nl 1 points 1 month ago

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.

[–] rtxn@lemmy.world 1 points 1 month ago* (last edited 1 month ago)

I had the same issue, you need to run sysprep inside Windows immediately before you create the image. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation?view=windows-11

[–] Blaster_M@lemmy.world 1 points 1 month ago

Typically, I've fixed this with a Windows install stick and using the bcdboot command to rebuild the BCD from scratch.

[–] TrickDacy@lemmy.world 0 points 1 month ago (1 children)

It's been a while but I always had good luck with macrium reflect

[–] Jyek@sh.itjust.works 0 points 1 month ago (1 children)

No longer free

[–] TrickDacy@lemmy.world 0 points 1 month ago (1 children)

That sucks. Can you download the older versions? I know I have some on my drive.

[–] Jyek@sh.itjust.works 2 points 1 month ago

Not directly from macrium. I also wouldn't recommend using software from unofficial sources or that are out of date. Especially when it comes to your data. I use disk genius now. Works a treat.

[–] Jyek@sh.itjust.works 0 points 1 month ago (1 children)

I use disk genius. It's pretty great. Haven't had a single failed clone yet.

[–] Lanky_Pomegranate530@midwest.social 1 points 1 month ago (1 children)

Thanks for the reply. I was able to clone it last night using that software. Thank you.

[–] Jyek@sh.itjust.works 1 points 1 month ago

I'm glad it worked out!

[–] verdantbanana@lemmy.world -2 points 1 month ago

clones are never reliable

always use a fresh install