Hi Folks,
Have the same problem, but dug in deeper. 2 Windows 7 and 1 Windows 8 machine affected with same problem.
When you look close you see the system tries to create tzres.dll and immediately after it fails it tries to create tzres.dll.mui in the localized map in the windows\system32 folder.
After it fails to do so for 100 times (you can actually filter in procmon and see it happen) the process starts to read the objects.data file in the Wbem\Repository.
The WMIPRVSE services can be stopped with the penalty of stopping the IPHelper and Security Center services as well.
tested;
WmiPrvSe stopped + IPHelper stopped + Security Center stopped = No disk activity anymore - problem away
WmiPrvSe running + IPHelper running = problems
WmiPrvSe running + Security Center running = problems
Shutting WmiPrvSe totally is a problem because I have other software relying on the WMI event Sink like for Instance my office file synch and Defrag software.
Setting the debug option on the WMI Event Sink gave me a bunch of extra info, but always led to svchost as the culprit since the Sink service is running there and notifies all back with, off course, the same proc id.
And with no spirit to dive into the cim files to see what's in, the track ends here for me.
I have no more time to fiddle around to get the exact avast part up on the table, so avast, please fix this fast!
It will enhance the performance of the computer it's running on, since it's now trashing capacity,
(On my SSD it takes like 1-3% of queue length when loaded fully) that must be a nice performance improvement for all.