Vista Officially Cracked?

Rich Tate

Supreme [H]ardness
Joined
Jun 9, 2005
Messages
5,955
News has began filtering in this morning that a piracy group has created a working crack for Windows Vista. It appears that the program emulates information at the BIOS level to circumvent Activation altogether.

Unlike cracks which have been floating around since Vista RTM was released in late November, this crack doesn’t simply get around product activation with beta activation files or timestop cracks - it actually makes use of the activation process. It seems that Microsoft has allowed large OEMs like ASUS to ship their products with a pre-installed version of Vista that doesn’t require product activation – apparently because end users would find it too inconvenient.
 
too inconvenient? hmmm or some other ploy. regardless, I know many who will be thanking asus for their involvment since they never buy OS's. autopatcher next. this will help in my fight to upgrade lan buddies to dx10 gpu's.
 
I should also note we do have forum rules about piracy discussions.

Yes, I realize this is essentially a discussion about it, but there is no need to admit to it.
 
What's really funny is Microsoft spent tons of money on this "Activation System" and Asus finds it inconvenient so they pre-activate it? I think the was no point to build this system. They knew it would be cracked and the only people you're really hurting is your customers not the pirates.
 
What's really funny is Microsoft spent tons of money on this "Activation System" and Asus finds it inconvenient so they pre-activate it? I think the was no point to build this system. They knew it would be cracked and the only people you're really hurting is your customers not the pirates.

The thing is though that it isn't just ASUS. Take a look at the screenshot. You see some other big names like Dell and HP as well.
 
What's really funny is Microsoft spent tons of money on this "Activation System" and Asus finds it inconvenient so they pre-activate it? I think the was no point to build this system. They knew it would be cracked and the only people you're really hurting is your customers not the pirates.

That is pretty much what any protection schemes and DRM does, just hurts the consumer because pirates will always be able to get around it.
 
Doesn't Vista validation system check back periodically to see if it's key is still valid?

If so, since this crack is tied to the (I assume) stolen keys from the OEMs being emulated then MS just has to blacklist those keys and on the next validation cycle Vista will see it's PID is no longer valid and lock itself down.
 
That is pretty much what any protection schemes and DRM does, just hurts the consumer because pirates will always be able to get around it.

Also costs the consumer as well. Who pays for all the work on these DRM systems after all.
 
Doesn't Vista validation system check back periodically to see if it's key is still valid?

If so, since this crack is tied to the (I assume) stolen keys from the OEMs being emulated then MS just has to blacklist those keys and on the next validation cycle Vista will see it's PID is no longer valid and lock itself down.

Nope. It seemingly circumvents everything, if I looked at the torrent descriptions correctly.

Also, I read on another forum that the guy was saying it returns <default> for each piece of detected hardware, but I haven't confirmed that yet. I guess that would let you replace stuff at will...
 
What's really funny is Microsoft spent tons of money on this "Activation System" and Asus finds it inconvenient so they pre-activate it? I think the was no point to build this system. They knew it would be cracked and the only people you're really hurting is your customers not the pirates.

Most of the OEMs do it. If I used a Dell WinXP cd to reinstall my OS on my laptop, I don't have to put in a key because the CD detects that I'm using a Dell. If I use that disk in another brand computer, or another disk in this computer, I need to input the key myself.
 
Doesn't Vista validation system check back periodically to see if it's key is still valid?

If so, since this crack is tied to the (I assume) stolen keys from the OEMs being emulated then MS just has to blacklist those keys and on the next validation cycle Vista will see it's PID is no longer valid and lock itself down.

I don't see how MS can blacklist all the OEM keys, it would piss a lot of consumers off. If MS randomly decided to deactivate my computer and make it so I had to reinput/get a new product key, I'd be pretty mad.
 
If MS randomly decided to deactivate my computer and make it so I had to reinput/get a new product key, I'd be pretty mad.
I believe MS has done that before. I remember my OEM Dell key was cancelled around 1994. Not the key on the COA, the volume key used on all systems for bulk installation.
 
It works in conjunction with the OEMBIOS.BIN file that typically is used by major OEMs to tie the installation CD/DVD directly to their hardware alone. By emulating any OEM's BIOS under Windows and then using an actual key from the same OEM, it basically causes the activation code to be nullified after that point and makes the necessary changes in not only the Registry but some of the related system files as well.

And yes, it works just fine.

Microsoft does have the ability to detect this, however. That's the kicker here, and not something enough people are realizing - they're pouncing on this from the surface thinking "We put one over on The Man again!!!" and not thinking long term.

Short term successes mean jack shit, because in the long run Microsoft will drop the hammer on this, and then another hack will appear, and another fix, and another hack, and another fix.

btw, this concept of an emulated BIOS... Microsoft worked that out back in 2003, so this isn't "new" to them, it's just new to the hacking community, and as such, it won't last. :)
 
