All XP Machines now failing WGA test

[Daave]

Hello,

I have a remote site that has around 50 XP machines. All these
machines were installed with a valid XP OEM key.

{with the subsequent clarification

Each machine was installed WITH ITS OWN KEY.

The error message is
"The product key found on this computer is not valid for use in your
region."

Since about over a month ago, they are now all stating they are
counterfeit windows and do not pass WGA.
It says windows license not valid for current location.

What's going on??

XP Home or Pro?

Generic OEM or branded OEM?

Where did these 50 keys come from? I ask because it sounds like the
"valid XP OEM key" you *originally* mentioned might in fact be a banned
VLK!

Makes and models of PCs?

 

[AndyTC]

{with the subsequent clarification



XP Home or Pro?

Generic OEM or branded OEM?

Where did these 50 keys come from? I ask because it sounds like the
"valid XP OEM key" you *originally* mentioned might in fact be a banned
VLK!

Makes and models of PCs?

I never said it was a SINGLE key.
I said each machine with A VALID OEM KEY. That doesn't mean it was the
same key. I should have put IT'S instead of A.
Geez.
So is microsoft telling me where I can use my machine? I buy it in the
US, but I can't take it overseas and pass validation?
That's ridiculous.

These are XP pro machines, bought from HP.

 

[Unknown]

Your best bet-------Call Microsoft!

No it's not. Each machine was installed WITH ITS OWN KEY.

 

[Bennett Marco]

Each machine was installed WITH ITS OWN KEY.

The error message is
"The product key found on this computer is not valid for use in your
region."

ONE REPLY IS ENOUGH! Evreryone will see it.

 

[B.D.©]

I never said it was a SINGLE key.
I said each machine with A VALID OEM KEY. That doesn't mean it was the
same key. I should have put IT'S instead of A.
Geez.
So is microsoft telling me where I can use my machine? I buy it in the
US, but I can't take it overseas and pass validation?
That's ridiculous.

These are XP pro machines, bought from HP.

I suspect this is something that the US government is going to have to
work out with either Microsoft or HP. WGA does in fact verify the
region the product is being used in. There is a way of getting rid of
the WGA message but that doesn't solve the problem and since these are
US Government machines I would be somewhat loathe to provide that solution.
I can understand your frustration with people thinking it was only a
single OEM license, however your original post could have lead people to
that conclusion if they missed the US Government part.

 

[Shenan Stanley]

I have a remote site that has around 50 XP machines. All these
machines were installed with a valid XP OEM key.

Since about over a month ago, they are now all stating they are
counterfeit windows and do not pass WGA.
It says windows license not valid for current location.

What's going on??

Clarify:

"All these machines were installed with a valid XP OEM key"

They were all installed with the same valid OEM product key?

Each machine was installed WITH ITS OWN KEY.

The error message is
"The product key found on this computer is not valid for use in your
region."

Easy there. You are the one with the confusing choice of wording. ;-)

However - posting the exact message word-for-word was a wise idea (and
better than the original "It says windows license not valid for current
location") - as your interpretation (as seen by the responses in this groups
alone) will not always be the same as everyone elses.

Here's what I think you should do... Run Magic JellyBean KeyFinder on two or
three of the machines with the issue. Compare the keys.

I know - I know - you said "Each machine was installed WITH ITS OWN KEY",
great - do this anyway. All you have to lose is time and you are losing
that sitting there fuming over it. ;-) If I am wrong - so be it - but you
might find your way out if you do it.

If you kept the original install from the factory - it was possibly done
with a VLK from the factory. If the results from your Magic JellyBean
KeyFinder are all the same - that is most likely the situation you are in.

Seems that VLK could be what is known as a geographically blocked PID. A
"Geographically blocked PID" is a Volume License Key that is valid, but was
licensed solely to a corporation or larger enterprise/business. If that
business/larger enterprise gives its consent to block that VLK - it's done.

It's not unfixable. Assuming the stickers on the machines are still in
place and legitimate (you were not screwed by the original purchase) you can
try changing the prioduct key on one of the 'victim' machines to the one
found on its individual sticker using:

