I actually experience that problem, and I just kill the svchost.exe whenever I first power up — once I see which one it is that is running wild.
I think I had that problem some years ago and dropped back down to w2k on one machine because of it, thanks to a kind FReeper that was willing to help out with some data. The next machine I dealt with I immediately backed up the original partition before running anything and never allowed it to be connected online while running 'doze on it and disabled the autoupdate. Seems to have been quite stable after that.