XP key changer

I've used the XP key changer that is downloadable from here before. But when trying to use it today every unit that I have tried to use it on has failed. It is giving a fatal error and goes back to original registry values. Is anyone else having this problem? What is the fix to get the key to change. I work for a place that had an IT admin that used illegal VLK's and am now trying to put the pc's that have a legal key sticker on them back to the legal key. It has been frustrating today when it has not worked 3 times.

 

http://www.microsoft.com/genuine/se...en&sGuid=e1d56403-db68-47cf-9134-884f9a2f1fa1 here is a link to Microsoft own keychanger, but it WILL report to Microsoft, so only use genuine keys.

 

Tried MS but it says invalid key. Which is really amusing since it is printed right on the pc. So guess this one is screwed.

 

You may have used an os disc that doesn't match that key on your case (i.e. Xp home retail vs xp home oem). Just as a note though, instead of using a keychanger you can go to windows/system32 and delete wpa.dbl and when you reboot it will make you enter a new key (can't login until you do)

 

Didn't use a disc at all. I'm trying to fix the illegal versions in the place where I work. BTW on 1 from MS worked on the first 2. they are now legally back to their true key. So thanks for the help.

 

Your problem is you're trying to use OEM keys on a system that was installed using a corporate VLK disk. OEM keys only work on OEM disk, such that comes with a Dell computer, etc. Retail keys only work on retail disk you buy at a store. And volume license keys only work on Corporate installation disk. And to go one step farther, an XP Home key won't work for an XP Pro disk and vice versa.

If those computers were installed with a Corporate XP Professional, then the only way to get them back to the legal key on the side of the computer (which means it's an OEM key) is to format your hard drive and reinstall using the OEM disk. If it says XP HOME on the side of the case, then you'll need to use an XP HOME OEM disk. You comprehend?

 

Actually the PC's had XP pro Ordered on the the units from Tiger Direct. The illegal VLK was put on them by having new cloned HDD put into it. It was not a Corp key but a key generated VLK with a key generator. And in fact 3 of the 4 took the correct key that was on the PC MS key that is on the sticker written on the PC. What you don't understand is the IT admin has been using an illegal hack key gen to put keys on to all the machines here. It was "saving" the company money to do this. Well now that MS is catching up with the illegal VLK's and shutting them down we are now having to pay the price now. We hope that MS doesn't show up to check this place out while we are converting to legal OS S/W. We have found out just this Fri that our servers & exchange is also operating under a hacked keys as well and that is going to cost us some serious $$ to fix these. The exchange server is running a hacked Enterprise copy of 2003 server. The least expensive place I have found it will cost 1500 and the domain controller is going to cost us 700. Then there are around 35 pc's in the location that we will have to switch to legal. This is why I have been having to use the key changer to start with. Thing is not all of the units will take the correct key and then I have to use MS's key changer which reports back to MS. The later is what we are a bit worried about We may be being put on some kind of list aht will come up as tagging us to have MS pay us a visit for all of the hacked keys that we are changing. To tell you the truth at this point I hope the hacking IT admin get visited by MS. He not only does work for us but others that we bet also have illegal S/W keys as well. It's really time he is stopped from the practices and has been busted for other types of illegal stuff before and still hasn't learned his lesson. Whatever, I'll get off the soap box now. You are in effect correct that it was a corp VLK but that VLK was hacked and put on the an OEM machine which I was trying to return to the OEM key. So now we will be switching it to a legal disk when it comes to me this week. Oh BTW as far as we know the OEM pc's from Gateway didn't come w/ the disk it was loaded on the HDD and the restore disc was never here or the previous IT guys tossed them. There have been 2 in the past 2 years both of which seemed to not know what the F they were doing. So when we get the new disc I will load it on to the pc that the key wouldn't change. I'm going try to run it as an XP repair and then make sure it has the correct legal key.

 

This functionality was damaged by recent changes to WPA , there's no way around it as of now I suggest visiting www.ubuntu.com!

Cheers mate!

 

Ok, the extra information you gave helps to clarify everything a bit. I've never used a "hacked" keygen to do a VLK installation. I just have a couple of known good keys that I use that I know will never go bad and in fact have been using them for going on 4 or 5 years. If you need a OEM installation CD, you can download them easily from any torrent site. Also, you only mentioned XP key changer.....which one are you using? Magical Jelly Bean keyfinder? If that's the one you're using, the newer versions took out the ability to change your key. I use version 1.51 and it has never failed me. I could send it to you if you like and you could try it to see if it works for you. Just let me know!

 

I just figured out they allow you to attach an attachment so here it is if you want to check it out. Some virus scanners might detect this as a virus, but I assure you it's not. It's just the nature of these type programs (keygens, key changers)

 

I have been using the Magical Jelly Bean to find the key then I use the key changer supplied here or if it doesn't work use MS key changer. The problem with the MS key changer is it reports back to MS. But now I'm to the point I don't care. It shows that I'm changing illegal keys to legal ones. If they were to show up at work It would be a race as to who would turn in the Admin 1st. When we get thru replacing all the illegal stuff with legal it is gonna cost close to $10k. The management is just thrilled with this.

 

It's not working anymore , I'm telling ya. I've been using OEM ISO's for 5 years and then changing the key's after installation completes and then BOOM! about three weeks ago it just stopped working.

 

I think you may be right since I have had to use MS key changer to ge ti to take on pc's.

 

Try using the old version of Magic Jelly Bean I attached. It shows you the key AND allows you to change the key under options. As I said, the newer versions took out that ability to change it. I believe they did it because of some lawsuit by Microsoft. But anyway, the version of the program I attached works....and works well!

I haven't noticed the changes you two have, but then again I'm using a different key changer than you two :-D I built a computer for a friend of mine using an old VLK key that was widespread across the internet and has always worked for the past few years. However, recently Microsoft has blocked it. Tonight I had to email my friend this program so he could change to a new key that I have that isn't blocked. I've had to do that 3 times in the past week and it's never failed to change the key. Give it a try and see if it helps either of you!

 

A Dozen MCE installations last week using our old methods all failed , So different results in different environments is not uncommon but We've wrote it off as non-functional.

 

Here's some screen captures from me! I think I know now why they took out the ability to change the key in the new versions. Read the print on the 3rd pic. rolleyes It does the same job that Microsoft's changer does but doesn't report back! :-D

http://img.photobucket.com/albums/v515/dallasr/mjb01.jpg

http://img.photobucket.com/albums/v515/dallasr/mjb02.jpg

http://img.photobucket.com/albums/v515/dallasr/mjb03.jpg

 

True enough! I don't ever mess with MCE. Everything I deal with is Corporate XP Professional.

 

I tried XP KEY CHANGER ,
yesterday and today, on 3 computers:
- oem to oem
- vlk to oem

it worked fine, maybe you used an old version, it seems they updated the file server in these days, that's what the support told me,

they emailed me the newest version and it worked great.

I do not believe that the problem is in the oem key, i believe it depends on the cd u used... just my 2 cents.