win xp & windowsupdate

I've searched the forum but found no similar problems.

I had a WinXP installed with the FCKGW serial.
Used the Blue List Keygen and got 3 640 keys in 200 searches and 15 64x keys.
I have a copy of a retail Win XP CD.

Now, when I install (I tried it with 2 of my 640 keys and one simple pro key ***) and I try to go to windows update,
I have the green button "search for updates". When I press it the counter never passes 0%

and I really need them hardware updates...

Anyone any idea or a solution (other than search your shit elsewere)?

This is what my face looks like for the moment -> :(

and this is what I want it to look like -> :D or :cool:
or even :eek: if it's something stupid I've done (except for using xp... I like xp! Don't shoot me for that...)


*** I can now add an OEM serial number to that list...
 
Last edited:
check to make sure you aren't blocking any msn cookies, that your firewall isn't blocking the site or is in stealth mode etc... .
Then you shouldn't have a problem.
Good luck
 
Windows Update should work with they key you used. However some firewalls eg. Sygate block info needed by the update server.
However I always use the corp update option.
_http://v4.windowsupdate.microsoft.com/en/default.asp?corporate=true

If you update this way all updates are saved on your HD for use over and over again.

LaZorMan
 

dx

1
--dolfijntje--

The posts above are all sound advice.

1) Disabling cookies in IE and any third party cookie crusher leads to the problems you are having. M$ needs to put a cookie on your system to use Windows Update (even says this on their site). You can delete the cookies after update.

2) Related to above...clean out your IE cache. Sometimes the cache of a bad update can interfere with the next time you try.

3) Personal Firewalls can be problematic esp. Sygate (as was mentioned). Disable it for Windows Update.

4) You did try Update more than once...esp. on another day?! Windows Update gets bogged down from time to tme. I have found that if you can wait a day, then try again, it works just fine.

5) You say you used a "retail Win XP CD" and the FCKGW serial. This is a Corporate key so you must have done something to your retail CD to get it to take that key. What? Did your version ask you to "Activate Windows" after installation? Also, what version is it...Home or Pro?
 
The thing is I've reinstalled it each time to use another key.
So when I tested it, they were clean installations without firewall & cookie blocker or anything of that kind (did forget to deactivate MS' own firewall but that one sucks and couldn't be the cause, could it?)

Used an MSDN cd with the corp keys, thought it could be something with the cd, borrowed a retail XP PRO cd & used the Pro & OEM keys on em.

The MSDN cd should be the same as a normal one since no unattended stuff is present on the cd

@dxkim: will test the corp keys on the retail cd, you say that shouldn't work?

@LaZorMan: I can indeed go and search for the updates through the link you've mentioned but have you ever tried to look for a hardware update that way? My problem is that the hardware manufacturer's drivers do shit, but MS' update actually works!
 

dx

1
--dolfijntje-- said:
@dxkim: will test the corp keys on the retail cd, you say that shouldn't work?
I wouldn't !
It's best to use the right key with the right version...ie, OEM key for OEM, Corporate key for Corpfiles/Devilsown, Pro for Pro, Home for Home.

The main reason for not using Corp keys on Retail is simple. Corporate XP does NOT need activation, but Retail Pro and Home versions DO. So even if you get your retail to accept Corp key (never tried it but some say they have successfully) you are going to have to use an activation crack. Otherwise when you activate, M$ will know you are using a Corporate key with a retail version... and oops your XP stops working after a Wimdows Activation.

If you want to convert your retail version, give a gander at my tutorial here:
http://forum.cdrsoft.cc/showthread.php?s=&threadid=828&perpage=15&highlight=blade runner&pagenumber=2

Read the entire thread though, as most questions are answered with in this long thread.
 
Done that, I used my cd (I will no longer say Corp CD) and at first I didn't have a corp key but a pro key (had a dozen of them)
and I did indeed have to activate.
Then fckgw came up, the next time I reinstalled I used that one and didn't have to activate...

So is my cd a corp or a pro?

As you (dxkim) say if I use a corp key with a pro cd I'lld still have to activate, and a pro key wouldn't work on a corp cd...

my cd accepts corp (no activation needed), pro (activation needed), and OEM (activation needed) keys...

