Ask a new question

Cloned a disk, now problems

Used Acronis true image yesterday to clone my current 2 tb Western Digital hd, to a W.D. 5 tb hard drive. Now I have problems.

I boot up my original drive and get an 0xc00007b error message. (The MPR.DLL file appears to be corrupt.) And most of the desktop programs I click on, now give me "The specified procedure could not be found". I tried to run sfc/scannow, but it also gives me "the specified procedure could not be found", (right below the C:\windows\system32\cmd.exe line).

I'm baffled how cloning a hard drive could have messed my system up.  I can still go online, no problems. 

(A few examples that no longer work, schedhlp.exe, mbarw.exe, and avgu.exe all give me pop ups saying "can't run."

 I already ran an antivirus (online) and malware program, and got nothing negative. Windows update gives me a 80080005 error code.

And finally system restore says "System restore could not start".

Thanks

Could it be that you booted the machine after cloning while both disks were connected?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I am afraid to say correct....

Time for a reinstall?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I am afraid to say correct....

Time for a reinstall?

Not necessarily. What you did got Windows very confused, resulting in a large number of incorrect registry entries. You might be able to fix the problem as below. Please note that you must type the commands very accurately and not take any liberties.

1. Connect the old disk, disconnect the new disk.
2. Keep tapping F8 during the early boot phase.
3. Select Repair from the menu.
4. Log on as Administrator if prompted.
5. Select Repair when prompted.
6. Select the Command Prompt from the menu.
7. Identify the correct drive letter for your Windows installation. It could be a drive other than C: but it won't be X:. You do it by typing the commands and pressing Enter after each:
    dir C:\Win*
    dir D:\Win*
    dir E:\Win*
    until you find the Windows folder.
    I shall call that drive "Q:".
8. Type these commands and press Enter after each:
    cd  /d  Q:\windows\System32\config
    xcopy  *.*  Q:\MyRegBack\
    cd  RegBack
    dir
9. Examine the dates of the Software, System and SAM files. Were the files created before or after your cloning activity?
10. If they were made before then you can type these commands and press Enter after each:
    copy /y software  ..
    copy /y System  ..
    copy /y Sam ..
    (the two dots are part of each command)
10. Reboot normally. If things do not work out then you can backtrack by copying the original registry files from Q:\MyRegBack to Q:\Windows\System32\config.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

All was well until step 10, where I got "the process cannot access the file because it is being used by another process".

It said that on all 3 files.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

All was well until step 10, where I got "the process cannot access the file because it is being used by another process".

It said that on all 3 files.

This would happen in either of these cases:

  • You tried to do it with drive X:. I specifically excluded drive X: in my instructions.
  • You did not boot the machine into Repair Mode but ran the commands while Windows was active.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated September 16, 2023 Views 1,819 Applies to: