M$ to use new key on XP SP1!

[mpsan]

CNET had an article that gave the new stuff in the XP update due this summer! They said M$ is going to deactivate 90% of the people who used certain Corp Keys!

Gee, we should have a pool on how long it will take before we get a registry tweak so we can upgrade anyway. I bet we get it within 5 days of sp1's release!

Here is news...look towards botton.

h**p://news.com.com/2100-1001-922066.html

 

[dx]

Yes, I have read that the most common Corp key is now banned on latest versions of XP now in stores and M$ update will stop working if this key is used. Windows will continue to work, but no more updates will be allowed (even manual) if this key is used.

Will they be able to stop all Corporate keys? Probably not...but if they do...the XP activation crack used in conjunction with the BlueList Keygen is really effective.

Stop us...naaah! Slow us down for a few days...probably.

 

[Seb]

but we've got linux to play with while waiting for new keygen/crack

 

[Nothing]

Fear not, there are already alternative Corp keys from the BlueList Key Discoverer blah blah, and if they all happen to be blocked (unlikely) then I know of at least 2 more "legit" corp keys which I'm sure would be made available if needed.

The process of changing your key in XP Corp is simple and fast. Nobody need worry about this shit at all.

 

[cawdor]

To "Nothing": would you care to elaborate on how to change the corporate key simply and fast? We might need to know that soon.

Thanks.

 

[mpsan]

Yes, I have read that the most common Corp key is now banned on latest versions of XP now in stores and M$ update will stop working if this key is used. Windows will continue to work, but no more updates will be allowed (even manual) if this key is used.

Will they be able to stop all Corporate keys? Probably not...but if they do...the XP activation crack used in conjunction with the BlueList Keygen is really effective.

Stop us...naaah! Slow us down for a few days...probably.

Well, since I have it all working, I never paid attention to "the XP activation crack used in conjunction with the BlueList Keygen" is it still around?

 

[dx]

Well, since I have it all working, I never paid attention to "the XP activation crack used in conjunction with the BlueList Keygen" is it still around?

Do a search for "BlueList Keygen"and "XP activation crack" and you will find all that you need to know (including the files you need).

I stopped using XP Corp key about 2 weeks ago and am using this solution now. Works like a charm and M$ is none the wiser.

Don't get me wrong though, your keygenerated Corp key may well work. But if they are banning the common Corpfiles (Devilsown) key it is possible that others may be banned as well. The amount of Corp keys is limited and M$ could check it against its database. If your keygened Corp key is not listed...no more updates. The BlueList Keygen (with a Pro or Home key) and XP activation crack are far too difficult for M$ to check them all.

But then again, we won't really know until SP1 comes out.

 

[mpsan]

Thanks, I will try the search.

Also, when is M$ supposed to stop Devilsown? I did an update just a few days ago and all was OK. I see some who say the Devilsown is already banned.

 

[Nothing]

Originally posted by mpsan Also, when is M$ supposed to stop Devilsown?

SP1

Okay, changing the key...

1. Run regedit and go to: HKey_Local_Machine\Software\Microsoft\WindowsNT\Current Version\WPAEvents, on the right double click on "oobetimer" and change at least one digit of this value to deactivate windows.

2. Choose run from start menu and type in this command:
%systemroot%\system32\oobe\msoobe.exe /a
to get the activation screen and go to the second option which is activate by phone.

3. In the new screen choose the option to change product key, and type in the new product key ( corporate one only ).

4. Close that window, reboot your system and enter the command in step 2 for the second time to verify your activation , you should see "windows is already activated".

And that's how

 

[dx]

Thanks, I will try the search.

Also, when is M$ supposed to stop Devilsown? I did an update just a few days ago and all was OK. I see some who say the Devilsown is already banned.

There is now a newer version of WinXP in the stores that accepts the key, but refuses to do updates. This is reportedly the same thing that will happen to you on SP1's implementation.

