- XP Home Activation - Re-Activation
- Posted by Darryl on October 11th, 2005
I've just had to repair an XP Home installation. Corrupted files meant I had
to put back the files in the Windows\system32\config directory. After I had
the system up and going again, XP tells me it requires activation .... why???
None of the hardware changed. It was reinstalled over the top of the old
one, and wasn't a clean install. It was a repair using restore point snapshot
files to get the system working. Nothing has changed!!
Can anyone shed some light on this, or suggest a way around it?
Regards
Darryl.
- Posted by kurttrail on October 11th, 2005
"Darryl" <Darryl@discussions.microsoft.com> wrote in message
news:0965CBF1-E99C-493B-B50E-070B1B83E371@microsoft.com...
> I've just had to repair an XP Home installation. Corrupted files meant
> I had
> to put back the files in the Windows\system32\config directory. After
> I had
> the system up and going again, XP tells me it requires activation ....
> why???
>
> None of the hardware changed. It was reinstalled over the top of the
> old
> one, and wasn't a clean install. It was a repair using restore point
> snapshot
> files to get the system working. Nothing has changed!!
>
> Can anyone shed some light on this, or suggest a way around it?
Have you tried activating it yet?
--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"
- Posted by Mistoffolees on October 11th, 2005
Darryl wrote:
> I've just had to repair an XP Home installation. Corrupted files meant I had
> to put back the files in the Windows\system32\config directory. After I had
> the system up and going again, XP tells me it requires activation .... why???
>
> None of the hardware changed. It was reinstalled over the top of the old
> one, and wasn't a clean install. It was a repair using restore point snapshot
> files to get the system working. Nothing has changed!!
>
> Can anyone shed some light on this, or suggest a way around it?
As far as Windows is concerned, changing some of the files
by re-installing them probably altered the checksum enough
to require a re-activation. How many files were replaced in
the repair process if it did not amount to a re-installation?
A very fine point. But since activation/re-activation is a
way of life with Windows XP, don't argue the point and just
do it.
- Posted by Eric on October 11th, 2005
Read this information on how to save the activation files so that you can
restore them and avoid reactivating - if no hardware has changed -
http://www.pcbuyerbeware.co.uk/RecoveringXP.htm#self
Eric,
PC Buyer Beware!
http://www.pcbuyerbeware.co.uk/
"Mistoffolees" wrote:
>
> Darryl wrote:
> > I've just had to repair an XP Home installation. Corrupted files meant I had
> > to put back the files in the Windows\system32\config directory. After I had
> > the system up and going again, XP tells me it requires activation .... why???
> >
> > None of the hardware changed. It was reinstalled over the top of the old
> > one, and wasn't a clean install. It was a repair using restore point snapshot
> > files to get the system working. Nothing has changed!!
> >
> > Can anyone shed some light on this, or suggest a way around it?
>
>
> As far as Windows is concerned, changing some of the files
> by re-installing them probably altered the checksum enough
> to require a re-activation. How many files were replaced in
> the repair process if it did not amount to a re-installation?
> A very fine point. But since activation/re-activation is a
> way of life with Windows XP, don't argue the point and just
> do it.
>
>
- Posted by Darryl on October 11th, 2005
"Mistoffolees" wrote:
>
> Darryl wrote:
> > I've just had to repair an XP Home installation. Corrupted files meant I had
> > to put back the files in the Windows\system32\config directory. After I had
> > the system up and going again, XP tells me it requires activation .... why???
> >
> > None of the hardware changed. It was reinstalled over the top of the old
> > one, and wasn't a clean install. It was a repair using restore point snapshot
> > files to get the system working. Nothing has changed!!
> >
> > Can anyone shed some light on this, or suggest a way around it?
>
>
> As far as Windows is concerned, changing some of the files
> by re-installing them probably altered the checksum enough
> to require a re-activation. How many files were replaced in
> the repair process if it did not amount to a re-installation?
> A very fine point. But since activation/re-activation is a
> way of life with Windows XP, don't argue the point and just
> do it.
>
>
Sorry, I should have read what I wrote before I posted it. It 'wasn't' a
repair install. The files in the directory I mentioned were corrupt. I
replaced the corrupt files with copies created by XP System Restore, in the
snapshot directory, to get the system up and running again.
This is why I'm surprised. The files that were replaced, were replaced with
files created by the XP system itself. The files were in
Windows\system32\config ... SAM,SECURITY,SYSTEM,SOFTWARE and DEFAULT. All
were replaced with backups created by System Restore.
Obviously I have no choice but to reactivate ... but it's an unnecessary
pain, and considering it's an OEM version, it's a waste of one of the three
valid activations.
Thanks for your reply though.
Darryl