I'm getting kind of paranoid here...
I would so much prefer hearing that it's stupid me that has done something wrong than that MS has blocked my IP or stuff like that...
 

dx

1
--dolfijntje--

I don't think M$ has blocked your IP. I have yet to hear anything that drastic from them. Disable your XP...absolutely! I have spoken to several members on this list that this has happened to.

As far as keys, there is some fudge factor and some versions like Corporate may well indeed accept other keys. I know there are list members who claim this key swapping worked for them, but somewhere down the road they have troubles. This is usually after Activation or Windows Update.

You see, Corporate and OEM XP don't need activation with Microsoft, but the other standard versions do. So if you put a Pro key into a Corporate version, you will have to activate it with M$. At Windows Update, M$ sees that you are using the wrong key for the wrong version and surprise...after Activation or Windows Update your windows stops working.

Now, my attitude is why tempt fate?! M$ is not stupid they are trying to stop this "piracy" of XP. Why not just use a Corporate key with a Corporate version? And yes, my tutorial teaches you how to make an XP Corporate CD. The files, as the story goes, came from a true Corporate CD. They were then zipped and distributed all around the Net as Devilsown and/or Corpfiles...but in the end it is still a Corporate CD. It even came with the infamous "fckgw..." key, which is rumored to be Disney's old Corp key. I say old because M$ asked this Company to change the key, so M$ can ban it.

In the end, if none of the tweaks by Shadoe, LaZorMan, or myself don't apply...then yes I think you may have a bummed XP install. The Beta SP1 users who tried the "fckgw..." key have found that Windows Update no longer works. They can go to the site, but can't download anything from Windows Update. This is, BTW, exactly what M$ said it was going to do with pirated copies of XP.

So has this happened to you...seems possible. Give it one more try at Windows Update and if its still not working, then found your answer you have, No?!

On your next install, try using a Corp key generated from BlueList keygen with your Corp CD. I have yet to hear of a problem with this solution (except a bad Corpfiles conversion). SP1 may change this, but for now just go with what works.

Good luck!
 
I will give it a try! I've downloaded the corpfiles & will test it...
I hope this weekend... uless the "ball & chains" has other plans...

Thanks for all the info! you guys rule!
 
For some people, you have to add a s after the http so it's like this:

ht*ps://v4.windowsupdate.microsoft.com/en/default.asp

Give it a shot and let us know if it works!
 
--dolfijntje-- when you get to the corp download site there will be two options for you..."Find updates for Windows operating systems" and "Find driver updates for hardware devices"

That should be what you´re looking for, isn´t it?

LaZorMan
 
For f*ck sake!!!

Don't get me wrong here, I am as happy as a person could be in this situation...

How do you explain that fact that it DOES WORK with the secure httpS way... (_http://windowsupd... still doesn't work)

Till now I've always protected MS, it might be worth shit but hey... it's the best we've got...
But this... I can clearly see that my MCSE status should better be changed into ChimpanCSE...

I'm ashamed of myself!

@Almighty1: It was fate that gave you that name!

-----------> Am still curious about why this works... (on a clean install) <-------------

Okay people, I give up! I'm shutting down my puter and am going outside to play...
maybe get drunk...
and pee on a trashcan with MS-ads on it...
definitely do that...


@shadoe_phantom, dxkim, LaZorMan & last but certainly not least Almighty1: You guys may not know it but you rule... BIG TIME

I tried the corp download site and did find the hardware update I was looking for... all 20 of them... for the same sound card... no shit, check it out for yourself. It's an ESS sound card (default in Compaq Portables) and there's about 20 ESS updates with only some numbers which I apparently can't really rely on...

but I will get my other updates that way, thanks LaZorMan!

See you around...
 
--dolfijntje--.

I have no idea why it works the https way only on some machines since on mines, http works perfectly for me but not for others according to posts on neowin. The Corp updates have one problem, it doesn't really show the model number, it only shows the manufacturers name. When you try h*tp://windowsupdate.microsoft.com - does it work at all?
 
It seems to be working but when you press the green button "search for updates" it never goes further then 0%...

only with the https does it show the updates...
 
Top