[64]Adding RAM caused Vista deactivation

[SuperSparks]

Has anybody added extra RAM to their PC after installing Vista?

I added an extra 2GB of RAM, to bring the total up to 4GB earlier today, and I was very surprised to find that after waking it up again this evening it was telling me it had deactivated because of hardware changes I was able to reactivate over the Internet with no problem, so it's not that big a deal, but I'm sure it isn't supposed to require reactivation after a simple RAM addition. If this has happened to anyone else then I'll report it as a bug, if not, then I'll just put it down to an odd glitch.

[liam858]

I've heard of it happening with the slightest thing, including drivers, and extra hard drives.

A few examples in this thread:

http://www.evga.com/forums/tm.asp?m=...=1&key=&#71451


Liam

[dunedin]

Same here

I have even heard of it happening after a driver update from Automatic Updates These people were not at all pleased, to say the least

Elaine

[dunedin]

Nick,

Read this.

http://arstechnica.com/news.ars/post/20061030-8104.html

NOTE
"Validation will fail if the software detects a substantially different hardware configuration," the spokesperson said. "At that point, the customer is able to use the one reassignment for the new device. If, after using its one reassignment right, a customer again exceeds the tolerance for updated components, the customer can purchase an additional license or seek remediation through Microsoft’s support services."

If this means what I think it does, a lot of people are in big trouble

I think it must be a bug when driver updates and added Ram etc are calling for reactivation

Elaine

[jenae]

Hi, we have updated many 32 bit vista memory's, no problem so far. No 64 bit. I notice the date in Liam and Elaine's link's were last year, maybe a glitch Nick, or a 64 bit thing... I would have heard more about it, last week had a meeting with many Sydney based tech's and not one mention.

[SuperSparks]

I asked about this in the MVP newsgroup as well, and it appears that it happens to some PCs and not to others, with no obvious cause as to why. I think I'll report it as a bug, and hopefully it will get looked at.

Thanks everyone