Heres what i did: 1. Set bios date to October 2010 2. Clean install - 6.1.7850.0.winmain_win8m1.100922-1508_x86fre_client-enterprise_en-us 3. Stop services (Software Protection), replaced tokens.dat (C:\Windows\System32\spp\store), pkeyconfig.xrm-ms (C:\Windows\System32\spp\tokens\pkeyconfig) 4. Start services (Software Protection), reinstall MAK key (Used to activate Windows 7 Enterprise) 5. Reboot (set Bios date back to today) 6. Activated.. The MAK key was the HP one released last year.
Any chance those working and failing activation depend on Windows starting up and detecting it timebombed? I don't normally screw with betas but I'll take a look at a few things (curious to test my future-proofing of AutoKMS, as in will it choke on a later version or have MS changed WMI calls).
Eh, I seemed to DL the iND build and I don't know if its been messed with as its KMS Key last 5 were equal to normal Windows 7. Apparently all the WMI commands are the same but I could not KMS activate and the KMS host wasn't even trying due to some C004E015 error. Well I found out what I wanted, the WMI calls are still the same so no compatibility errors, but I don't feel like messing with BETAs since my internet connection is crap and I don't know if things have been changed in the ISO. Does anyone have Win 8 with a key ending in anything other than HVTHH? Not sure why some people aren't able to KMS activate with this build. Anyone have ISO MD5 other than:EA2DCFADA6BBA517A0A0649D15E1EB3D
OK managed to KMS activate by frankenbuilding/screwing around alot with it (can't completely retrace). AutoKMS worked fine but I want to pinpoint the issue. Will try again with a clean install. About the timebomb, mine didn't complain but I couldn't seem to activate.
Here's my Hashes CRC32: 32EB1881 MD5: EA2DCFADA6BBA517A0A0649D15E1EB3D SHA-1: DCA69DF6074BCA8B5DBA5C8D6D030D53CB6D82C8 Is the real leaked one with this hashes ? Thanks.
Well that's why I asked, I am curious if any ISO's were made that have been changed. Then again, we couldn't be 100% sure the original leak was untouched. Thing is if we do all have the same ISO, I can make a small patch to the ISO to make activation stuff easier to deal with, removing timebomb, etc. DL a tiny patch vs someone ULing a full ISO and doing god knows what to it.
Seems great minds think alike, though I'm going for an ISO patch vs another 2.5GB torrent. Just so you know, in Win 8 they moved tokens location to SPP, so you have to get the tokens.dat/cache.dat from a ServicesProfile folder in windows and copy them where they should go. I'm testing a method for this in VMware.
Unfortunately my differncing tool makes a big patch since you have to rebuild wim and iso to do this, so I'll test this in VMware and post the files for everyone to make use of.
Sounds good. Couldn't you just release some .IPS file (which would be pretty big I imagine) of the differences between the two ISOs (original and modified) and release them for us to IPS patch though?