Windows Update key checking

[Grzyb]

Quote:

- Generated keys will work fine for getting SP1 installed. However, don't forget that when MS turns on Windows Update key checking (rumored to be in early October), Windows Update will go bye-bye.

Just read this on another forum.....

What's everyone's input on this......!!!!

[Dudelive]

Yes I have read the same and it may be problems for some people. I just installed sp1 and changed the clock ahead 1 year and NO updates. Changed it back and 3 updates are there again. I wonder alot of things right about now......LOL

[greasemonkey]

The key checking will be done on Microsofts end (comparing your key to a list a of possible valid keys) so changing your system date won't test the microsoft update check.



Last edited by greasemonkey at Today at 7:51 pm

[Dudelive]

@ greasemonkey That is what I am wondering, if microsoft does check on there end then would it not also be able to not let you see any updates if the key does not match. Questions, questions questions
I guess we will wait and see how it turns out.

I think I will do a CLEAN install and update, then see what happens. I have installed several betas on here over top of one another. I did unstall the betas before installing this one. Maybe a clean install will erase lots of questions for me anyway

[TheCrossMovement]

Yeah, it'll erase everything ELSE you have too..... LOL :P

[NutCracker]

If you've used a KeyGen to generate yourself a new key, which is accepted by WinXP, then how are MS (via the WindowsUpdate) going to know that your key is dodgy ?

There not! They have no way of knowing the difference between a valid purchased WinXP with a valid Key and a Devil'sOwn release of WinXP and a KeyGen'd key.

I guess the more keys that are published as 'working keys' for all to use will end up over time being on MS's blacklist set of keys and will refuse to work with WindowsUpdate.

I think there's nothing to worry about if you don't use WindowsUpdate and if you do and your key becomes blacklisted, then I guess generating yourself another one will resolve the problem ?

Comments ?


Nutz

[Jupiter2k]

In no time there will be a Sp1 *REPACK*

there .. it should solve all the ill and worries ?

[poolman]

And if all else fails someone with a "vaild" key will get the updates and post them somewhere for all to grab.

[ecperez]

Quote:

Originally posted by Dudelive@Yesterday at 11:38 am
Yes I have read the same and it may be problems for some people. I just installed sp1 and changed the clock ahead 1 year and NO updates. Changed it back and 3 updates are there again. I wonder alot of things right about now......LOL

I made a new slipstream XP Corporate and try a clean install, and successfully installed it, try to check the Windows Update i have 3 files to download. Tried to advanced the date to 1 year ahead, and checked it again, yes there is no update anymore... strange..

Is it because the windows update check those drivers wether its too old to download... so thats why windows update never display it on the listing..

but reset back to its ordinary date the 3 update was there..

so Dudelive you're not alone.

[ecperez]

Found on another board ....

Quote:

(Black Talon @ 31st August 2002 - 09:44)
Installed a slipstreamed 1106 and all went well using genned Corp key. Checked Windows Update and it worked fine, but:

Something's weird here.

I set the date ahead in the BIOS one year to check for time bombs. Rebooted and everything was fine, but when I used WinUpdate it said there were no updates to install, even though there are. I kept setting the clock date back. When I got to May 3, 2003 Windows Update started working again! If I advance the date to May 4th it stops! I counted the days from today and it's 242 days. Does this mean there's a time-bomb here or is this just nornmal procedure? Anyone know? I'm ready to install this slipstreamed sp1 on a new box I'm building but I don't want to if it's going to quit working in the future.

After this happened with Corp Ed + sp1 I decided to slipstream my retail XP Pro with 1106 and see what happened. This install has the same "Windows Update Lockout after 242 days" that the Corp Ed has. So I guess it's just normal and not an M$ anti-piracy thing.