This topic is talk about people's Windows Product Activation experiences.
I stated my experience with it in the "Windows 7" topic. In my experience Windows only needs to be reinstalled once every year or two if nothing goes wrong with it and with that time frame it doesn't seem like that big of a deal to call Microsoft after doing so.
Some disagreed with it not being a problem.
I decided to make a new topic so people could list their experience with it as I would like to know how it causes problems for other people.
How-To Geek Forums » Off Topic
Tip: Click Here to Update All Your PC's Outdated Drivers (Sponsored Link)
What is your experiance with Windows Product Activation?
(37 posts)
Here is a summary of the way Product Activation works.
http://aumha.org/win5/a/wpa.htm
If one reads it carefully, one can see that it becomes a nightmare for Builders, Software Testers and those who constantly reconfigure, change components, etc. and then do O/S Clean installs on their machines on a regular basis.
---------------------------------------------------
At some point in time, though they may be working on the same machine using their own genuine copy of the MS O/S, the over the net PA will fail and a manual PA over the phone will have to be done. From that point forward, net PA will always fail there after and a manual phone PA will always have to be done.
---------------------------------------------------
I have NO idea how MS acquires the information to put a known Genuine Product key piece of software on an only manual phone call to activate list but some how they do.
---------------------------------------------------
To avoid this "hassle" especially on complex Builds and Machines:
1. Purchase MS O/S 3-5 computer volume license.
2. Purchase Retail MS O/S license.
3. Purchase OEM MS O/S with Cals license.
---------------------------------------------------
Have run into the problem on occasion of UN-Archiving an already PAed version of an O/S which had to be Re-PAed on the same machine with a different configuration so archiving / imagining is not mentioned as a solution above.
---------------------------------------------------
In summary, without purchasing expensive appropriate O/S license versions as mentioned above, Builders and others (may) run into a huge problem with MS PA through NO fault of their own and when using legitimate, genuine MS software.
Rick,
I take it the PA phone call will work though. Certainly an irritant, bothersome, and a hassle, but that does do it, doesn't it?
And what do you tell M$ on the phone? Do you have to go through a lengthy explanation of your circumstance and an argument, or is it relatively straightforward and brief? Is the "huge problem" you refer to the phone call, or is it something else with PA?
@Bob,
A phone number and code pop up in a box on the screen when PA fails.
The phone call is free and can go to any MS call center world wide.
When someone answers, you give them the 45 digit alphanumeric code that pops up when PA fails over the net.
They give you a 50 digit alphanumeric code back in "broken Language" to put in the pop-up box and hit enter to PA the software. (This may be reverse numbered - can't remember but code is longgggggg.)
------------------------
If there is a squabble, you give them the Product ID and the Product Code on the Software.
They look that up.
If one has a special status with MS such as MS Partner, You give them that ID.
They look that up.
------------------------
That will settle the issue but it is a "hassle" with all the alphanumeric code going back and forth in "broken language" usually at 2:00 AM in the morning your time. (LOL)
------------------------
I actually got answer one time from a person who said they couldn't help me.
I ask why ??
They replied; "that they were just there to answer the telephone" - BUT DID switch me to another country who could after I got there attention. NOT A JOKE. (LOL) (LOL)
------------------------
If your software is on the "blacklist" or "pirated", don't even bother to pick up the phone. You are just wasting time.
------------------------
Remember, you don't own any MS products. You only have a license to use their products if they are kind enough to let you use them.
------------------------
Regards,
Rick P.
Rick, I have to say though, with all the pirating that is being attempted and going on, I understand their caution. Already 23 years ago I found out that $100 million worth of software was pirated WW each year - and that was only of 1 company and only with commercial customers. I wanted to start with product keys back then - but the development houses would not buy it. MS does the right thing. Maybe the implementation is a little flaky, but if you spoke Hindi, you could make out a lot better.
@whs,
It's a though matter as I can see BOTH sides of the issue.
I don't know what the answer is.
Maybe if MS didn't have such a large market share, the answer would be easier to figure out.
Most folks will NEVER do a manual PA as they don't build their own machines.
In fact, probably most think the O/S comes free with their machines and don't even know what this thread is about.
Best Regards,
Rick P.
@0z,
Don't know the answer to your question.
If you are abiding by the Eula License, I can find no legal grounds for MS stopping one from manually PAing forever.
However, MS makes its own rules up as they go and are much less well regulated in the US than in other world regions so they can really step on the consumers here without one having any recourse.
Best Regards,
Rick P.
I'm not sure but I would think that if you restore an install from an image made with something like Ghost you would not need to reactivate. So you could just create an image after a clean install and then you wouldn't need to activate again. Problem solved (in theory, I haven't tested it, I rarely do clean installs on my computer and I have yet to try restoring an image).
Wrong.
A machine may need Re-PAing even when using an MS OEM O/S Edition if (SUBSTANTIAL) machine reconfiguration can be accomplished on the (SAME) machine.
----------------------------
The Posters above are (NOT) reconfiguring a Builder Machine in between the original archived machine configuration archive file and a (new completely different) machine configuration onto which the archive file is UN-archived upon.
----------------------------
Ghost is only a tool used to make an archive file of a system and components as they are when the file is created.
----------------------------
On Pre-built OEM Machines, it is highly, highly unlikely one has the option to reconfigure the machine enough to
require a RE-PA.
----------------------------
However one can run into trouble on a (Complex) Machine with Multiple LANs, WIFI Cards, Multiple Hard Drive Controllers, Multiplicity of Hard Drives used in Different Configurations, Memory Configurations, etc., etc.
----------------------------
I know of what I speak as my Genuine MS Software is on the (Only Activate Upon Phone Call) MS List.
Regards,
Rick P.
As for OEM and PA, a friend of mine called me back about 2 months ago and said M/S wouldn´t reactivate his system online due to a graphics card upgrade!! He thought it was a virus (not understanding computers that much)!! What had happened was due to a (massive!!) change in hardware, lol, graphics card and ram, one had to call M/S to reactivate (XP). In my opinion it´s absolute B/S, just because one changes memory and graphics card (on an OEM system)!! Matt
Reply »
You must log in to post.