[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2407
  • Last Modified:

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.
  • 2
2 Solutions
.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.
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.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now