Guest Mike M Posted March 28, 2008 Posted March 28, 2008 Win2008 server running in VMWare Workstation 6 with latest VMWare additions installed. Win2008 runs flawlessly in this configuration save for the wmiprvse.exe taking up 8-15% of the CPU. Turning off the Windows Management Instrumentation fixes the problem but is not ideal. Turning the WMI back on seems to "fix" the problem however the services "IP Helper" and "Windows Resource Manager" aren't automatically started when the WMI service is turned back on. Turning the IP Helper service back on has no ill effects on the CPU. But turning the Windows Resource Manager on brings the WMIPrvSe.EXE back to the top of the CPU's most used processes. Would leaving the WRM off adversely affect the system?
Guest Frankster Posted March 30, 2008 Posted March 30, 2008 Re: Windows 2008 Server, wmiprvse.exe taking up excessive CPU "Mike M" <nospam@nospam.net> wrote in message news:uftxZiRkIHA.4120@TK2MSFTNGP06.phx.gbl... > Win2008 server running in VMWare Workstation 6 with latest VMWare > additions installed. Win2008 runs flawlessly in this configuration save > for the wmiprvse.exe taking up 8-15% of the CPU. > > Turning off the Windows Management Instrumentation fixes the problem but > is not ideal. Turning the WMI back on seems to "fix" the problem however > the services "IP Helper" and "Windows Resource Manager" aren't > automatically started when the WMI service is turned back on. > > Turning the IP Helper service back on has no ill effects on the CPU. > > But turning the Windows Resource Manager on brings the WMIPrvSe.EXE back > to the top of the CPU's most used processes. > > Would leaving the WRM off adversely affect the system? Not an expert here, but... I recently had a case where there were some documents stuck in a non-existent print queue (printer had been removed but user printed to it) and the wmiprvse was taking a ton of CPU cycles trying to print to this non-existent queue. So was the crss process (or similar). That left the system idle process fluctuating between 10 and 20 percent. Anyway, deleting the documents from the phantom print queue fixed the issue. Something to look at. -Frank
Recommended Posts