Windows update issues with new drive

I just installed a new seagate 1.5 TB drive into my system, check specs below

I forgot to activate Vista 64 bit ultimate and went to the windows update site, I was never prompted to activate, but I was given 59 updates which took an hour to download and install if not more
At the end of it one update failed to install, I carried on and restarted, Vista went through its pretty green screens, then the reboot and the wait, Vista sat at 100% for over 15 minutes, then I return to the pc to get the message that the updates were not configured properly and that the OS was reverting the changes, another hour and the machine is back to normal
Is this MS's punishment for not activating? or is my quad core not powerful enough for their bloatware
Heres the specs on my box

Asus p5QE mobo
Intel core2 quad 2.4 ghz
8 gigs of Corsair ram, Matched sets for dual channel
Evga gforce gtx 285
Auzen sound card. XFI Forte
Corsiar 1000 watt power supply
Samsung DVD burner
USB card reader
Seagate 1.5 terabyte drive
Vista 64 bit Ultimate

My Os came back from this adventure, hopefully intact, I am running Norton 2009 AV and I am behind a Linksys firewall WRT54G

I may try the update again, maybe try and get SP-2 for Vista Ultimate 64 bit

Now back to my second life , thanks in advance folks

This isn't unusual. I have seen some updates that failed and needed to be redone a few time.
It isn't punishment for you not activating. LOL!
Nor is it that your quad core isn't powerful enough.
Retry the updates again and see if they work.
Sometimes its other things running in the back ground.
You can also check the update logs and see what they say.
http://support.microsoft.com/kb/906602

Thanks Ferrit, What I did was download SP-2 and then run the install, I shut down Norton 2009
I did have a blue screen event, but I forgot to turn off the auto restart, Could have just been a glitch
I am going to try Windows update soon and see what happens, There should be fewer updates now that I have SP-2 installed
I did check the update logs and found an issue with dot net 3.5 SP-1 and Windows power shell All the error codes were the same, except these two , and there was no info from MS on the codes
I will keep you posted as to what happens