I HAVE PROOF THAT WITH WINDOWS 10 FREE UPGRADE IS CRAP

If I'm following this right, then I think Ace Modder's problem is that he upgraded a Retail Windows 7 key to Windows 10 expecting to get a Retail Windows 10 key from it - i.e one that he would be able to transfer from motherboard to motherboard.

But instead he has effectively upgraded his retail key to an OEM one, and has therefore tied it to a single motherboard?
 
So the fact that everyone has been saying this exact thing in the windows 10 topic for the last week makes this important how ?? there is nothing stopping you doing back to your old windows if you don't like it don't use it

Tute said:
But instead he has effectively upgraded his retail key to an OEM one, and has therefore tied it to a single motherboard?
Click to expand...

He can still go back to 7 if it likes.
I really wish people would take the time to read the forum before posting as I have been watching people ask this question in the windows 10 topic for the last week and people answering what Microsoft said its not really something that needs to be said apart from in a Windows 10 FAQ sticky if someone would set that up.

Personally I am going to buy a key for my main PC that I upgrade every few years but the rest of my pc's Laptops, media centre and my parents pc I am just going to use the free version as they don't change often.
 
Last edited:
Twirlywoos said:
I guarantee the generic keys now tied to a win 10 upgrade will fail that activation upon new hardware change and the oem keys will remain blocked.
Click to expand...

Thats happens anyway with a mobo change and you have to ring MS, nothing will change in that regard what you are suggesting is a class action lawsuit waiting to happen and will violate EU anti trust.
 
We do have unique keys. I pulled this off another forum.

Save the code to a textfile, rename extension to .vbs, run. Ctrl C to copy the key that appears on screen.

Set WshShell = CreateObject("WScript.Shell")
MsgBox ConvertToKey(WshShell.RegRead("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DigitalProductId"))

Function ConvertToKey(Key)
Const KeyOffset = 52
i = 28
Chars = "BCDFGHJKMPQRTVWXY2346789"
Do
Cur = 0
x = 14
Do
Cur = Cur * 256
Cur = Key(x + KeyOffset) + Cur
Key(x + KeyOffset) = (Cur \ 24) And 255
Cur = Cur Mod 24
x = x -1
Loop While x >= 0
i = i -1
KeyOutput = Mid(Chars, Cur + 1, 1) & KeyOutput
If (((29 - i) Mod 6) = 0) And (i <> -1) Then
i = i -1
KeyOutput = "-" & KeyOutput
End If
Loop While i >= 0
ConvertToKey = KeyOutput
End Function
Click to expand...

Mine: TY4CG-XXXX-XXXXX-XXXXX-XXXXX

No idea what we can do with this unless a clean install asks for it.

However, the other forums lists standard keys as

Windows 10 Home: TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
Windows 10 Pro: VK7JG-NPHTM-C97JM-9MPGT-3V66T
Windows 10 Home Single Language: 7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH
Windows 10 Enterprise: NPPR9-FWDCX-D2C8J-H872K-2YT43

which are different from the 'standard' ones posted in this thread.
 
Last edited:
I have pro and mine is different too...

I did believe microsofts "no key" thing but this other method worked for me when all the others would just say "0A3xOriginalProductKey". So i have saved the key just encase until we learn more.
 
Danny091 said:
I have pro and mine is different too...

I did believe microsofts "no key" thing but this other method worked for me when all the others would just say "0A3xOriginalProductKey". So i have saved the key just encase until we learn more.
Click to expand...

Danny, my key looks like it's the same as yours along with the version 'Windows 10 Pro' I am now under the impression these are new generic keys issued.
 
mrbell1984 said:
Danny, my key looks like it's the same as yours along with the version 'Windows 10 Pro' I am now under the impression these are new generic keys issued.
Click to expand...
I think you were looking at mine.

My last 3 keys are: **FC6

The key from the script is completely different from the one shown in ProduKey link on the first page.

Danny091 said:
I didnt post my key anywhere have i? :eek::confused:

But it looks like this.. PV24P-*****-*****-*****-**4DB
Click to expand...

Yep i'm on pro too and we have different keys.
 
mrbell1984 said:
Sorry I meant @D3K ....

Maybe people with retail version will get their keys shown and people with OEM get generic keys.. The retail keys could be used to activate in the future maybe?
Click to expand...

I'm on retail, or vol, as it came from my work's msdn account. Are you oem? And do your last 3 keys match mine?
 
D3K said:
I'm on retail, or vol, as it came from my work's msdn account. Are you oem? And do your last 3 keys match mine?
Click to expand...

I am on OEM (Surface Pro 2) - Windows 10 Pro. My last key is different too yours...HCF*6

What is even more interesting is I have another key using the ProduKey OEM Bios Key... starts with HP3NC6 (Maybe this is the real activation Key!)

I did it as an upgrade not clean install (From Windows 8.1)
 
You must log in or register to reply here.
Back
Top Bottom