So I had a little spare time just now, and decided to se what was happening on facebook. Nothing, as it turns out. Seems like all the applications are broken. They can’t be added or used.
Ho hum.
Anyhow, back to a pet peeve of mine: Microsoft will you fix this please! Windows Update. More specifically, Windows Update on Windows Vista and Windows Server 2008.
You might recall my previous post about "TrustedInstaller.exe". Well, since then, I’ve done more digging. This process is spawned not just by the Windows Update service or the licensing service, but it also fired off when Windows decides to go and see if any updates are available.
Now, I can’t be 100% sure, but I seem to recall this process was being spawned even if "Check for updates" was disabled. I’ve disabled checking on Windows Server 2008. It remains to be seen whether it will cause problems or not.
Now: to the beef. Microsoft you *have* to fix this damned process. It is completely unacceptable for what is supposed to be a background process to be chewing up close to 100% CPU!
Secondly, why does it chew so much CPU doing a check for new updates? Who wrote this thing and did such a bad job? Why didn’t QA pick up on it?
Last part for the day: Hibernation. It happened on Vista and certainly does it on Server..
When the machine hibernates and restores, for some reason arbitrary (I assume this is on a first come, first serve basis) processes that request CPU time get max CPU. When you kill the process, the next process to request CPU time also gets max CPU.
This seems to continue until you reboot. What gives? QA department missed this too?
Anyhow… cheers
