Friday, March 09, 2007

Curse you wmiprvse.exe process

This process has been a pain in my arse lately. I'm working at a client site that seems to make copious use of this process within their internal network. First of all, what is this process used for...

Yep, it's part of the Windows operating system. Makes sense why a company might want to use this tool for collecting and setting information on client desktop systems. What doesn't make sense is how the process renders my development laptop totally useless when it is activated. I'm assuming the process always runs, but stays silent until activated by some WMI remote calls. At that point, the process sucks 80-100% of the CPU for a long durations of time (minutes). Particularly irritating when attempting to build a large Visual Studio solution or testing our WPF application. If you kill the process from task manager, it just comes right back. I probably kill this process 5-10 times per day.'s damn frustrating!! One more reason why not to use Windows for a development environment. I really like a lot of .NET and C#, but hooking it up to the Windows XP operating system cripples the .NET platform. I'm going to have to investigate Mono one of these days. My Ubuntu Linux boxen don't exhibit this type of behavior ;-)

powered by performancing firefox

1 comment: