Restoring Registry Backup = BSOD


Recommended Posts

I want to try again, but this time, I have to ask,

How do I fully restore a registry backup? (Problem was probably in the fact that I can't fully restore it so..)

It is an 82.6 MB file (15 days old) and there is no way in hell to restore it fully from within Windows as I see it. :|

Link to comment
https://www.neowin.net/forum/topic/792766-restoring-registry-backup-bsod/
Share on other sites

How to back up and restore the registry in Windows: http://support.microsoft.com/kb/322756

The above uses System Restore

I have created manual backup Registry files as well, ad have had difficulties in restoring it completely

Did you use a specialized program to originally back up your registry?

Does System Restore work?

Have you tried Safe Mode?

How to back up and restore the registry in Windows: http://support.microsoft.com/kb/322756

The above uses System Restore

I have created manual backup Registry files as well, ad have had difficulties in restoring it completely

Did you use a specialized program to originally back up your registry?

Does System Restore work?

Have you tried Safe Mode?

I don't use System Restore.

I got an idea on how to restore it more completely, will see if it works. Probably won't.

Yes, it was specialized, called regedit.exe

I don't use System Restore.

Wouldn't have posted otherwise - driver problems after restoring a backup are rather easy to fix.

Something is happening during the Import and is causing the BSOD at boot.

I need to restore everything related to Windows Installer, File Associations, and Installed Applications.

Use a boot Cd called UBCD4Win which you can download from UBCD4WIN. Its a boot CD that gives you a Windows like desktop loaded with various computer repair tools.

Once you have downloaded the ISO from ubcd4win.com, burn it to a CD and boot the computer from it.

Go to Start > Programs > Registry Tools > Registry Restore Wizard to repair the registry.

I like to keep backups of my registry with a really good tool to backup/restore and optimize, called ERUNT.

ERUNT

Use a boot Cd called UBCD4Win which you can download from UBCD4WIN. Its a boot CD that gives you a Windows like desktop loaded with various computer repair tools.

Once you have downloaded the ISO from ubcd4win.com, burn it to a CD and boot the computer from it.

Go to Start > Programs > Registry Tools > Registry Restore Wizard to repair the registry.

UBCD4Win needs to be built first. I wrote about it here: http://www.techspot.com/vb/topic123957.html

"I don't use System Restore"

"I don't use Antivirus software"

I'm totally understanding of why some people decide to work on their computer on their own, but isn't it good to have a backup plan? I mean, if you did have System Restore turned on, even if you didn't use it as your first option, you probably wouldn't have this issue right now.

You are taking me for an idiot: regedit /s is using regedit to import without actually using the graphical interface. In other words, BSOD.

Anyway, I am reinstalling, this time though, I will make full Windows backups instead. .reg backups failed me.

I may have worded my (removed) reply incorrectly

I am not taking you for an idiot

I asked if you could try Regedit from a command prompt to avoid any changes corrupting on your Windows GUI, including even your wallpaper, or any other change in your GUI due to the Registry import. That could possibly cause the import to fail.

You have stated that the import (I think works, but still not sure) but when starting up again you have "BSOD at boot" This would mean that the original .REG file, is likely adding (not replacing) to any changes you have made since creating the backup. And that change is then conflicting with the original registry

It may have been a Windows Security Update, or it may have been some new program installed, conflicting with drivers or services or just references to registry entries that cannot work together. Therefore upon successful import of your registry backup you could have either Repaired Windows. Or before doing the registry import, you could have uninstalled any new software (or hardware) changes

You have now decided to "Reinstall" Windows and create full Windows backups instead. I note that the best option for this would be to image the system, which includes Windows and all other files; filesystem and installed programs and updates and registry. Basically a copy of everything. Registry backups however, can just be done via System Restore, or by making smaller designated areas of the registry (possibly giving multiple backup registry files)

Yes you can ask any question you like, I just wanted you to confirm that support replies worked or not, before answering why try this. Many users/members ask why to try something that is suggested by support members, to explain these things in detail can be difficult at times, and therefore I ask members to first try what is mentioned, then see if it worked or not. If it works the question may not even require answering any longer, or may be given more time is explaining the differences or reasons why.

You may feel secure in knowing that I am happy to answer any question (in detail), but ideally I ask to leave this to the end of the thread, whilst the support replies, due to the original issue, are still being tried.

I tried that said command before showing frustration.

I am probably just going to make a *.bak backups of my registry hives this time to avoid any complications that might arise.

The full import will never truly work from within that said OS as that said OS prevents access to certain parts of the registry that may or may not have changed. That might be the problem and the whole add and not delete and replace thing..

I would say that if it was a driver issue then a safe boot would have worked as most drivers are not being loaded during a safe boot. Also, I do not really update my Windows, except DX9.

I already reinstalled XP (this time x32 - massively nlited - fresh install under 500MB - now it bloated to 900MB ) - took about 20 minutes to install and another two hours to get everything working. Saved myself some space.

You know, I was fairly certain that a registry backup (*.reg) could be modified back into individual hives - as to - replace the new and crappy registry hives. I am surprised that such a tool is non-existent. :|

I have created manual backup Registry files as well, ad have had difficulties in restoring it completely
You know, I was fairly certain that a registry backup (*.reg) could be modified back into individual hives - as to - replace the new and crappy registry hives. I am surprised that such a tool is non-existent. :|

Yes I agree. I have not backed up the entire Registry for many years due to this issue you have had

Backing up the actual Hive files is a good idea ;)

These days I just use imaging and that's all. Everything recovered in about 30 to 45 mins. And I keep my data external

At least the clean install is probably working much faster now for you

Thanks for the update.

You know, I was fairly certain that a registry backup (*.reg) could be modified back into individual hives - as to - replace the new and crappy registry hives. I am surprised that such a tool is non-existent. :|

Individual hives can be replaced from the recovery console. For example, the command to replace the system hive is:

ren c:\windows\system32\config\system system.old

copy c:\windows\repair\system c:\windows\system32\config

This process can also be used for the software hive and the security hive. Of course if you use it for the software hive, all programs installed after the initial OS install will have to be reinstalled.

By the way, using a registry backup utility (such as the free and excellent ERUNT) or a drive imaging utility (which I believe everyone should use) will help avert similar problems in the future.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.