http://blogs.msdn.com/wmi/archive/2009/05/27/is-wmiprvse-a-real-villain.aspxHow often has it occurred that you were working on something and suddenly your computer became slow? You opened task manager to find out the culprit that is hogging your systems CPU cycles. You sorted the processes according to CPU usage and saw WMIprvse.exeen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/wmi/archive/2009/05/27/is-wmiprvse-a-real-villain.aspx#9643246Wed, 27 May 2009 06:12:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:9643246Is WMIprvse a real villain? | ASP NET Hosting<p>PingBack from <a rel="nofollow" target="_new" href="http://asp-net-hosting.simplynetdev.com/is-wmiprvse-a-real-villain/">http://asp-net-hosting.simplynetdev.com/is-wmiprvse-a-real-villain/</a></p> http://blogs.msdn.com/wmi/archive/2009/05/27/is-wmiprvse-a-real-villain.aspx#9644308Wed, 27 May 2009 14:29:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:9644308Christoph Voigt<p>Thanks for the tip Varun, but is there a chance to find the real villain in XP too? Usually we use ProcessExplorer and look at the threads wmiprvse is starting but this has one huge disadvantage: it's realtime only. </p>http://blogs.msdn.com/wmi/archive/2009/05/27/is-wmiprvse-a-real-villain.aspx#9726171Thu, 11 Jun 2009 11:16:44 GMT91d46819-8472-40ad-a661-2c78acb4018c:9726171someone who complains a lot<p>What OSes is this tip valid for? When you publish tips like this you should always say what OSes it is valid for. That said, it is very useful, for a few of us anyway.</p> <p>Thanks</p>http://blogs.msdn.com/wmi/archive/2009/05/27/is-wmiprvse-a-real-villain.aspx#9815147Fri, 03 Jul 2009 01:04:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:9815147nitin<p><a rel="nofollow" target="_new" href="http://blogs.msdn.com/ntdebugging/archive/2009/04/24/using-netmon-to-figure-out-the-source-of-high-cpu-in-wmiprvse-exe.aspx">http://blogs.msdn.com/ntdebugging/archive/2009/04/24/using-netmon-to-figure-out-the-source-of-high-cpu-in-wmiprvse-exe.aspx</a></p>