corrupted registry

Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T


--
When we ask for advice, we are usually looking for an accomplice.
--Charles Varlet de La Grange

On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then the only
application affected is the one that relies on that registry key. To
resolve it, just re-install that particular application (or repair
install) and everything should be back to normal.

Some registry cleaners might aid you to delete that corrupted registry
key and I suggest try using CCleaner to see if it fixes it.

Now this is all in generality so if you tell us what made you think that
registry is corrupted? there is a misconception here on these
newsgroups that when there is a problem with a "registry" you won't be
able to boot the machine and all that non sense. This is not true
because "Registry" is not just one file. There are 1000s of registry
keys/files and one or two might be corrupted but it is not the end of
the world.




--
With over 500 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 04/06/2017 09:41 AM, Good Guy wrote:
On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then the only
application affected is the one that relies on that registry key. To
resolve it, just re-install that particular application (or repair
install) and everything should be back to normal.

Some registry cleaners might aid you to delete that corrupted registry
key and I suggest try using CCleaner to see if it fixes it.

Now this is all in generality so if you tell us what made you think that
registry is corrupted? there is a misconception here on these
newsgroups that when there is a problem with a "registry" you won't be
able to boot the machine and all that non sense. This is not true
because "Registry" is not just one file. There are 1000s of registry
keys/files and one or two might be corrupted but it is not the end of
the world.

Hi Guy,

It is not just one program having issues and the issue
is growing. The motherboard the customer is using is
over 15 years old. I condemned it for that and other
reasons

His hard drive and DVD drive a less than 6 months old,
so I will reuse that and his w7 key to rebuild him.

So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?

-)T

On 06/04/2017 18:00, T wrote:


So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?



Yes. If windows is dodgy then it is best to re-install it from scratch
by wiping the disk clean and starting from ground zero. Make sure you
have compiled a list of apps and their serial numbers so that you don't
go around chasing them.




--
With over 500 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T

The recovery *concept* for this, is prefaced on having
an operational System Restore. Restore Points are supposed
to capture a backup copy of the registry for you.

The repair procedure basically consists of two steps:

1) With the OS offline, copy the "empty set" of registries
which sit in the OS partition. These are a set of registries
that know nothing about the user installed programs. As such,
these registries are *useless* for ordinary work. But,
they allow the OS to be brought upright. It'll boot.

2) Once the OS is bootable (by virtual of the empty but
working registry file set), now you can use System Restore,
and restore the last working Restore Point. That puts fully
loaded registries, in place of the empty ones you just fitted.

Note that, Restore Points can be recovered by rstrui either
in Safe Mode or in regular boot mode. However, a restore attempt
in Safe Mode has no undo. It's all or nothing. A restore done
in regular OS mode, you can undo it again if you need to.

If the user has turned off System Restore (mine is off right now),
then you're screwed. Sure, you can load the empty registry files
for the user, but they're not fully functional. Program settings
would be lost and so on. People who turn off SR, are those who
use a whole partition backup scheme for safety. I have backups,
but I don't make a backup every day.

https://support.microsoft.com/en-us/...-from-starting

(If the size of System Volume Information is zero, that's
a hint you're screwed.)

So that's one _conceptual_ way to fix it.

*******

Now, in principle, "File History" could have old copies
of files in it, but what are the odds that is set up. There
are two schemes for that, one relying on System Restore, another
relying on some build-in Windows backup scheme (uses an external
drive). So that's another potential source of files. The question
there would be, how do you gain offline access to File History ???
The OS probably has to be running for something like that to work.

*******

You can only do a "Repair" install, from a running Win7 OS. You
execute setup.exe off the DVD, and that kicks it off. How could
it migrate registry contents, if the registry is bad ? And if you
used some empty registry files to bring the OS upright, how
could migration of empty registry files help ? Lotsa questions
there.

*******

The last time I looked, the set of files for the Registry
had grown larger and larger. Some of the files looked like
they were for journaling. This is supposed to make the
registry recoverable automatically (rollback changes or
something). Older OSes didn't seem to have such protection.

Paul

On 4/6/2017 10:00 AM, T wrote:
On 04/06/2017 09:41 AM, Good Guy wrote:
On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then the only
application affected is the one that relies on that registry key. To
resolve it, just re-install that particular application (or repair
install) and everything should be back to normal.

Some registry cleaners might aid you to delete that corrupted registry
key and I suggest try using CCleaner to see if it fixes it.

Now this is all in generality so if you tell us what made you think that
registry is corrupted? there is a misconception here on these
newsgroups that when there is a problem with a "registry" you won't be
able to boot the machine and all that non sense. This is not true
because "Registry" is not just one file. There are 1000s of registry
keys/files and one or two might be corrupted but it is not the end of
the world.

Hi Guy,

It is not just one program having issues and the issue
is growing. The motherboard the customer is using is
over 15 years old. I condemned it for that and other
reasons

His hard drive and DVD drive a less than 6 months old,
so I will reuse that and his w7 key to rebuild him.

So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?

-)T
sounds to me like your systems file is corrupt. The machine keeps
backups right in the same folder or one folder over , And you can just
then do a rename file swap thing, Then reboot it. Its in your Windows
folder, under system32 folder, inside the config folder. In there, is
your system files. Should be about 17mb or so in size... It runs from
config folder. there is a extra one, in there somewhere, and should be
there with maybe another folders name that it is in. or a bkp
extension. You can tell by the size of the file, should be about the
same. There are logs that tell you when it was changed. Set your dates
to dates created, so you can use that and size to determine it from.
You can use the event viewer if you can still use the windows, to
determine the error that took its place. Before it messed up that is.

