After installing Windows 7 RC 7264 my windows 7 beta product key have stopped working :( When entering the key windows says the key does not appear to be valid! What can i do? Its a 64 bit installation and yes i did use the 64 bit key. I get the key by going through the regular win7 beta download proccess for 64 bit. I had no problems in earlier RC builds with my key. Help!!

Beluga -Unfortunately, there's not much we can do to help you out there.. There are exactly two builds that are allowed to be discused in these forums - build 7000 (the Beta) and Build 7100 (the RC). Builds other than that have been known to have been "leaked" and as such, there's no clear chain of custody. Given that, what you have downloaded may be infected with malware and may not function as expected.The references on this can be found hereand here..If you actually got the ISO from an official source - you should probably be posting in the appropriate forum on MSDN or Connect.

The first linkthat Wolfie2k6 provided gives the forum policy on "unofficial" builds. As these forums are moderated, Iexpect that to be enforced. (I'm just a visitor here, though.)That said, 7264 doesn't accept the RC keys for activation. Web searches may reveal hacks that permit activation, but they'rehacks. The state of the hackedOS may not be what you'd like, even if it is stated to be activated and passes WGA.That's completely aside from the malware issues.If you insist on playing with "leaked" builds, I hope that you're at least checking file verification ("hash") codes. That's not certain to prevent your PC from being recruited for a botnet, but it's a line of defense.

The first linkthat Wolfie2k6 provided gives the forum policy on "unofficial" builds. As these forums are moderated, Iexpect that to be enforced. (I'm just a visitor here, though.) That said, 7264 doesn't accept the RC keys for activation. Web searches may reveal hacks that permit activation, but they'rehacks. The state of the hackedOS may not be what you'd like, even if it is stated to be activated and passes WGA. That's completely aside from the malware issues. If you insist on playing with "leaked" builds, I hope that you're at least checking file verification ("hash") codes. That's not certain to prevent your PC from being recruited for a botnet, but it's a line of defense. Yep. I'm checking the hashes and only download builds that i read about at www.windows7center.com which i find is a very reliable source for getting some kind of idea about wether the source is reliable or not.

The problem that inhibits Microsoft from making their hashcodes readily public is that, while it might offer some protection, it likewise would encourage that very same (torrent) activity. That goes for legitimately obtainedofficial releases too. It's a difficult policy issue.Which hashcodes are you confirming?

The problem that inhibits Microsoft from making their hashcodes readily public is that, while it might offer some protection, it likewise would encourage that very same (torrent) activity. That goes for legitimately obtainedofficial releases too. It's a difficult policy issue. Which hashcodes are you confirming? www.windows7center.com provide a set of hashes with every leak. The leaks always come from reliable source, at least that what the site claims.

www.windows7center.com provide a set of hashes with every leak. The leaks always come from reliable source, at least that what the site claims. BelugaWhale Since these are 'leaked' builds, this means that somebody had to violate a signedagreement, somewhere along the line to make a copy of this build public. This would preclude any notion of 'reliability' for these builds.Take the time to read the links that Wolfie2k6 posted. You are at risk when you use any of these unofficial builds. Ronnie Vernon MVPForum Moderator