Unless it's the key? I don't know which key FS is using. I can't use any until one has been confirmed either.
Not here... tested with 2 different keys (one i suspect to be real, and one generated) Both remain activated, both without '1058' warnings
Can you use KeyInfo on the key that does not cause the alert and let me know what they KeyID is? The KeyID isn't sensitive; it's just what represents the edition ID.
there was Automatic Virtual Machine Activation (AVMA) KEY (which one was published too) hxxp://technet.m!crosoft.com/en-us/library/dn303421.aspx that on PID Checker show info as belov Validity : Valid Product ID : 00254-10000-00000-AA320 Activation ID : f002931d-5536-4908-8d93-40ae584e24d6 Edition Type : ServerStandard Description : Windows Server 12 R2 RTM ServerStandard VT:IA Edition ID : X18-90812 Key Type : VT:IA Crypto ID : 2541
It doesn't matter that much as i never have encountered the '1058' warning tested (Hyper-V) with 2 different keys (the one i suspect to be real, and one definitely generated) Both remain activated, both without '1058' warnings... i don't get it either FYI, not that i think it is related but who knows Code: Table NameOEMID&TableIDAddress LenthDescription Table (ACPI 1.0) RSD PTR ACPIAM 000F56F0 20Root System Desc.Pointer | |- RSDTFUJ PC 7FFF0000 68Root System Desc.Table | 00 |- FACP FUJ PC 7FFF0200 129 01 |- MSDM FUJ PC 000FF200 85 02 |- WAET FUJ PC 7FFF1480 40 * 03 |- SLIC FUJ PC 7FFF14C0 374Software Licensing Desc.Table 04 |- OEM0 FUJ PC 7FFF16C0 100 05 |- SRAT FUJ PC 7FFF0600 240 (I also altered the last remaining OEMID, and OEMTableID in vmwp.exe, not located in 1B module) 06 |- APIC FUJ PC 7FFF0300 588 07 |- OEMB FUJ PC 7FFFF040 100 --- Scan Finished ---
I've not tested any generated keys so can't comment on the error code, but like I've said, it sounds a lot like the error code WAT logs for Windows 8.x when you use a DM key on a different system. Apart from that though I just wanted to chime in on the one you thought might be legit in case anyone was getting their hopes up. Someone somewhere must have a confirmed OEM SLP key for WS 2012 R2 by now. We had one for every WS 2012 edition really early compared to this. As for the OEM ID's being changed, that's a possibility. I mean with Server 2012 they made it so that the RSDP must remain in ROM, so the new trick might be to check some more OEM ID's. The loader already has an option to spoof them all though and I guess it's not difficult for BIOS mods either.
I used Retail en_windows_server_2012_r2_x64_dvd_2707946, so I have no idea why (ofcourse I do it on physical hardware - VM activation is a bit different (with routine for AVMA)) sebus
@ Inge001 The guy who worked on KeyInfo application did it here though. He even fixed some bugs. It was janek2012 that originally posted the keys as I was in contact with him. He got ahold of them from a leak of sorts. So anything with info that's partially the same as the keys I posted is fake.
Says who? Did anybody here actually get access to any system with such keys directly from OEM? We did all assume the keys are legit (I never even seen OEM 2012 physical machine) And keyinfo did not come from janek, but bob sebus
@ sebus As I've just said in the post, janek2012 leaked out the keys in August and I was in contact with him about it. I was also the first person to post in the "Windows 8 Product Key Decoding" thread because thread creation for Windows 8 content had been set to moderated. When Bob65536 first created the thread it contained mostly information and ideas as he was still debugging things. If you then read a few pages into the thread you'll see that bugs were fixed and he then released the program. So it wouldn't of been possible for the keys janek2012 leaked a whole month before to of been generated by Bob's program as there would of been issues. The 9TJ3H key didn't show up until much later (it might not even be posted here), so my guess is that someones used the key info (group and key ID) from X4PQH and has then changed the secret value. The result from doing that is that you'll get the same product ID. FS logs all keys entered into his website, so he's probably having some of the fake generated keys checked against his site to see if they pass as "valid" keys.
Still, no "proof" that the 2012 legit key are so, right? We assume they are (and they might be), but maybe not? Unless we get a real iso (real or official download etc) sebus
Well, that could be said about every random key we receive, I guess? I just class them Server 2012 keys as legit as I know they existed before the app to generate keys did. The dates between things are enough for me, but anything newer than them keys I now can't trust. If the person who had of posted the v2.3 SLIC had of also posted a key then I'd of accepted that as legit OEM dump, but now any random person can register and post a key while telling us all that they got it from a server at work. We can't trust that source anymore, unless they post a complete OEM dump (new SLIC, cert and key) for something that we don't have already. I guess in a way the KeyInfo app being public kind of screwed up a good thing we had going.
@ Inge001 --removed so that others don't try it--- Hiding or removing Bob's thread wouldn't benefit us anymore as it's been available to the public for too long.