1.

Solve : XP pro - sp2 won't start after merging some registry back ups/reboot?

Answer»

.........and nothing I've tried has worked. Including a fresh set of boot disks I downloaded from microsoft.

One time I got as far as the repair console and it asked me for my password, lol. (embarrassingly, I have no idea what it is if even exists. Had it on automatic sign in since my last clean install!!! lol)

Needless to say, that's about as far as I have gotten. Left on it's own, it will just cycle threw to the advanced settings partition over and over again....

Given what I was up to at the time, I can pretty much guarantee that it isn't a hardware issue at all.

I did try to get to the C prompt 1 or 2 times, but that was before I tried the boot disks. Just to see if I could as I don't really have the knowledge to do much if I did get in there.....:-(

Anyway, thanks in advance to anyone that can offer a solution to my problem here. Quote

Given what I was up to at the time, I can pretty much guarantee that it isn't a hardware issue at all.

I'd put my money on a corrupt registry

Quote
One time I got as far as the repair console and it asked me for my password, lol. (embarrassingly, I have no idea what it is if even exists. Had it on automatic sign in since my last clean install!!! lol)

Repair Console=Recovery Console This is a well documented problem with some versions of XP, the fix is a registry edit but you cannot access the registry.

The relevant MS KB is here, unfortunately the 'cure' requires you to access the Recovery Console.

Quote
I did try to get to the C prompt 1 or 2 times, but that was before I tried the boot disks. Just to see if I could as I don't really have the knowledge to do much if I did get in there.

Have you tried Safe Mode?

Did you create a Restore Point before merging registry backups? It's possible to go back to a Restore Point from the Command Prompt.

Did you fully backup your registry before merging (using ERUNT or similar)?

Do you have an install cd of XP Pro? You may have to do a Repair Install.

Are there any critical data files on your hdd which you want to backup before a possible/probable reinstall?

This is why manually editing the registry can be a dangerous thing...
As Dusty stated without a good backup of the Registry you may be looking at a re-install.Quote from: Dusty on March 08, 2008, 01:53:13 AM
Quote
Given what I was up to at the time, I can pretty much guarantee that it isn't a hardware issue at all.

I'd put my money on a corrupt registry Because of how far I can get, I think that it's the boot record that is corrupt, yes?

Quote
One time I got as far as the repair console and it asked me for my password, lol. (embarrassingly, I have no idea what it is if even exists. Had it on automatic sign in since my last clean install!!! lol)

Repair Console=Recovery Console Yes
This is a well documented problem with some versions of XP, the fix is a registry edit but you cannot access the registry.

The relevant MS KB is here, unfortunately the 'cure' requires you to access the Recovery Console.

Quote
I did try to get to the C prompt 1 or 2 times, but that was before I tried the boot disks. Just to see if I could as I don't really have the knowledge to do much if I did get in there.

Have you tried Safe Mode? Yes, no go.....

Did you create a Restore Point before merging registry backups? It's possible to go back to a Restore Point from the Command Prompt. I should have lots of restore points. But I made those threw apps like CCleaner etc....

Did you fully backup your registry before merging (using ERUNT or similar)? No

Do you have an install cd of XP Pro? Yes

You may have to do a Repair Install. **See following post to see where I am to this point.....**

Are there any critical data files on your hdd which you want to backup before a possible/probable reinstall? Yes



Well, this is where I'm at now. My hold up now is that recovery console is asking for a password. I'm trying to use "Windows-KEY-Enterprise". It was in ISO. The machine I have to use doesn't have a burner and so I tried using ISO MAGIC. **Not sure if I did that right!!!**
Because of it's size, I knew that I would have to span it over multiple floppies, right?

I think that I mounted it to a virtual drive ok. So I just right clicked to add it to a spanned zip file? To which it made 5 of...

SO! lol Now I can get as far as recovery console, then select the windows installation that I want to repair ( C: WINDOWS ) , but I can't seem to get it to boot those floppies when it needs to deal with the password issues..... Baaaahhh!!!

The boot sequence is:

1:) CD
2:) A:\Windows-Key-Enterprise\disk#1of5
3:) C:WINDOWS At the password prompt just hit Enter...
Quote from: patio on March 09, 2008, 07:04:45 PM
At the password prompt just hit Enter...


That's what I thought too. But it says wrong and makes me try again. Up to 3 times, then says that you've gotten it wrong 3 times and hit enter to restart.....

Then it just cycles back again.............since then, I have tried just copy and pasting the contents of the mounted image onto A: drive and it seemed to span it on it's own, without using winzip. Still the same....didn't work.....! lol Quote from: Digit on March 09, 2008, 07:10:23 PM
Quote from: patio on March 09, 2008, 07:04:45 PM
At the password prompt just hit Enter...


That's what I thought too. But it says wrong and makes me try again. Up to 3 times, then says that you've gotten it wrong 3 times and hit enter to restart.....

Then it just cycles back again.....

I don't have any gems of info to assist with your current problem. However, with regard to the Recovery Console password, I posted something like this on Jan.22.

Quote
There are several things I believe should be done when your system is running sweetly, in preparation for the day your system lets you down. Here is one of them:

On many XP installations you can't start the Recovery Console because it won't recognize any password, even if a password has never been set, and will not accept a blank password either. This registry edit causes the Recovery Console not to ask for a password. This works for both XP Home and XP Professional.

Start | Run | Regedit
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Setup\RecoveryConsole
Set the DWORD SecurityLevel value to 1
Exit Registry and Reboot

Might come in HANDY for when your system is back to normal.

If I were you I'd be getting close to format & re-install

Quote

If I were you I'd be getting close to format & re-install




Really? But why? I hope it's not because it's the easiest/shortest way?Quote from: Digit on March 09, 2008, 06:42:09 PM

I'm trying to use "Windows-Key-Enterprise". It was in ISO.....

.........but I can't seem to get it to boot those floppies when it needs to deal with the

password issues.....


There just HAS to be some way to get by this little hurdle!!! lolWindows Key Enterprise seems to be a third party utility to set/change the admin password to 12345. The password problem with Recovery Console is not due to any password, and even if you were able to set an admin password Recovery Console would not accept it. The problem is a bug in XP which seems not to go away unless the Registry entry is amended to stop Recovery Console asking for a password.

Quote from: Digit
Are there any critical data files on your hdd which you want to backup before a possible/probable reinstall? Yes

So why don't you concentrate on recovering your files

Quote from: Dusty
If I were you I'd be getting close to format & re-install
Quote from: Digit
Really? But why? I hope it's not because it's the easiest/shortest way?

Perhaps I was a bit HASTY.... but from my point of view there comes a time when trying to save an operating system is a total waste of time and the recovery of critical data files is surely more important. Without backup of these files there's the possibility, even if it's a REMOTE possibility, that data which has taken a long time to create will be lost or damaged while trying to save an operating system which can easily be re-installed.

Good luck with your struggles.



Discussion

No Comment Found