wmiprvse.exe constantly creating tzres.dll

Yes I have installed Office 2013 (which may be the problem), Evernote, Adobe CS5 Production Premium, Adobe CS4 Web Premium, Microsoft Mathematics and all the ThinkVantage software that came preloaded with my ThinkPad from Lenovo. All my Google searches seem to find Windows System Resource Manager as the culprit but I don't have that installed. The is-wmiprvse-a-real-villan.aspx form only  got me a ClientProcessId of 0 which is no help at all. I have run the fixit and I disabled a couple of startup entries, rebooted my computer but nothing has changed. By the way, wmiprvse.exe seems to also be messing around with registry keys associated with time zones??? As well as other registry keys. I have included a screen shot of procmon: http://sdrv.ms/QhGBFK. I have to stop the capturing or I get messages from windows that I am running out of RAM wmiprvse.exe keeps creating this file over and over and over again!!

I'm having the exact same symptoms except that I have Office 2010 and it's not on a ThinkPad, and my other installed software is different.  I have 4 GB of RAM and typically I have about 1 GB free.  Windows 7 with all the updates as of today's date.  My drive light is almost constantly on.  Out of 1.14 million events in a procmon capture, 985 thousand of them were wmiprv.exe.  And all of those were it accessing tzres.dll.

I've read about possible sidebar gadgets causing this.  However I still have issues even after shutting down sidebar.

I have also gone through closing all running programs to see if there is any improvement.  None.

Then I went into the Services applet and shut down all services I thought I could get away with one at a time.  No improvement.

Finally I went through Task Manager and killed all processes I thought I could.  Still no improvement.

I know it hasn't always been like this but do not know when it started.  However my computer is so slow because of this that it's hardly useable.

Please let me know what other info I can provide to help diagnose this issue.  I'd appreciate any help as I really don't want to wipe and reload everything.

Cheers,

Drew

I had this problem and was able to fix it.  I went to msconfig and disabled the startup of everything suspect.  When the problem went away I started adding back until the problem returned.  I found it was Mal-Ware by a company called Conduit.  Something called "searchprotect".

I have this issue too, and is still not fixed, and there is no malware in my pc, even on clean install of Windows the trouble persist.

Long story short, I've spent a day investigating the spikes my cpu made at idle (between 4% and 16%, the culprit was tzres.dll accesed by WMI trying to create a file over and over again.

Probable causes I found browsing the internet wirth their solution:

1) Windows Resources Management software - not installed on my system, an official patch exist if you're affected

2) Malware (opencandy, conduit etc...) - use an anti malware program like adwcleaner or hitman pro

3) Temporary solution with no culprit found - restart the Windows Management Instrumentation service, the bad behaviour will come back after reboot

None of these solutions satisfying me, I remembered Antivirus software use the time of your computer in their procedures to weed out malicious programs. TZres.dll dealing with timezones, I decided to investigate and VOILA, the culprit on my system is AVAST ANTIVIRUS.

Uninstalled and the spikes were gone, my cpu stays at about 2 to 3% at about 600 Mhz, perfect for my little atom tablet!

Hope this helps

PS: Now trying Panda cloud antivirus, as it is supposed to be light on resources and quite effective if you believe the last AV-comparatives test http://www.av-comparatives.org/dynamic-tests/

the culprit on my system is AVAST ANTIVIRUS too!

Old thread, but may have to do with Oracle VM VirtualBox.

very old thread - but one of the fist you find googling this problem.  A fix has been made available.  https://support.microsoft.com/en-us/kb/970067

Hi

I've found a definitive answer here (eg. solution to find the root cause : AV, etc.)

https://blogs.msdn.microsoft.com/wmi/2009/05/26/is-wmiprvse-a-real-villain/