Windows Vista crashded and don't accept product key anymore

A very nasty incident happened today. I tried to install AuzenTech HDA
XPlosion to my 32-bit Vista. There were some problems after having installed
AuzenTech's beta drivers. I did scanned the memory in order to find possible
problems in memory. After the Vista's memory test Vista did allow me to log
in, but wanted to have the product key. After having given it, Vista gave me
an error message in hexadecimal form (something linke 0x8000000) and began to
claim that the operating system is not original.

That's normal when you need to reinstall and re-activate Vista. Just call
the activation center number and explain what happened and they will help
you re-activate your copy.

--
Richard G. Harper [MVP Shell/User]
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Dass Spiel ist aus" <Dass Spiel ist > wrote in
message news:5FC656EB-5C4B-48CD-B325-...
>A very nasty incident happened today. I tried to install AuzenTech HDA
> XPlosion to my 32-bit Vista. There were some problems after having
> installed
> AuzenTech's beta drivers. I did scanned the memory in order to find
> possible
> problems in memory. After the Vista's memory test Vista did allow me to
> log
> in, but wanted to have the product key. After having given it, Vista gave
> me
> an error message in hexadecimal form (something linke 0x8000000) and began
> to
> claim that the operating system is not original.
>

"Richard G. Harper" wrote:

> That's normal when you need to reinstall and re-activate Vista. Just call
> the activation center number and explain what happened and they will help
> you re-activate your copy.
>

Thanks for your answer. I'm mainly interested in, if a poorly written device
driver can cause such a mess. Unfortunately MS's help wasn't able to help me
to reinitialize the product, (it is Sunday here). It was impossible to "roll
back" the operating system to the point it was before the installation. There
were three recovery points, but something was missing from the boot segment,
or at least I interpreted the error messages so. I don't think that the copy
of my Vista could be a pirate, because it was purchased to me by my employer
in order to let me use it in my home office.

I think that kind of anti piracy protection is a bit Draconian. I have
plenty of my text and source code locked in the machine.

The key term here is "beta drivers". Unless you have a known good backup
(which you apparently didn't), it's not a good idea to be running beta
anything on your main production PC unless your prepared to deal with the
possible fallout. Doesn't help you now, but lesson learned maybe.

--
----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375
How to Post http://www.dts-l.org/goodpost.htm
http://www.db-pc.com
----------------------------------------------------------------------------------------------------------------------
"Dass Spiel ist aus" <> wrote in
message news:8E70BB62-37B7-4A0C-BD49-...
>
>
> "Richard G. Harper" wrote:
>
>> That's normal when you need to reinstall and re-activate Vista. Just
>> call
>> the activation center number and explain what happened and they will help
>> you re-activate your copy.
>>
>
> Thanks for your answer. I'm mainly interested in, if a poorly written
> device
> driver can cause such a mess. Unfortunately MS's help wasn't able to help
> me
> to reinitialize the product, (it is Sunday here). It was impossible to
> "roll
> back" the operating system to the point it was before the installation.
> There
> were three recovery points, but something was missing from the boot
> segment,
> or at least I interpreted the error messages so. I don't think that the
> copy
> of my Vista could be a pirate, because it was purchased to me by my
> employer
> in order to let me use it in my home office.
>
> I think that kind of anti piracy protection is a bit Draconian. I have
> plenty of my text and source code locked in the machine.
>

"Dave B." wrote:

> The key term here is "beta drivers". Unless you have a known good backup
> (which you apparently didn't), it's not a good idea to be running beta
> anything on your main production PC unless your prepared to deal with the
> possible fallout. Doesn't help you now, but lesson learned maybe.
>

The good thing is, that I use a simple disk mirroring. It is't obviously not
the best backup mechanism in situations like this. I think I need to put the
second disk in another computer that can read NTFS and write the contents to
a USB drive.

Does anyone have better ideas?


> ----
> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
> How to ask a question http://support.microsoft.com/kb/555375
> How to Post http://www.dts-l.org/goodpost.htm
> http://www.db-pc.com
> ----------------------------------------------------------------------------------------------------------------------
> "Dass Spiel ist aus" <> wrote in
> message news:8E70BB62-37B7-4A0C-BD49-...
> >
> >
> > "Richard G. Harper" wrote:
> >
> >> That's normal when you need to reinstall and re-activate Vista. Just
> >> call
> >> the activation center number and explain what happened and they will help
> >> you re-activate your copy.
> >>
> >
> > Thanks for your answer. I'm mainly interested in, if a poorly written
> > device
> > driver can cause such a mess. Unfortunately MS's help wasn't able to help
> > me
> > to reinitialize the product, (it is Sunday here). It was impossible to
> > "roll
> > back" the operating system to the point it was before the installation.
> > There
> > were three recovery points, but something was missing from the boot
> > segment,
> > or at least I interpreted the error messages so. I don't think that the
> > copy
> > of my Vista could be a pirate, because it was purchased to me by my
> > employer
> > in order to let me use it in my home office.
> >
> > I think that kind of anti piracy protection is a bit Draconian. I have
> > plenty of my text and source code locked in the machine.
> >
>
>
>