[SOLVED] Operating system needs to be repaired.

Solution
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If...
i imagine the error is with the clone, not the original drive?

if you still have the original drive with the OS on it just try again.
i've seen clones turn out corrupted many times where just redoing them works out eventually.

you can also try different software.
Samsung Magician always used to work with any brand, i imagine it still does.
 
i imagine the error is with the clone, not the original drive?

if you still have the original drive with the OS on it just try again.
i've seen clones turn out corrupted many times where just redoing them works out eventually.

you can also try different software.
Samsung Magician always used to work with any brand, i imagine it still does.
Thanks for that. I'll do as suggested but... I had this same error message prior to cloning (that's why I went the cloning route). This just doesn't make any sense? Cloning should have removed the missing or corrupted system files but it didn't???
 
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specifiy the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------
 
Solution
Thanks for this. Will give it a go and get back to you. Although I'm unclear as to your last part. Why would I want to wipe all partitions on the drive if everything is good?
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specifiy the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------

The source and target drives are the same make and size. Will cloning still work here?
 
no, it shouldn't have.

you are cloning the exact same operating system with the exact same data.
any issue you had with the original is just carrying over to the clone as it should.
no, it shouldn't have.

you are cloning the exact same operating system with the exact same data.
any issue you had with the original is just carrying over to the clone as it should.

I see. Then that really doesn't make sense to me because I am having no issues with the source drive? But I guess based on what you are saying its just a matter of time.
 
I see. Then that really doesn't make sense to me because I am having no issues with the source drive? But I guess based on what you are saying its just a matter of time.
I see. Then that really doesn't make sense to me because I am having no issues with the source drive? But I guess based on what you are saying its just a matter of time.
No sense recloning then. I have corrupted system files. I've wracked my brains for days doing all kinds of repair attempts to no avail. Even reformatted the drive but I guess with cloning I just got the same problem back. Maybe I'll try reformatting again, skip the cloning get the drive to where I need it then clone it as the source to the other target drive. Unless, you have better idea.
 
I am having no issues with the source drive
but you just stated,
Error code 0xc0000001...
I had this same error message prior to cloning
so which is it?

did your original drive produce this error and you then decided to clone thinking it would repair the issue?
or have you just been confused when writing this thread and there's something else going on?
 
No sense recloning then. I have corrupted system files. I've wracked my brains for days doing all kinds of repair attempts to no avail. Even reformatted the drive but I guess with cloning I just got the same problem back. Maybe I'll try reformatting again, skip the cloning get the drive to where I need it then clone it as the source to the other target drive. Unless, you have better idea.
Basically as a backup computer. That's it.
 
No sense recloning then. I have corrupted system files. I've wracked my brains for days doing all kinds of repair attempts to no avail. Even reformatted the drive but I guess with cloning I just got the same problem back. Maybe I'll try reformatting again, skip the cloning get the drive to where I need it then clone it as the source to the other target drive. Unless, you have better idea.
A clone operation does NOT fix a corrupted source.
You are simply moving the problem between drives.

Fix the source.
Or a full wipe and reinstall.
 
Let me explain. I have two identical computers (model, make, hard drive, etc.) that I keep, one as my working computer and the other as backup (source vs target). I used Macrium Reflect to do image backups on both back and forth which I didn't realize is not a smart thing to do (should have done cloning instead). Anyhow, thinking the source drive was okay, I did a clone of the target drive which was clearly problematic only now to find out from you that the source drive is the problem too because the target drive still has the same corrupt systems files problem after cloning. Hope this explains it all. Next I'm ready to blow my brains out as I'm exhausted, been at it for days. Should of came here to begin with.
 
Again...if the source drive and OS is faulty, cloning does not fix that.
It simply copies the problem to a different drive and or system.
I realize that. Therefore, I see my only option is leaving my source drive alone (although corrupted) and reformatting/install the target drive to the point I have it where I need it then cloning it to the source drive is what I tried to say as being the only solution I can think of. Can you think of a better option?
 
I realize that. Therefore, I see my only option is leaving my source drive alone (although corrupted) and reformatting/install the target drive to the point I have it where I need it then cloning it to the source drive is what I tried to say as being the only solution I can think of. Can you think of a better option?
If you can fix the current faulty drive and OS, what need is there for the clone operation?

Keeping a whole second PC as an exact duplicate would seem to be a waste of resources.
There are other ways to safeguard the data and OS.

In any case...you need to either completely fix the original, or a full wipe and reinstall on the original system.
 
If you can fix the current faulty drive and OS, what need is there for the clone operation?

Keeping a whole second PC as an exact duplicate would seem to be a waste of resources.
There are other ways to safeguard the data and OS.

In any case...you need to either completely fix the original, or a full wipe and reinstall on the original system.
Like I said I spent days on this target drive. I think you are right, using this target drive computer as a back up is a waste of resources considering I have Macrium and Aeomei backupper. But I still need to recover this drive while now trying to figure out what's wrong that's not showing itself with my original drive. Presently doing a sfc /scannow on it. But if that doesn't fix what's broken when nothing is showing as broken not sure what I should do next. Any ideas or suggestions would be appreciated.
 
Like I said I spent days on this target drive. I think you are right, using this target drive computer as a back up is a waste of resources considering I have Macrium and Aeomei backupper. But I still need to recover this drive while now trying to figure out what's wrong that's not showing itself with my original drive. Presently doing a sfc /scannow on it. But if that doesn't fix what's broken when nothing is showing as broken not sure what I should do next. Any ideas or suggestions would be appreciated.
If nothing else works, full wipe and reinstall

Find and save all your personal critical data.
Save that elsewhere.
Full wipe and reinstall.

 
If nothing else works, full wipe and reinstall

Find and save all your personal critical data.
Save that elsewhere.
Full wipe and reinstall.

Will do. Thanks for your input. And for the link. Best, John