Activation failure

I am trying to instal Beta 2 on a Dell Latitude D610. I've done a clean
install (creating a new partition each time) two times, and both times as
soon as I log in, I am presented with the Windows Activation screen and given
three choices:

1. Buy new Product Key
2. Retype Product Key
3. Activate Windwos online

When I choose options 2 or 3, the machine stalls for about 5 minutes and
returns this error:

"Autenication failed with the following error:

0X800705B4"

The first option will bring up I.E. and ask me to buy a license.

--
--
Whatever you do, take care of your shoes.

This can be a timeout issue where it's not reaching the server or not
reaching the server it time.
It could be firewall issue, it could be a slow traffic issue.
--
--
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


"Hiland" <Hiland@discussions.microsoft.com> wrote in message
news:ACB1B6D9-DF9D-4A98-B8CA-58C2160852B9@microsoft.com...

>I am trying to instal Beta 2 on a Dell Latitude D610. I've done a clean
> install (creating a new partition each time) two times, and both times as
> soon as I log in, I am presented with the Windows Activation screen and
> given
> three choices:
>
> 1. Buy new Product Key
> 2. Retype Product Key
> 3. Activate Windwos online
>
> When I choose options 2 or 3, the machine stalls for about 5 minutes and
> returns this error:
>
> "Autenication failed with the following error:
>
> 0X800705B4"
>
> The first option will bring up I.E. and ask me to buy a license.
>
> --
> --
> Whatever you do, take care of your shoes.

I am experiencing the same error after i try to login.

'Activate windows online now' and 'Retype your product key' timeout with
that error
'Buy a new product key online' pops up an internet explorer but no way to
activate.
The 2 options under other ways don't work either and timeout with the same
error.

I think this problem can be backtraced to the system time before
installation and after.
I had a windows XP computer installed for testing purposes and forgot to set
the date to todays date. (it was somewhere in 2004)
During the configuration of Vista i set the date to Today.

My guess is that the installation took the date when i submitted my product
key (somewhere in 2004) and thinks i have vista beta2 installed for 2 years
now.
Which results in the expiration.

As a follow up i see i can login as administrator in safe mode cause
activation status is not available in safe mode.

Hopefully i can do something there to fix the error.

"Justin Doek" wrote:

> I am experiencing the same error after i try to login.
>
> 'Activate windows online now' and 'Retype your product key' timeout with
> that error
> 'Buy a new product key online' pops up an internet explorer but no way to
> activate.
> The 2 options under other ways don't work either and timeout with the same
> error.
>
> I think this problem can be backtraced to the system time before
> installation and after.
> I had a windows XP computer installed for testing purposes and forgot to set
> the date to todays date. (it was somewhere in 2004)
> During the configuration of Vista i set the date to Today.
>
> My guess is that the installation took the date when i submitted my product
> key (somewhere in 2004) and thinks i have vista beta2 installed for 2 years
> now.
> Which results in the expiration.
>
>

Yes, if your date and time settings are not correct, it can cause problems.
--
--
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

"Justin Doek" <Justin Doek@discussions.microsoft.com> wrote in message
news:77376AED-2F67-4552-81FA-1C0FC4923D75@microsoft.com...

>I am experiencing the same error after i try to login.
>
> 'Activate windows online now' and 'Retype your product key' timeout with
> that error
> 'Buy a new product key online' pops up an internet explorer but no way to
> activate.
> The 2 options under other ways don't work either and timeout with the same
> error.
>
> I think this problem can be backtraced to the system time before
> installation and after.
> I had a windows XP computer installed for testing purposes and forgot to
> set
> the date to todays date. (it was somewhere in 2004)
> During the configuration of Vista i set the date to Today.
>
> My guess is that the installation took the date when i submitted my
> product
> key (somewhere in 2004) and thinks i have vista beta2 installed for 2
> years
> now.
> Which results in the expiration.
>
>

I tried loggin in as Admin in safe mode... I get booted out due to the
activation error.


--
--
Whatever you do, take care of your shoes.


"Justin Doek" wrote:

> As a follow up i see i can login as administrator in safe mode cause
> activation status is not available in safe mode.
>
> Hopefully i can do something there to fix the error.
>
> "Justin Doek" wrote:
>

My installation hangs when I enter the key that Microsoft provided me. If I
enter my XP Pro key, it tells me right away that it's invalid. Any ideas why?

