Daily backups of registry useful, or unnecessary ?

[Mark Conrad]

Windows-7 newbie here.

I already have had one "blowout" of an application
that could have been registry corruption, but as a
newbie I am in no position to point the finger at the
registry, as being tha actual culprit.

Does anyone have experience, one way or the other,
for just how common registry corruption is ?

Thanks,

Mark-

 

[Big Steel Shoe Kicker]

Windows-7 newbie here.

I already have had one "blowout" of an application
that could have been registry corruption, but as a
newbie I am in no position to point the finger at the
registry, as being tha actual culprit.

Does anyone have experience, one way or the other,
for just how common registry corruption is ?

Thanks,

Mark-

It's not common. And I doubt that the real problem was due to the
registry. I have never backed-up the registry ever on any Windows O/S.

 

[LSMFT]

Windows-7 newbie here.

I already have had one "blowout" of an application
that could have been registry corruption, but as a
newbie I am in no position to point the finger at the
registry, as being tha actual culprit.

Does anyone have experience, one way or the other,
for just how common registry corruption is ?

Thanks,

Mark-

I used to back it all the time with Windows 95, 98, ME But not with
Windows 7. Never had a problem. I do do regular scheduled backups to an
external drive.

 

[Ken Blake]

I used to back it all the time with Windows 95, 98, ME But not with
Windows 7. Never had a problem. I do do regular scheduled backups to an
external drive.

I have erunt scheduled to automatically backup my registry every
morning. I've never needed to use any of the backups, but it takes
only seconds, uses a very small amount of disk space, and takes no
effort on my part.

It's extra security. It's not essential, but in my view there's no
reason not to provide yourself with extra protection, since it costs
nothing in dollars or effort, and next to nothing in time or disk
space.

 

[Bruce Chambers]

Windows-7 newbie here.

I already have had one "blowout" of an application
that could have been registry corruption, but as a
newbie I am in no position to point the finger at the
registry, as being tha actual culprit.

Does anyone have experience, one way or the other,
for just how common registry corruption is ?

Thanks,

Mark-

It's not at all common, unless you have defective RAM or suffer
frequent and unexpected power outages. (Or use a registry cleaner.)


--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

 

[Parko]

I have erunt scheduled to automatically backup my registry every
morning. I've never needed to use any of the backups, but it takes only
seconds, uses a very small amount of disk space, and takes no effort on
my part.

It's extra security. It's not essential, but in my view there's no
reason not to provide yourself with extra protection, since it costs
nothing in dollars or effort, and next to nothing in time or disk space.

ERUNT works with Win7? I'd forgotten about that package. Thanks for the
reminder.

 

[Nil]

It's not common. And I doubt that the real problem was due to the
registry. I have never backed-up the registry ever on any Windows
O/S.

If you have ever used the System Restore feature, you have backed up
the Registry.

 

[Nil]

Does anyone have experience, one way or the other,
for just how common registry corruption is ?

I can't say how common it is, but I can say that I have twice been
saved from major inconvenience by being able to restore a registry
backed up with ERUNT. Both times the registry had become corrupt due to
a failing hard disk.

 

[Mark Conrad]

I can't say how common it is, but I can say that I have twice been
saved from major inconvenience by being able to restore a registry
backed up with ERUNT. Both times the registry had become
corrupt due to a failing hard disk.

Interesting.

Thanks everyone for all the responses.

I will flip a coin, depending on which side comes up,
will use ERUNT, ... or not ;-)

Mark-

 

[Big Steel Shoe Kicker]

If you have ever used the System Restore feature, you have backed up
the Registry.

That's a no then.

 

[Dave \Crash\ Dummy]

Interesting.

Thanks everyone for all the responses.

I will flip a coin, depending on which side comes up,
will use ERUNT, ... or not ;-)

From the ERUNT FAQ page
http://larshederer.homepage.t-online.de/erunt/faq.htm
<quote>
Question: Do ERUNT and NTREGOPT run on Windows 7?

Answer: ERUNT and NTREGOPT in their current versions 1.1j are still
compatible with Windows 7, but as in Vista, they will only work
correctly if you turn off User Account Control in Windows' Control Panel
(move the slider to the lowest position).