It works in conjunction with the OEMBIOS.BIN file that typically is used by major OEMs to tie the installation CD/DVD directly to their hardware alone. By emulating any OEM's BIOS under Windows and then using an actual key from the same OEM, it basically causes the activation code to be nullified after that point and makes the necessary changes in not only the Registry but some of the related system files as well.

And yes, it works just fine.

Microsoft does have the ability to detect this, however. That's the kicker here, and not something enough people are realizing - they're pouncing on this from the surface thinking "We put one over on The Man again!!!" and not thinking long term.

Short term successes mean jack shit, because in the long run Microsoft will drop the hammer on this, and then another hack will appear, and another fix, and another hack, and another fix.

btw, this concept of an emulated BIOS... Microsoft worked that out back in 2003, so this isn't "new" to them, it's just new to the hacking community, and as such, it won't last. :)


Thus, wouldn't a timerstop-style crack, theoretically, be a more permanent solution?
 
No, because it's not activated yet - Microsoft can tell that stuff, yanno. The activation servers garner a lot of non-personably identifiable information, meaning about the OS installation itself, dates, times, etc. You might not be getting anywhere in terms of time but the specific activation ID created for your particular mix of components (that 50 digit code) is still used whenever you get an update from Windows Update and tracked.

All Microsoft would have to do is have a piece of code do a run through and say "Yanno, this activation ID hasn't been activated, but it's been used for a long long time with Windows Update, lemme put up a flag here so some human can take a look" at which time a human gets involved and can look at the actual data involved - the same stuff you'd get if you typed slmgr -dlv at an elevated Command Prompt.

People seem to think these hacks/cracks/timer bypasses/etc are actually going to prove useful in the long run. They're wrong, of course, they just don't believe it yet.

I've seen stranger things happen...
 
It works in conjunction with the OEMBIOS.BIN file that typically is used by major OEMs to tie the installation CD/DVD directly to their hardware alone.

OEMBIOS files are from the old version of System Locked Preinstallations (SLP), WinXP and before. Vista uses a new version of SLP (2.0) that is far different from the OEMBIOS method. In fact there are no OEMBIOS files in Vista at all. What SLP2.0 uses is a table in the BIOS along with a public key certificate embedded in there as well. The product key entered matches the certificate in the BIOS and in addition to that, the certificate that is installed in the OS. That combination gives you an activated state.

Microsoft does have the ability to detect this, however. That's the kicker here, and not something enough people are realizing - they're pouncing on this from the surface thinking "We put one over on The Man again!!!" and not thinking long term.

Very true. From what I saw, this method actually installs a driver file in the OS (royal.sys if I recall correctly), while I have no doubt this method will work, and work well too, it will be VERY easy to detect based on that single file. WGA will be upgraded, and all systems with that file located on their system will be invalidated. Hope everyone that is jumping on this didn't overwrite their XP install, they may need to fall back on it shortly. :)
 
What's really funny is Microsoft spent tons of money on this "Activation System" and Asus finds it inconvenient so they pre-activate it? I think the was no point to build this system. They knew it would be cracked and the only people you're really hurting is your customers not the pirates.

Same thing that all of the big OEM systems have done for a while.

All this means is the next version of WGA will scan the system for this and catch it. You'd be better off just writting down the cd key on the side of a computer at bb or something if you really wanted a pirate copy.

I don't see this as a big deal.
 
I'll only get vista when I can use Virtualization Technology to go from XP to Vista (and to Ubuntu).
 
When theres a will theres always a way ;). No software is 100% uncrackable. It was bound to happen sooner or later.
 
A little research seems to indicate that you can approach this crack two ways. You can load the spoofed BIOS layer into your OS, or you can actually hack your system BIOS. Either way works, but both seem horribly inconvenient. The timestop crack seems to work the best out of all of them so far (not that I would have any experience in this field ;)).
 
I find it hilarious that they spend millions creating an uncrackable OS yet leave a massive gaping hole in it.

Its like fort nox with hundreds of steel doors and bulkheads with surveillance and retina checks, but having a single wooden door for the cleaners so they can dust the gold.
 
All Microsoft would have to do is have a piece of code do a run through and say "Yanno, this activation ID hasn't been activated, but it's been used for a long long time with Windows Update
That's why you don't let Little Billy dial home.

Microsquat is far more concerned with people paying for a legit OS and getting pirated crap, that's their entire incentive for going through all this trouble and loading stupid system-slowing, resource hogging services when you're computer starts up. Pirates are not going to pay for it regardless, ever, and forcing geeks off Windows by creating an uncrackable version would only put them onto Linux or Mac OS where they would immediately start improving on it.

Naturally, "uncrackable" isn't actually possible.
 
I find it hilarious that they spend millions creating an uncrackable OS yet leave a massive gaping hole in it.

Its like fort nox with hundreds of steel doors and bulkheads with surveillance and retina checks, but having a single wooden door for the cleaners so they can dust the gold.