I feel this area is a BUG.
See my Blog: http://spaces.msn.com/ce-aus/
Where I am blogging my Vista (Beta 2) installation experiences. So far
VPC
VMWare
VIA ITX M1000
-This last one I ran into similar problems as above.
-I am doing a complete reinstall
-Suggestions:
New key for subsequent installs
Disable "Activate as soon as connects"
Don't change date until after activation

--
David Jones
Senior Lecturer
School of Electrical & Computer Engineering
RMIT University
+61 3 99255318


"Andre Da Costa [Extended64]" wrote:

> Yes, if your date and time settings are not correct, it can cause problems.
> --
> --
> 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
>
> "Justin Doek" <Justin Doek@discussions.microsoft.com> wrote in message
> news:77376AED-2F67-4552-81FA-1C0FC4923D75@microsoft.com...

>
>
>

"David Jones" wrote:

> I feel this area is a BUG.
> See my Blog: http://spaces.msn.com/ce-aus/
> Where I am blogging my Vista (Beta 2) installation experiences. So far
> VPC
> VMWare
> VIA ITX M1000
> -This last one I ran into similar problems as above.
> -I am doing a complete reinstall
> -Suggestions:
> New key for subsequent installs
> Disable "Activate as soon as connects"
> Don't change date until after activation
>
> --
> David Jones
> Senior Lecturer
> School of Electrical & Computer Engineering
> RMIT University
> +61 3 99255318
>
>
> "Andre Da Costa [Extended64]" wrote:
>

'Activate windows online now' and 'Retype your product key' timeout with
that error
'Buy a new product key online' pops up an internet explorer but no way to
activate.
The 2 options under other ways don't work either and timeout with the same
error.

I think this problem can be backtraced to the system time before
installation and after.
I had a windows XP computer installed for testing purposes and forgot to set
the date to todays date. (it was somewhere in 2004)
During the configuration of Vista i set the date to Today.

My guess is that the installation took the date when i submitted my product
key (somewhere in 2004) and thinks i have vista beta2 installed for 2 years
now.
Which results in the expiration.


This is very similar to the issue I am experiencing.

You have to understand that Vista will be installed on a lot of new machines
- and it is not uncommon for the date and time to be wrong on initial
install. I have done this many times - as have many system admins I know.

You can't have a scenario where the wrong date and time locks people out
like this - it makes no sense - partricularly where the actual activation
process is itself currently broken.

"David Jones" wrote:

> I feel this area is a BUG.
> See my Blog: http://spaces.msn.com/ce-aus/
> Where I am blogging my Vista (Beta 2) installation experiences. So far
> VPC
> VMWare
> VIA ITX M1000
> -This last one I ran into similar problems as above.
> -I am doing a complete reinstall
> -Suggestions:
> New key for subsequent installs
> Disable "Activate as soon as connects"
> Don't change date until after activation
>
> --
> David Jones
> Senior Lecturer
> School of Electrical & Computer Engineering
> RMIT University
> +61 3 99255318
>
>
> "Andre Da Costa [Extended64]" wrote:
>

> I feel this area is a BUG.
> See my Blog: http://spaces.msn.com/ce-aus/
> Where I am blogging my Vista (Beta 2) installation experiences. So far
> VPC
> VMWare
> VIA ITX M1000
> -This last one I ran into similar problems as above.
> -I am doing a complete reinstall
> -Suggestions:
> New key for subsequent installs
> Disable "Activate as soon as connects"
> Don't change date until after activation
>
> --
> David Jones
> Senior Lecturer
> School of Electrical & Computer Engineering
> RMIT University
> +61 3 99255318
>
>
> "Andre Da Costa [Extended64]" wrote:
>

'Activate windows online now' and 'Retype your product key' timeout with
that error
'Buy a new product key online' pops up an internet explorer but no way to
activate.
The 2 options under other ways don't work either and timeout with the same
error.

I think this problem can be backtraced to the system time before
installation and after.
I had a windows XP computer installed for testing purposes and forgot to set
the date to todays date. (it was somewhere in 2004)
During the configuration of Vista i set the date to Today.

My guess is that the installation took the date when i submitted my product
key (somewhere in 2004) and thinks i have vista beta2 installed for 2 years
now.
Which results in the expiration.


This is very similar to the issue I am experiencing.

You have to understand that Vista will be installed on a lot of new machines
- and it is not uncommon for the date and time to be wrong on initial
install. I have done this many times - as have many system admins I know.

You can't have a scenario where the wrong date and time locks people out
like this - it makes no sense - partricularly where the actual activation
process is itself currently broken.