Also, a problem has been discovered which on many systems causes ERDNT
and NTREGOPT to display a "RegSaveKey: 3" error when optimizing /
restoring the BCD00000000 hive. The cause is that after a clean install
of Windows 7, the BCD part of the registry which contains Windows' boot
configuration data resides on a hidden system partition with no drive
letter assigned in Explorer. You can simply ignore this error and
continue, or as a workaround, open Disk Managemant in Control Panel and
right-click on the partition displayed as "System Reserved" to assign a
drive letter.
</quote>

 

[Mark Conrad]

From the ERUNT FAQ page
http://larshederer.homepage.t-online.de/erunt/faq.htm
<quote>
Question: Do ERUNT and NTREGOPT run on Windows 7?

Answer: ERUNT and NTREGOPT in their current versions 1.1j are still
compatible with Windows 7, but as in Vista, they will only work
correctly if you turn off User Account Control in Windows' Control Panel
(move the slider to the lowest position).

Also, a problem has been discovered which on many systems causes ERDNT
and NTREGOPT to display a "RegSaveKey: 3" error when optimizing /
restoring the BCD00000000 hive. The cause is that after a clean install
of Windows 7, the BCD part of the registry which contains Windows' boot
configuration data resides on a hidden system partition with no drive
letter assigned in Explorer. You can simply ignore this error and
continue, or as a workaround, open Disk Managemant in Control Panel and
right-click on the partition displayed as "System Reserved" to assign a
drive letter.
</quote>

Thanks very much for that report. Just now downloaded ERUNT.

Mark-

 

[Ken Blake]

ERUNT works with Win7? I'd forgotten about that package. Thanks for the
reminder.

Yes, it works fine. And it takes me 3 or 4 seconds every morning.

Ken

 

[Dave]

Yes, it works fine. And it takes me 3 or 4 seconds every morning.

Ken

Thanks for the tip, I downloaded Erunt and it works good. What is your
opinion on it's sister program NTREGOPT NT Registry Optimizer? Info says it
doesn't remove any entries, only compacts it, so I'm not clear on any real
advantage, but sometimes I'm dense. :-D
Dave

 

[Ken Blake]

Thanks for the tip, I downloaded Erunt and it works good. What is your
opinion on it's sister program NTREGOPT NT Registry Optimizer? Info says it
doesn't remove any entries, only compacts it, so I'm not clear on any real
advantage, but sometimes I'm dense. :-D

You're welcome. Glad to help.

Registry cleaners are all dangerous, and even if NTREGOPT only
compacts the registry, compacting it isn't needed. So I never use it.

 

[Bob I]

Thanks for the tip, I downloaded Erunt and it works good. What is your
opinion on it's sister program NTREGOPT NT Registry Optimizer? Info says
it doesn't remove any entries, only compacts it, so I'm not clear on any
real advantage, but sometimes I'm dense. :-D
Dave

Ina nutshell, the registry is a database, and deleting entries in a
database leaves space where the entry was. Compacting databases merely
removes the "dead space". This was important for something like Outlook
Express dbx file as you would eventually end up with a file so large it
would corrupt itself by becoming too large to open. On the other hand,
not so big a deal with the registry as you would have to create and
delete entries constantly to get it big enough to hurt.

 

[Guest]

how is your vagina doing?

 

[Dave]

Ina nutshell, the registry is a database, and deleting entries in a
database leaves space where the entry was. Compacting databases merely
removes the "dead space". This was important for something like Outlook
Express dbx file as you would eventually end up with a file so large it
would corrupt itself by becoming too large to open. On the other hand, not
so big a deal with the registry as you would have to create and delete
entries constantly to get it big enough to hurt.

That's what I was thinking as I've never seen a registry backup that was any
size at all.
Thanks,
Dave

 

[Bob I]

That's what I was thinking as I've never seen a registry backup that was
any size at all.
Thanks,
Dave

You're welcome, I'm one of those that favors not messing with the
registry unless there is a real issue to be corrected.