The Genuine Advantage Product Key Update Tool is only valid for
users attempting to change their current non-genuine Product Key
to a genuine COA sticker or genuine Product Key - all without a
reinstall!
http://go.microsoft.com/fwlink/?LinkId=50346&clcid=0x409

In case (I am wrong and you were right and each machine has its own
individual product key from its own sticker already OR if I was right and
the product key change tool fails you) - you have one other option. The
true support for that copy of Windows XP is the OEM you purchased the
machines from. HP, Dell, Gateway, Lenovo, etc. You should contact them
immediately and tell them what is happening, where you are and what you have
done to correct the situation. They should provide you with at least a new
key if not media to fix the situation.

Just for fun - what happens here:
http://www.microsoft.com/genuine/do...6c140663-a8a2-453a-b9c2-41ec490a8d03&submit=1

 

[Daave]

I never said it was a SINGLE key.
I said each machine with A VALID OEM KEY.

No, you didn't. You stated, "All these machines were installed with a
valid XP OEM key."

That doesn't mean it was the same key.

Maybe to you, but to the rest of us, that's what it sounded like.

I should have put IT'S instead of A.
Geez.

Don't be upset with others if you're the one not being clear.

So is microsoft telling me where I can use my machine?
No.

I buy it in the US, but I can't take it overseas and pass validation?

No one said that.

That's ridiculous.

Yes, it would be ridiculous.

These are XP pro machines, bought from HP.

Okay, that's useful information. (It would have saved some time had you
stated that from the outset.) What about models and model numbers?

Once more:

Where did these 50 keys come from? Did these HPs all come with XP Pro
pre-installed? That is, do they have Certificate of Authenticity (COA)
stickers on them mentioning Windows XP Professional along with the
Product Key? Are these the keys that were used? Or did you or someone
else use HP's golden master keys for XP Pro? Or some other keys? Did you
or someone else install or reinstall XP Pro on these PCs? And if so, how
was it done? With HP's method? And if so, what method did they
provide -- XP Pro installation CD, HP recovery CD, or hidden recovery
partition? Or did you use a *generic* OEM Windows XP Pro installation
CD? Unless you provide details, no one will be able to help you!

 

[Shenan Stanley]

I have a remote site that has around 50 XP machines. All these
machines were installed with a valid XP OEM key.

Since about over a month ago, they are now all stating they are
counterfeit windows and do not pass WGA.
It says windows license not valid for current location.

What's going on??

Clarify:

"All these machines were installed with a valid XP OEM key"

They were all installed with the same valid OEM product key?

Each machine was installed WITH ITS OWN KEY.

The error message is
"The product key found on this computer is not valid for use in your
region.

Easy there. You are the one with the confusing choice of wording.
;-)
However - posting the exact message word-for-word was a wise idea
(and better than the original "It says windows license not valid
for current location") - as your interpretation (as seen by the
responses in this groups alone) will not always be the same as
everyone elses.
Here's what I think you should do... Run Magic JellyBean KeyFinder
on two or three of the machines with the issue. Compare the keys.

I know - I know - you said "Each machine was installed WITH ITS OWN
KEY", great - do this anyway. All you have to lose is time and you
are losing that sitting there fuming over it. ;-) If I am wrong -
so be it - but you might find your way out if you do it.

If you kept the original install from the factory - it was possibly
done with a VLK from the factory. If the results from your Magic
JellyBean KeyFinder are all the same - that is most likely the
situation you are in.
Seems that VLK could be what is known as a geographically blocked
PID. A "Geographically blocked PID" is a Volume License Key that
is valid, but was licensed solely to a corporation or larger
enterprise/business. If that business/larger enterprise gives its
consent to block that VLK - it's done.
It's not unfixable. Assuming the stickers on the machines are
still in place and legitimate (you were not screwed by the original
purchase) you can try changing the prioduct key on one of the
'victim' machines to the one found on its individual sticker using:

The Genuine Advantage Product Key Update Tool is only valid for
users attempting to change their current non-genuine Product Key
to a genuine COA sticker or genuine Product Key - all without a
reinstall!
http://go.microsoft.com/fwlink/?LinkId=50346&clcid=0x409

