This is a quick guide shows how to activate Windows 8 Build 7955 with Windows 7 Beta Product Keys.

1] Close all windows of Windows Explorer;
2] Click on Start, search Command Prompt; right click on first result and click on Run as admnistrator;
3] Hold CTRL+SHIFT+F9;

Now is required a Windows 7 Beta Product Key. If you don't have it (anymore), you can insert your Windows 7 Ultimate Retail's Product Key, or:


4] Type slmgr.vbs -ipk and your Product Key (ex. slmgr.vbs -ipk 6JKV2-QPB8H-RQ893-FW7TM-PBJ73) and press Enter;
5] Wait for the Windows Script Host window and close it clicking on OK;
6] Type slmgr.vbs -ato and press Enter;
7] Wait for the Windows Script Host window and close it clicking on OK;
8] Finished!

Screenshots:




Thanks to Windows 8 Italia Forum - Original Post.

Looks very interesting That means how Windows 8 Builds a bit similar to Windows 7. Many thanks!

When I need to activate Windows 8 I'll try this method, thanks for sharing.

@SninS No, that's not true. The activation takes just (still) the current or old beta keys. Windows 8 isn't similiar to Windows 7.

misplaced topic.... but good guide!

Doesn't work for me.

The normal way worked for me.

Activated with 6JKV2-QPB8H-RQ893-FW7TM-PBJ73 (:
It works!

Hmf. I keep getting "Error 0X8007007F On a compute running Microsoft windows non-core edition, run slui.exe 0x2a 0x8007007F' to display error text." Might have something to do with the fact that I've tried to activate with both BluePill and NoPill 1.0. (Neither have worked, for the record)

Thank you very much for the great, simple guide! I'll be sure to use it if I need it.

@ackart: I've got the same problem. I figured out I probably got this error because I installed Build 7955 in VirtualBox. So VB probably 'fakes' the processor differently from the real processors. Is it true that you're also simulating Windows 8 through virtualisation software? If so, that's probably the reason for this error.
(I haven't found a solution yet, but I'll keep you updated!)

I think that MS are going to change there activation method before the retail release. They just dont want it getting cracked before retail release, so it will be implemented to later builds of the OS.

I also get this error, but I'm not using a virtual machine :/

Just make fresh install of windows 8 7955 and go to Genuine Center, put Win7 Beta key and that's all! Windows Activated! at least, i done that way.. No command prompt, no commands, no activators.. Just simple way..

The last blue pill for 7955 should work correctly but only after a fresh install. activation must be done before the unlocking of features! (so press "2" to activate then "1" to unlock)

And don't forget , do never crack genuine center dll's (like Sebastian did) to attain genuine status , it may show as activated in genuine center and a couple of other places but unfortunately , it will never pass genuine validation in Microsoft products like mse and other products which require genuine validation and by the way ,neither the internet activation way nor the telephone(used us toll free number in skype) did not work for me , patching slc.dll after the second installation reboot through live operating system did work for me(got the new out of box experience too a a bonus) (i (literallly) smashed my head on the keyboard for both the username and computer name. after this , i used the beta keys and it got activated (my internet connection wasnt working at the time), however it took a few minutes )

Thanks, worked good.

Strange, I activated through the Windows 8 installation, and it succesfully activated Windows for me (it will expire somewhere today though )

this method should use the first and never try activate on genuine center afraid of.. an error activation happen.. so it will be same after use that then use CMD(slmgr) method it's can't activate... except try to remove the key and fresh activate with cmd (slmgr method)

yup activation depending on systembaord and the key

In 7989 is the same thing but with Windows 7 Ultimate RTM key.

yea Retail keys and for the activating the best way is use slmgr.vbs CMD

Same thing = slmgr.vbs = obviously

yeah obviosly same...