WMIPRVSE process is overloading the CPU

The WMIPRVSE process, currently running under NETWORK SERVICE, is using the majority of my CPU on two workstations here. This problem started occuring last night after .NET 1.1 SP1 was installed on both PCs.

I've checked the PCs for viruses, but this isn't the cause.

Although please bear in mind that .NET 2.0 was already installed when .NET 1.1 SP1 was installed. An option in WSUS was accidently set to INSTALL on the .NET 1.1 SP1 option, which caused the auto update to occur.

Would uninstalling .NET Framework 1.1 fix the problem? Any assistance would be greatly appreciated.

Thanks in advance.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

.net1.1 and .net 2.0 are very compatible and can exist on same machine with no problmes. Never caused me problems with them being together. For more info check this: http://msdn.microsoft.com/netframework/default.aspx?pull=/library/en-us/dnnetdep/html/netfxcompat.asp

Also coming to the question: you can try  uninstalling it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You could try checking the WMI logs in C:\WINDOWS\system32\wbem\Logs for any information that might explain what WMI is trying to do. By default it's only set up to log errors, so if you don't see anything in the logs you can change it to verbose logging mode in wmimgmt.msc.
DReade83Author Commented:
Yeah, I've run a System Restore now, which seems to have sorted out the problem and only .NET 2.0 is installed now.
DReade83Author Commented:
Apologies for not replying sooner. It turns out HP drivers were causing this problem to occur! Good old HP eh!

Anyhow, all fixed now. Thanks anyway, much appreciated.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.