In case (I am wrong and you were right and each machine has its own
individual product key from its own sticker already OR if I was
right and the product key change tool fails you) - you have one
other option. The true support for that copy of Windows XP is the
OEM you purchased the machines from. HP, Dell, Gateway, Lenovo,
etc. You should contact them immediately and tell them what is
happening, where you are and what you have done to correct the
situation. They should provide you with at least a new key if not
media to fix the situation.
Just for fun - what happens here:
http://www.microsoft.com/genuine/do...6c140663-a8a2-453a-b9c2-41ec490a8d03&submit=1

Other people - similar situation (heck - even mentioned HP!)
http://social.microsoft.com/Forums/...p/thread/4701a7c1-7096-421b-866c-57cb70225dcb

This 'real world' stuff, it sucks. On that we agree. ;-P

 

[AndyTC]

"WGA does in fact verify the region the product is being used in."

So is it possible to have a valid key invalidated because the country it
is being used in?

 

[AndyTC]

Other people - similar situation (heck - even mentioned HP!)
http://social.microsoft.com/Forums/...p/thread/4701a7c1-7096-421b-866c-57cb70225dcb

This 'real world' stuff, it sucks. On that we agree. ;-P

Thanks I will try this. You have been extremely helpful.

 

[Ken Blake, MVP]

No it's not. Each machine has its own valid key.

Glad to hear that, but let me point out the importance of using
precise language when you ask a question. You said "All these machines
were installed with *a* valid XP OEM key." Note the word "a" in that
sentence, which is singular and implies that there was a single key
used for all 50 machines.

So don't be surprised when almost all of us here misunderstood what
you said.

 

[B.D.©]

"WGA does in fact verify the region the product is being used in."

So is it possible to have a valid key invalidated because the country it
is being used in?

Yes. I would be surprised if this is the first time the US Government
has run into this issue.

 

[PA Bear [MS MVP]]

Contractor.
Each machine was installed WITH ITS OWN KEY.

The error message is
"The product key found on this computer is not valid for use in your
region."

You will need to contact your local Microsoft subdiary (i.e., Israel; Middle
East; Saudi Arabia; UAE) for assistance:
http://support.microsoft.com/common/international.aspx

 

[PA Bear [MS MVP]]

Yes. There are international trade laws governing this stuff.

 

[Shenan Stanley]

<entire conversation>
http://groups.google.com/group/micr...p.general/browse_frm/thread/a3a83b8f6b983dc3/
</entire conversation>

Thanks I will try this. You have been extremely helpful.

Hope it really does resolve your issue.

If you would not mind - pleasae return when you have resolved the issue (or
during the resolution) and post your progress/results and what fixed it -
some details.

That way we will all know what happened and how it was fixed for posterity
and in case it happens again in the future to someone. ;-)

 

[The Seabat]

True. Correct me if I'm wrong, but isn't the soil (area) inside a
U.S. Embassy considered to be U.S. soil? Which would validate the use
of those VLK's!

 

[Greg]

True. Correct me if I'm wrong, but isn't the soil (area) inside a
U.S. Embassy considered to be U.S. soil? Which would validate the use
of those VLK's!

The isp is not obviously.

Greg

 

[AndyTC]

True. Correct me if I'm wrong, but isn't the soil (area) inside a
U.S. Embassy considered to be U.S. soil? Which would validate the use
of those VLK's!

Exactly! So therein lies my problem.
These are not US government machines.

 

[AndyTC]

Yes. There are international trade laws governing this stuff.

Well all these machines had to get all proper ITAR before being shipping.
That being said, they are connected to the internet via VSAT with has
ground station in Europe. Also considering I can proxy the machine from
anywhere, it seems pretty dumb to validate location based by source IP
block ownership, especially when a worldwide satellite internet provider
is the owner, providing vsat in over 50 countries.


I am thinking of routing all internet traffic through a US based VPN so
I can pass the damn validation test, then allowing route back to the
internet.

 

[Kevin]

ONE REPLY IS ENOUGH! Evreryone will see it.

BUT HE HAS 50 MACHINES SO 50 REPLIES IS WARRANTED!!! SAMBO!