Vista - Total failure installing Vista Beta 2

I'm trying to upgrade my Windows XP with Vista Beta 2.

I start the setup.exe program, and it starts fine, and gets to the point
where it asks me for my product key.
I enter my "Ultimate edition product key".

I enter the product key, and it switches to the next page (verify license
dialog).
If I click "accept", or just wait a minute, suddenly I'll get a dialog from
the "Microsoft C++ Runtime" telling me the application (setup) has failed.

Here's the actual message:

"Microsoft Visual C++ Runtime Library - Runtime Error! The application has
requested the Runtime to terminate it in an unusual way. Please contact the
application's support team for more information."


If instead I enter a "home basic" product key, I don't get a crash, but the
next dialog in setup tells me that you can't upgrade XP pro to home basic.

So I'd guess it has started looking at the system in preperation for the
upgrade, but something goes wrong?

The system has plenty of available resources (4gb memory, 250 GB free on C:,
etc).

The C++ Runtime error is a result of the product key being hard coded to the
installer. As for the Home Basic setup failure thats a result of the upgrade
path being invalid. XP Professional includes features such Encryption,
Domain Join and additional networking and mobile features which are not
available in the consumer edition of Home Basic. You could try requesting a
new key from MSDN for Ultimate or try the Business Edition key which is a
valid upgrade path from XP Professional.
--
--
Andre
Windows Connected | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

"Charles F McDevitt" <Chuck_McDevitt@m-s-n.com> wrote in message
news:eivZeYvfGHA.1260@TK2MSFTNGP05.phx.gbl...
> I'm trying to upgrade my Windows XP with Vista Beta 2.
>
> I start the setup.exe program, and it starts fine, and gets to the point
> where it asks me for my product key.
> I enter my "Ultimate edition product key".
>
> I enter the product key, and it switches to the next page (verify license
> dialog).
> If I click "accept", or just wait a minute, suddenly I'll get a dialog
> from the "Microsoft C++ Runtime" telling me the application (setup) has
> failed.
>
> Here's the actual message:
>
> "Microsoft Visual C++ Runtime Library - Runtime Error! The application has
> requested the Runtime to terminate it in an unusual way. Please contact
> the application's support team for more information."
>
>
> If instead I enter a "home basic" product key, I don't get a crash, but
> the next dialog in setup tells me that you can't upgrade XP pro to home
> basic.
>
> So I'd guess it has started looking at the system in preperation for the
> upgrade, but something goes wrong?
>
> The system has plenty of available resources (4gb memory, 250 GB free on
> C:, etc).
>
>
>
>
>

"Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
news:O2$61svfGHA.4004@TK2MSFTNGP04.phx.gbl...
> The C++ Runtime error is a result of the product key being hard coded to
> the installer. As for the Home Basic setup failure thats a result of the
> upgrade path being invalid. XP Professional includes features such
> Encryption, Domain Join and additional networking and mobile features
> which are not available in the consumer edition of Home Basic. You could
> try requesting a new key from MSDN for Ultimate or try the Business
> Edition key which is a valid upgrade path from XP Professional.
> --

I don't understand. The installer accepts the product key I'm giving it, and
it's a valid key I just got from MSDN.

The product key works if i use it to do a "clean install" by booting off the
DVD, but I don't want to wipe out my existing system.

I got a business editon key, and it has the same problem.

"Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
news:O2$61svfGHA.4004@TK2MSFTNGP04.phx.gbl...
> The C++ Runtime error is a result of the product key being hard coded to
> the installer. As for the Home Basic setup failure thats a result of the
> upgrade path being invalid. XP Professional includes features such
> Encryption, Domain Join and additional networking and mobile features
> which are not available in the consumer edition of Home Basic. You could
> try requesting a new key from MSDN for Ultimate or try the Business
> Edition key which is a valid upgrade path from XP Professional.

Try generating new keys if that's possible. If that doesn't work... try
contacting MSDN and see if they come up with anything )

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!

--: Original message follows :--
"Charles F McDevitt" <Chuck_McDevitt@m-s-n.com> wrote in message
news:OnrN4w1fGHA.1856@TK2MSFTNGP03.phx.gbl...
>I got a business editon key, and it has the same problem.
>
> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
> news:O2$61svfGHA.4004@TK2MSFTNGP04.phx.gbl...
>> The C++ Runtime error is a result of the product key being hard coded to
>> the installer. As for the Home Basic setup failure thats a result of the
>> upgrade path being invalid. XP Professional includes features such
>> Encryption, Domain Join and additional networking and mobile features
>> which are not available in the consumer edition of Home Basic. You could
>> try requesting a new key from MSDN for Ultimate or try the Business
>> Edition key which is a valid upgrade path from XP Professional.
>
>

You need to report this issue to microsoft.public.msdn.general since they
are the ones responsible for generating the keys.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
"Charles F McDevitt" <Chuck_McDevitt@m-s-n.com> wrote in message
news:OnrN4w1fGHA.1856@TK2MSFTNGP03.phx.gbl...
>I got a business editon key, and it has the same problem.
>
> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
> news:O2$61svfGHA.4004@TK2MSFTNGP04.phx.gbl...
>> The C++ Runtime error is a result of the product key being hard coded to
>> the installer. As for the Home Basic setup failure thats a result of the
>> upgrade path being invalid. XP Professional includes features such
>> Encryption, Domain Join and additional networking and mobile features
>> which are not available in the consumer edition of Home Basic. You could
>> try requesting a new key from MSDN for Ultimate or try the Business
>> Edition key which is a valid upgrade path from XP Professional.
>
>

There is nothing wrong with the key.


"Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
news:%23kxb7e2fGHA.1324@TK2MSFTNGP04.phx.gbl...
> You need to report this issue to microsoft.public.msdn.general since they
> are the ones responsible for generating the keys.

I did try getting a new key (Business edition). Again, the key was
accepted,
but then setup crashed.


"Zack Whittaker" <admin@zacknet.co.uk> wrote in message
news:u$E4w91fGHA.1204@TK2MSFTNGP02.phx.gbl...
> Try generating new keys if that's possible. If that doesn't work... try
> contacting MSDN and see if they come up with anything )
>
> --

Well its an issue with the ISO then or somebody voodooed you. Download the
ISO again or burn the existing ISO and try installing.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
"Charles F McDevitt" <Chuck_McDevitt@m-s-n.com> wrote in message
news:OHSx%23p2fGHA.4792@TK2MSFTNGP03.phx.gbl...
> There is nothing wrong with the key.
>
>
> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
> news:%23kxb7e2fGHA.1324@TK2MSFTNGP04.phx.gbl...
>> You need to report this issue to microsoft.public.msdn.general since they
>> are the ones responsible for generating the keys.
>
>

Imho this might be a driver problem.

--
Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net