If the motherboard has a crack in it, nothing you do will work out, But
i don't think thats your problem, somehow older motherboards last
longer. I think somehow, the system file corrupted itself. And thats
why, you have so much trouble with it. So if you can swap that file,
with its backup file, it may start up just fine... And once you do
that and it starts up fine, then you can check your registry...

On 04/06/2017 11:05 AM, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T





Try a System Restore

On 4/6/2017 10:00 AM, T wrote:
On 04/06/2017 09:41 AM, Good Guy wrote:
On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then the only
application affected is the one that relies on that registry key. To
resolve it, just re-install that particular application (or repair
install) and everything should be back to normal.

Some registry cleaners might aid you to delete that corrupted registry
key and I suggest try using CCleaner to see if it fixes it.

Now this is all in generality so if you tell us what made you think that
registry is corrupted? there is a misconception here on these
newsgroups that when there is a problem with a "registry" you won't be
able to boot the machine and all that non sense. This is not true
because "Registry" is not just one file. There are 1000s of registry
keys/files and one or two might be corrupted but it is not the end of
the world.

Hi Guy,

It is not just one program having issues and the issue
is growing. The motherboard the customer is using is
over 15 years old. I condemned it for that and other
reasons

His hard drive and DVD drive a less than 6 months old,
so I will reuse that and his w7 key to rebuild him.

So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?

-)T

sounds to me like your systems file is corrupt. The machine keeps
backups right in the same folder or one folder over , And you can just
then do a rename file swap thing, Then reboot it. Its in your Windows
folder, under system32 folder, inside the config folder. In there, is
your system files. Should be about 17mb or so in size... It runs from
config folder. there is a extra one, in there somewhere, and should be
there with maybe another folders name that it is in. or a bkp
extension. You can tell by the size of the file, should be about the
same. There are logs that tell you when it was changed. Set your dates
to dates created, so you can use that and size to determine it from. You
can use the event viewer if you can still use the windows, to determine
the error that took its place. Before it messed up that is.

If the motherboard has a crack in it, nothing you do will work out, But
i don't think thats your problem, somehow older motherboards last
longer. I think somehow, the system file corrupted itself. And thats
why, you have so much trouble with it. So if you can swap that file,
with its backup file, it may start up just fine... And once you do
that and it starts up fine, then you can check your registry...

We use VIT, cleaner, its free, and it will knock your socks off. Its
SMART.... Good software... But so is getting rid of malware. for
that, you need, novirusthanks stuff.

On 04/06/2017 10:08 AM, Good Guy wrote:
Make sure you have compiled a list of apps and their serial numbers so
that you don't go around chasing them.

Hi Guy,

Chuckle. It is always a trip trying to get those
out of a customer! I make as many screen shots as
possible. I also, with the customer's permission,
keep encrypted copies of their serial numbers,
passwords, etc..

I can' tell you how many times I get call "What is my
wireless password?"

-T

On 04/06/2017 11:10 AM, Paul wrote:
T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T

The recovery *concept* for this, is prefaced on having
an operational System Restore. Restore Points are supposed
to capture a backup copy of the registry for you.

The repair procedure basically consists of two steps:

1) With the OS offline, copy the "empty set" of registries
which sit in the OS partition. These are a set of registries
that know nothing about the user installed programs. As such,
these registries are *useless* for ordinary work. But,
they allow the OS to be brought upright. It'll boot.

2) Once the OS is bootable (by virtual of the empty but
working registry file set), now you can use System Restore,
and restore the last working Restore Point. That puts fully
loaded registries, in place of the empty ones you just fitted.

Note that, Restore Points can be recovered by rstrui either
in Safe Mode or in regular boot mode. However, a restore attempt
in Safe Mode has no undo. It's all or nothing. A restore done
in regular OS mode, you can undo it again if you need to.

If the user has turned off System Restore (mine is off right now),
then you're screwed. Sure, you can load the empty registry files
for the user, but they're not fully functional. Program settings
would be lost and so on. People who turn off SR, are those who
use a whole partition backup scheme for safety. I have backups,
but I don't make a backup every day.

https://support.microsoft.com/en-us/...-from-starting


