High CPU usage & higher temps after windows updates: How long?

[amovingtarget]

Hi everyone,

I've seen a few posts about this, but none too recent and none that specifically address how long to expect this to keep on...

Situation: Allowed windows to update this morning, it did several updates, and six in particular I suspect of being the cause of this "problem". I suspect the .NET Framework updates (6 today...!) to be the root of my high usage issue. I say high, but it's around 20%,sometimes shooting up to 40-60%. Usually I idle around 2%. Temps are now at CPU ~40C; MB ~30C. These are usually around 35C & 27C.

Oh,and I updated at around 11:30 AM, and its now 1:40PM.

Here's the build: No overclocking.
Windows 7 Ultimate 64 Bit
AMD Phenom II x6 1100T w/ CoolerMaster Hyper 212 Plus
OCZ Agility 3 (installed on Saturday; optimized for the OS) primary disk--no activity showing.
Thermaltake Chaser MK1 (more big fans than you ever need)
16GB RAM (not important)
And some other stuff not pertinent to the issue.

How long do you all think I should expect this behavior? I want to play a game dangit! Thanks for any input, and questions.

UPDATE: I just checked resource monitor and while I've never used it before, it shows a wmiprvse.exe at CPU 15, everything else is bouncing around at 0-2. i searched this online, but nothing but a Windows Server fix. What gives?

 

[amovingtarget]

Okay, this is REALLY strange. I individually uninstalled all updates from today and nothing seemed to matter. Okay, I uninstalled a patch for a steam game that I downloaded yesterday. No difference. Then, I turned off the "Drives Meter" gadget for my desktop, and voila. CPU back to 0-2%. Restarted to make sure it wasn't a fluke, and sure enough still low CPU. What the heck? Until today, this was never a problem. I really liked that Drives Meter. Since this is Windows and not Linux (can't use Conky), anyone have any other suggestions. I'll mark this solved right away if anyone says they have some idea of why this happened today; also, if no one cares, I'll mark it in a bit.