@acyuta An MAK activated Windows 7/8.x isn't eligible for Windows 10 upgrade path, as it is under VL agreement. Though you can force to upgrade manually & it will activate with a generic MAK, it is not recommended. You can, however, change the key of upgraded Windows 10 to generic retail & re-activate. Afterwards you can do clean install without inputting any key & reactivation is easy. The whole discussion is only applicable for Pro (/ProWMC) but not Enterprise. ALso 7 Ultimate can't be activated using MAK - why don't you use OEM:SLP method?
Thanks Tito for the prompt reply. So the first part of your para implies: 1. On a 10 image upgraded from 8.1 MAK, I change product key to generic retail. 2. Then do clean 10 install of course without adding keys. 3. I have activated 7 Ultimate for years from 2010-12 using MAK technet key. I thought of goinf this way to solve this problem. 4. One thing: I do not sign in with a MS hotmail account, but from a local account. Will signing from MS account help in curing this. Since this is a home system, I really prefer not to input the password on each startup. Does MS account force this.
1. Yes. 2. Yes. 3. 4. I never use Microsoft account on any of my PCs & there is no effect on activation.
Will changing key to generic key (ending with T) on a clean 10 image also solve this problem. Also if for future, can I do this: 1. Upgrade 7 Pro to 10. 2. Clean 10 install. 3. Not use store and sign in from my hotmail account. Also no hotmail on browsers.??
That is useful but not for me. I can anyway upgrade from 8.1 to 10 using my MAK key. What I want is a clean install of 10 which is running into activation problems recently.
I understand after windows 10 is activated after an upgrade it is HWID related That means it wil be activated after clean install But make sure that after an upgrade it is activated online
This was working for me (1) upgrade (2) clean install till last week, but read the original post. It is not working on clean install. System gets activated right off but a few hours/reboots later, goes unactivated.
Yeah that is very strange which generic key you used after clean install if I may ask ? Should end with 3V66T or T83GX at least For home version I have to check BTW
I thought that clean install does not require any key. In all cases of clean install, I do any input any key (should not have to since I had earlier upgraded from 8.1). I know this generic key, which is also shown on settings-activation. As Tito said, when it shows non genuine, I should change product key to generic (66T) and see what happens. Completely at a loss as to why after 1 month of doing 2-3 clean installs successfully (all on prior upgraded systems), things have gone wrong.
In my experience you have to change the key in the proces have heard other people talking here who had the same poblem with a blocked generic key. Can't tell you why it apears tho. I did change the key after done with windows 10 install. Because I'm used to do it like that from the past as generic keys never activated my system !