The Devilsown key is reported to cause a Corporate=False message at Windows Update page. It (so far) does not stop your updates in any way though.

Supposedly, a recent security patch from M$ installs some new code to better track your license (on Windows Update) esp. if you have used XP Antispy (for example) to disable some of XP's imbedded spyware. Remember these things have always been there, its just M$ wasn't pushing for them on updates.

So for now...if you use the Devilsown key you are safe. Once SP1 is implemented...me thinks you need a new solution.

 

[mpsan]

Well, perhaps the best thing to do is to not do any more updates. Then when sp1 comes out there will be a whole new round of "workarounds"!

 

[Nothing]

For older conversions, the Devilsown key will cause a Corporate=False message at Windows Update page. So far, it has not stopped your updates. But I think it will soon.

A common misconception, corp=false doesn't mean that your WindowsUpdate has "downgraded" your access in any way. The corp=false arg is correctly passed to the WindowsUpdate site when you access WindowsUpdate with links provided in the start menu etc, it happens on all corp versions. This is because the users of corporate XP installs are not expected to be system admins etc, they are not introduced to the (expert) corp=true site by default.

As for the key discovery code in a recent update, well, it seems that Microsoft is trying to verify how widespread the generated keys are before they take action (remember all WindowsUpdate transactions pass your GUID to Microsoft). Remember that the keygen often produces duplicate keys in a single session, it's very limited - also, the PID's of many generated corp keys are completely invalid, however, they do allow you to install corp versions perfectly well.

I would suggest that the vast majority of generated corp keys could be blacklisted as well as the Devils0wn key (but it's not likely). Still, there's no need to worry. I know there are other corp keys out there, they have valid PID's and they are already in use by large corporations. If the worst happens, i.e. generated and Devils0wn keys are blacklisted, we will have a perfectly useable key within that 3 day grace period.

 

[dx]

A common misconception, corp=false doesn't mean that your WindowsUpdate has "downgraded" your access in any way. The corp=false arg is correctly passed to the WindowsUpdate site when you access WindowsUpdate with links provided in the start menu etc, it happens on all corp versions. This is because the users of corporate XP installs are not expected to be system admins etc, they are not introduced to the (expert) corp=true site by default.

Hmmm, I stand corrected then. Although, to be fair, I did not say that Windows Update has "downgraded" your access (at least yet anyway). Funny though I've read this miconception in more than one place...so I guess its pretty common as you say. Don't get me wrong though, I'm glad to be wrong. Better for all of us.

BTW, how does one get into the (expert) corp=true site by default? It can't be logged in as an Administrator, as that's how I always log in as. I'm not using Corporate now...but I could swear that I was getting Corporate=true when I was using it.

 

[Nothing]

v4 corp update - http://v4.windowsupdate.microsoft.com/en/default.asp?corp=true

classic corp update - http://corporate.windowsupdate.microsoft.com/en/default.asp

Well, there are certain circumastances where the corporate update site will be obtained straight off. Before the final release of Windows XP - there was a period of time when all access to the update site was defaulted to corp=true.

AFAIK, most people would just use one of the above links to select updates from the corporate update site. Links provided in IE and wupdmgr.exe always default to corp=false regardless of the user's privileges. As corporate updates are just downloads (don't auto-install) I'd bet that anyone can access them whether they be Administrator or not.

I know you didn't say that windowsupdate had downgraded the access level, but the conversation was heading that way - as it often does when corp=false is mentioned

 

[Nothing]

Originally posted by dxkim but I could swear that I was getting Corporate=true when I was using it.

Was this during the gap between Devils0wn being available and 2600 being officially released? I remember that too

 

[Nothing]

Guys, problems happen all the time with Microsoft OS's. But you aren't having problems with the keys yet - or updates.

I've got 4 machines running XP Corp, 2 using the Devils0wn key and both of those are fully updated with WindowsUpdate = no problems at all. (another 1 with a generated key, all updated fine too)

Some people are having problems after updates and blaming keys etc - there are no problems (yet)