(If the size of System Volume Information is zero, that's
a hint you're screwed.)

So that's one _conceptual_ way to fix it.

*******

Now, in principle, "File History" could have old copies
of files in it, but what are the odds that is set up. There
are two schemes for that, one relying on System Restore, another
relying on some build-in Windows backup scheme (uses an external
drive). So that's another potential source of files. The question
there would be, how do you gain offline access to File History ???
The OS probably has to be running for something like that to work.

*******

You can only do a "Repair" install, from a running Win7 OS. You
execute setup.exe off the DVD, and that kicks it off. How could
it migrate registry contents, if the registry is bad ? And if you
used some empty registry files to bring the OS upright, how
could migration of empty registry files help ? Lotsa questions
there.

*******

The last time I looked, the set of files for the Registry
had grown larger and larger. Some of the files looked like
they were for journaling. This is supposed to make the
registry recoverable automatically (rollback changes or
something). Older OSes didn't seem to have such protection.

Paul


Hi Paul,

This presumes the hardware is good. I condemned the
hardware. The stinker sputters trying to load
a Linux Live DVD.

But, 95% of the time it is software, which does throw me
off when I get a legitimate hardware issue.

Loved the write up. Thank you!

-T

On 04/06/2017 04:56 PM, philo wrote:
On 04/06/2017 11:05 AM, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T





Try a System Restore

Bad hardware.

On 04/07/2017 03:32 PM, T wrote:
On 04/06/2017 04:56 PM, philo wrote:
On 04/06/2017 11:05 AM, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T





Try a System Restore

Bad hardware.


Aha!

T news 16:05:06 GMT in alt.windows7.general, wrote:

Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?


Many thanks,
-T



*sigh* I see you're playing computer tech again. Have you gotten any
certifications under your belt yet, or, are you mooching off of usenet
posters and/or search engine results and charging the customer for your
learning? You really do give actual techs a bad name, man.


--
https://tekrider.net/pages/david-brooks-stalker.php

Cats must jump on the kitchen counter and make off with the roast
chicken.

T news 2017 17:00:15 GMT in alt.windows7.general, wrote:

On 04/06/2017 09:41 AM, Good Guy wrote:
On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then
the only application affected is the one that relies on that
registry key. To resolve it, just re-install that particular
application (or repair install) and everything should be back to
normal.

Some registry cleaners might aid you to delete that corrupted
registry key and I suggest try using CCleaner to see if it fixes
it.

Now this is all in generality so if you tell us what made you
think that registry is corrupted? there is a misconception here
on these newsgroups that when there is a problem with a
"registry" you won't be able to boot the machine and all that non
sense. This is not true because "Registry" is not just one file.
There are 1000s of registry keys/files and one or two might be
corrupted but it is not the end of the world.

Hi Guy,

It is not just one program having issues and the issue
is growing. The motherboard the customer is using is
over 15 years old. I condemned it for that and other
reasons

His hard drive and DVD drive a less than 6 months old,
so I will reuse that and his w7 key to rebuild him.

So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?

-)T


Damn. Dude, seriously, stop playing tech when you aren't actually
one. You really do give actual technicians a bad name. You're like
the shady tree mechanic.


--
https://tekrider.net/pages/david-brooks-stalker.php

My life has Chinese music torture playing in the background.

On 06/24/2017 08:22 PM, Diesel wrote:
T news 2017 17:00:15 GMT in alt.windows7.general, wrote:

On 04/06/2017 09:41 AM, Good Guy wrote:
On 06/04/2017 17:05, T wrote:
Hi All,

w7-pro x32

Am I correct, if I have a corrupted registry (can't even
open it and lots of errors regarding it in the logs),
it is a full reinstall, not an in place reinstall?




No you are not correct. If you have a corrupted registry then
the only application affected is the one that relies on that
registry key. To resolve it, just re-install that particular
application (or repair install) and everything should be back to
normal.

Some registry cleaners might aid you to delete that corrupted
registry key and I suggest try using CCleaner to see if it fixes
it.

Now this is all in generality so if you tell us what made you
think that registry is corrupted? there is a misconception here
on these newsgroups that when there is a problem with a
"registry" you won't be able to boot the machine and all that non
sense. This is not true because "Registry" is not just one file.
There are 1000s of registry keys/files and one or two might be
corrupted but it is not the end of the world.

Hi Guy,

It is not just one program having issues and the issue
is growing. The motherboard the customer is using is
over 15 years old. I condemned it for that and other
reasons

His hard drive and DVD drive a less than 6 months old,
so I will reuse that and his w7 key to rebuild him.

So basically, since Windows itself is having issues with
the registry, I was thinking that I was looking at a full
reinstall after upgrading the hardware. Your thoughts?

-)T


Damn. Dude, seriously, stop playing tech when you aren't actually
one. You really do give actual technicians a bad name. You're like
the shady tree mechanic.



What an ass hole!