Can't boot off of cloned hard drive

By rorbot ·
OS xp pro sp3, all drives are SATA

I cloned my dying C drive to a new one I just bought using norton ghost v14. However, removing the old drive and trying to boot off of the newly cloned drive won't let me get past the blue log in screen. My computer just sits there with no error message just an annoying windows xp logo. For some reason when i reconnected my old HD and had both connected at the same time i was able to get to the desktop.

I've been reading around and some people are suggesting that this is a windows security measure that doesn't allow you to run windows off a drive with a different serial #.

Just wanted to confirm if this was the case and if anyone had any suggestions?

any help would be great thanks.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

It's not security

by Jacky Howe In reply to Can't boot off of cloned ...

it's probably a glitch try this.
Boot the system using the Windows XP CD-ROM. In the first screen when the Setup begins, read the instructions press "R" (in the first screen) enter the Recovery Console.
Which Windows Installation would you like to log on to
(To cancel, press ENTER)?
After you enter the number for the appropriate Windows installation, Windows will then prompt you to enter the Administrator account password.
Note If you use an incorrect password three times, the Windows Recovery Console closes. Also, if the Security Accounts Manager (SAM) database is missing or damaged, you cannot use the Windows Recovery Console because you cannot have correct authentication. After you enter your password and the Windows Recovery Console starts, type exit to restart the computer.
Type the following command and press Enter.
(If that does not work, try CHDIR SYSTEM32)
At the prompt type in
Quit Recovery Console by typing EXIT and restart Windows.
You'll be able to login successfully as you've created the wsaupdater.exe file (now, a copy of userinit.exe)
Backup the Key before making changes.
Now, change the USERINIT value in the registry
Click Start, Run and type <b>Regedt32</b> and press Enter.
Navigate to:
In the right pane you will see that the value of the Userinit key is incorrectly set to <b>"wsaupdater.exe,"</b>

In the right-pane, change the value of Userinit to C:\WINDOWS\system32\<b>userinit.exe,</b>
Type the above value exactly as given, including the comma. Also, change the path to userinit.exe appropriately if Windows is installed in a different drive.
Close Registry Editor and restart Windows.
<i>Keep us informed as to your progress if you require further assistance.

Collapse -

some weird problems

by rorbot In reply to It's not security

first, thanks for your quick reply.

I went into windows repair and I noticed a weird pattern. rebooting with just the cloned drive i get 1: C:\WINDOWS only at the recovery console. But when i reboot and go into the recovery console with both drives connected (cloned + old) I get both 1: C:\WINDOWS and 2: F:\WINDOWS.

The odd thing is "My Computer" shows my old drive mapped to C: and the new one mapped to I:. It seems to be all mixed up. I don't have a F:/WINDOWS directory my F drive is just one of my storage drives.