How is it a massive hole? Its not a crack in OS security...its a crack in OS activation so your OS shows up as Genuine to MS. If this broke security that they've worked on to improve then I'd agree with your analogy.
 
That's why you don't let Little Billy dial home.

If you think that Windows Update is the only way Microsoft can glean information about your OS installation, boy have you got a lot to learn. You should read the EULA of anything related to Microsoft sometime, it's interesting reading, with all sorts of open clauses... open for interpretation, open for change, open for implementation... and not needing your consent in any way, shape, or form.

I tell ya...

As for the "gaping hole" theory, it's not a hole as was just stated. There's no way to prevent every possible attempt at breaking such protective measures simply for the fact that every possible method hasn't been created yet. New methods come out to stop people from doing something, then someone finds a "new" way to get around it, another new method to stop someone, someone else finds another way around it, etc.

It's a neverending battle going on, and all Microsoft can do is try their best to protect their property.

Kids and their "I got one over on The Man!!!" attitudes... I mean really.
 
The funny thing is this is in XP as well...we have been using it for about 5 years where I work and are using the Vista version now as well....

The BIOSs that we get on our mainboards are each licensed copies of the said version of XP or Vista (and the mainboard manufactures have to pay MS for that license). Then when we use our special version of XP/Vista, it is activated and we never even enter a product key.

I think its funny this method was never used in XP even though it was still there.
 
Not to condone the piracy, but sometimes there are quite clever ways ot circumvent it... activate Vista? eh.. just make a program to make it think you have an ASUS prebuilt rig.

Anyone remember the sharpie with a CD trick? Some time back?
 
Microsquat is far more concerned with people paying for a legit OS and getting pirated crap,

I seem to recall reading somewhere that microsoft makes WAY more money of selling licenses to companies who pre-install their software on machines (or those who install on multiple systems like colleges & business) than they do from the end consumer who simply buys an OS. If this is true, seems silly to put so much effort into antipiracy.
 
This had been debunked. It was a hoax.

Got any more info on this?

Anyway the idea behind this is pretty good. Personaly I'd rather have them fail at it though. Last thing I want if for ms to make it harder to load oem systems(have to do a few a month).
 
I seem to recall reading somewhere that microsoft makes WAY more money of selling licenses to companies who pre-install their software on machines (or those who install on multiple systems like colleges & business) than they do from the end consumer who simply buys an OS. If this is true, seems silly to put so much effort into antipiracy.

Not at all silly. This system was designed to stop two things: foreign companies who's entire country is run on illegal software (like China and India), and local shops who charge their customer for a license but use illegal software so they can get a free $100. I'd say it's worked wonderfully well.
 
Read the last link, it looks like a hoax to me. Sorry for 3 posts in a row ... can't edit.
 
bbz_Ghost said:
All Microsoft would have to do is have a piece of code do a run through and say "Yanno, this activation ID hasn't been activated, but it's been used for a long long time with Windows Update

Why would someone who is using that style of crack even bother with Windows Update unless they used some kind of WGA crack regardless?

If you think that Windows Update is the only way Microsoft can glean information about your OS installation, boy have you got a lot to learn. You should read the EULA of anything related to Microsoft sometime, it's interesting reading, with all sorts of open clauses... open for interpretation, open for change, open for implementation... and not needing your consent in any way, shape, or form.

I tell ya...

As for the "gaping hole" theory, it's not a hole as was just stated. There's no way to prevent every possible attempt at breaking such protective measures simply for the fact that every possible method hasn't been created yet. New methods come out to stop people from doing something, then someone finds a "new" way to get around it, another new method to stop someone, someone else finds another way around it, etc.

It's a neverending battle going on, and all Microsoft can do is try their best to protect their property.

Kids and their "I got one over on The Man!!!" attitudes... I mean really.

If it isn't connecting, it can't be changed ;).

As far as the "gaping hole" thing, it is, because it could have easily been solved at the time it was written. It's not some radical new style of cracking, it's just a hole they left that was later found/exploited. There's only so many theoretical ways to do it.

Yep... though I don't think people really pirate as much as everyone makes it out to be. It's definitely not "never-ending"... I'm quite sure people with the timerstop thingie have been probably using it since Vista was RTM'd and have been enjoying it as well as you and I enjoy our real versions.

I don't think it's really "kids" who are going OMG MANNNNNN... I think it's cheapskates or people who want to try something out before buying, or something they would usually have not bought anyway. In the few cases they might take something they would have bought, I would assume it was a lost cause in any case.
 

On the other hand, it seems to be back on again ... who knows.
http://keznews.com/2443_Video_Windows_Vista_Keygen_confirmation_

Read the last link, it looks like a hoax to me. Sorry for 3 posts in a row ... can't edit.

Thats the so called brute force keygen, not this "BIOS" hack we are talking about in this thread.

http://www.engadget.com/2007/03/03/windows-vista-brute-force-keygen-a-hoax/
 
Back
Top