• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

which windows 7?

For me, i was getting random BSODs even on stock clocks and i spent weeks trying to figure out what was wrong and then got the nerve to install a different version of windows 7 so i went with home premium X64 and the problems vanished. Im glad my x64 key worked with home premium :).

Thats strange. I've been using Win 7 from the time it came out. And not a single BSOD. :confused:
 
This is also only partially true: Windows will not pass activation automatically, but reactivation can be done by phone. All you have to say is you had to change out the motherboard due to failure. Acting as an OEM means you also have the authority to judge that.

You can do that, but you aren't supposed to, unless it is true of course.;) A failure is a failure, it doesn't matter that you are acting as the OEM, if the motherboard hasn't actually failed, then you aren't supposed to re-activate on a different board.

Now comes the vague part: several OEMs have their own sets of rules when it comes to reactivation, and that text can be quite confusing for a "single person OEM" like myself. It actually means that the rules applied by Microsoft can be tightened by the OEM so that when you change out (say) a HDD on (say) a Dell, it will whine about reactivation, whereas according to pure Microsoft rules, this wouldn't be necessary.

That isn't true at all. OEMs can not change how strict the activation process is. Any re-activation requirement has been triggered by Microsoft, and Microsoft's rules, not the OEMs.

However, I can certainly see why this behavior might give you the impression that because a computer comes from OEMs it has stricter rules. The main reason is how Microsoft handles hardware changes. When Windows is first installed it takes a snapshot of the hardware. Once there are a certain number of hardware changes(I don't know how many exactly), it forces a re-activation. Now, with the OEMs, they tend to use a standard install image across multiple different hardware models. What this means is that the OEM has already made a large number of hardware changes from the original install. So, when the user changes one or two pieces of hardware, it triggers Microsoft's re-activation rules.

Basically it's not more than this:

Retail: The customer/user is able to reactivate. You are the customer/user. For additional support you can contact Microsoft as a customer.

OEM: The customer is unable to reactivate upon large hardware changes, the OEM is. If you are the OEM, you can simply contact Microsoft as an OEM. Additional support however is your own job.

The OEM doesn't have any more power to re-activate then the customer, both follow the same rules for re-activation. The only thing an OEM is responible for is support, this does not include activation. The customer can re-activate the OS 10 years from now, far after the OEM's responsibility is over. Microsoft follows the EULA for re-activation, EU standing for End User. It doesn't matter who is re-activating, Microsoft follows the same rules. New motherboard = no re-activation unless the new board is replacing a failed board
 
I guess I should have taken the effort to include my sources but then again, neither do you :D

Since I'm lazy, and at work, all I'm going to say is that I've gathered this info from Microsoft employees, at the Microsoft forums. If you don't want to believe that, go ahead.
 
Back
Top