(is it possible for my computer to set the old drive as C and the new one as I, but when in the booting area windows thinks the new one is C and the old one is F?

so that confused me as to which one to pick. I tried doing it on the F:/WINDOWS directory but it didn't seem to change anything.

the registry edit seemed promising I saw that userinit was still on C:\WINDOWS\system32\userinit.exe, so I changed it to I:\WINDOWS\system32\userinit.exe, but that didn't change anything either I still needed the old drive for the log-in screen to show me my profile so I could sign in.

I can log in and edit my cloned drive's properties (as long as I have the old drive connected too) so im not sure the windows repair part is necessary, however the registry might be the solution. changing the path to userinit.exe really made sense just don't know why it didn't work.

it's as if the log in part of the boot sequence is looking for the files on the old drive because of path in the registry is still set to the old drive's mapping since its a clone copy. I think I need to edit some stuff so it looks for the stuff on the new drive instead of the old one.

Collapse -

Remove you old hard drive and boot from the XP CD

by Jacky Howe In reply to some weird problems

Insert your XP CD and when you see ?Press any key to boot from CD? press a key. Now wait for the XP installer to finish loading up and you will be presented with the option to press R to Repair.
Press R.
The next screen will ask you which Windows? installation you would like to log on to. Normally the following will be listed:
Press 1, then Enter to continue.
You may now be asked for the Administrator password. If you know this type it and press Enter. If you don't know the Administrators password it may be blank. Just press Enter or type your username and password.
At the command prompt type:
fixmbr and press Enter
fixboot and press Enter
bootcfg /rebuild and press Enter
Wait until you are returned to the Recovery Console.
Once you are back to the Recovery Console remove the XP CD and restart your PC.
<i>Keep us informed as to your progress if you require further assistance.

Collapse -

still not working ;/

by rorbot In reply to Remove you old hard drive ...

thanks for all your help.

after i did the bootcfg /rebuild

i got prompted with

enter load identifier:
enter OS load options:

I think this created another boot option everytime i boot my computer i have 2 options to pick from both didn't work unless i had the old drive in.

I think im just going to go ahead and reformat it

thanks for all your help

Collapse -

It has to do with hidden physical partitions, typically

by robo_dev In reply to still not working ;/

Many times I've had problems booting ghosted drives.

The most typical cause of the problem are when the PC vendor (Dell, Compaq) has a hidden Diagnostics or Recovery partition on the hard drive. If you ghost the Windows partition to a blank drive, but not those other partitions, then the new drive is NOT the same, with respect to where to look for the boot sector. Typically a Compaq laptop will just sit there with a flashing __ at the upper left.

Some Dell PCs, for example, have three hidden partitions, so it aint easy!!

The solution depends on the manufacturer, for Dell, it's kinda complicated.... www.goodells.net/dellrestore/fixes.htm

As I recall for Compaq, you would have to do their disk-prep utils to setup the correct diag partitions, the ghost to it.

Collapse -

My computer is custom built

by rorbot In reply to It has to do with hidden ...

and i'm using Western Digital drives. Each drive just has one big partition. my the WD will have some info i'll check

Collapse -

Bios issue?

by robo_dev In reply to My computer is custom bui ...

On one PC, it would not boot because the cloned drive was a larger capacity, and the bios version had 'issues' with drives over 140GB. A bios update fixed that one....

Typically there there bios settings to toy with regarding SATA... (LArge versus AUTO, SATA1 versus SATA2)

Are you ghosting from SATA to SATA...(PATA to SATA tends to have problems).

Sorry if you posted this info already....did ANYTHING else change? (SATA controller, MOBO, etc).

Collapse -

not likely a BIOS issue if it boots to Windows up until

by The Scummy One In reply to My computer is custom bui ...

the logon screen.
This does not sound like a boot issue, but a Repair issue for Windows.

However, if you want to re-try the clone, I have had less problems with Linux and the dd command than with Ghost.
With dd, it clones the entire drive bit by bit, to make an exact copy. You can set by partition, or do the entire drive.
Afterwards, use a partition extender to get the newly available disk space.

Collapse -

I agree with scummy

by Dumphrey In reply to My computer is custom bui ...

on the DD command. Ghost went down hill fast after version 2003...

So can you get to the recover console at all from the new hard disk? FIXMBR and fixboot and chkdsk are 3 command to try if you can get in. You may want to erase the disk and try a new clone (last resort), you may have some corruption in the data. Also would not hurt to run chkdsk on the cloned drive to verify partition information. Also, verify that the bootable flag is enabled on the cloned disk. It SHOULD have enabled that on the clone, but ya never know. Can you specify what drivers to use for the sata disks in Ghost 14?
Clonezilla is a GPL ghost-like product that can do bit copy of a disk. This means its slower then partition copy tools like ghost, but more reliable. http://clonezilla.org/
Try using a different tool to create the clone and compare.

Collapse -

Yeah I can reach windows recovery console

by rorbot In reply to My computer is custom bui ...

i tried fixmbr fixboot chkdsk all that stuff and bootcfg /rebuild but it still required the old drive for me to get passed the log on screen and use my new drive as the new system drive (how weird is that?)

(btw anyone know how to delete the new bootcfg i created now its always asking me to pick one everytime i boot up)

I'm going to try your suggestions and use a different program cause a lot of people have had problems with norton ghost.

thanks all

Related Discussions

Related Forums