WmiPrvSe.exe is calling tzres.dll multiple times per second with Avast

[bluto32]

Thank you for taking the trouble to reply.

I don't think that Avast is a scapegoat in my case due the following:

• If Avast is allowed to start-up normally when rebooting, the problem appears
• If Avast is prevented from starting when rebooting, there is no problem... until Avast is started manually, in which case the problem appears.

I'd be interested to know if other users reading this post have the same issue. It is easy to check with "Procmon", a tiny (974 KB) download from Microsoft. Simply run Procmon, click "OK" on the filter box that appears, and then turn off the following from the main window:

• registry activity
• network activity
• process and thread activity

That should leave only "Show file activity" selected. If you have the same problem with Avast as me, your screen should very quickly look like the image in the post above from "thedrs", with wmiprvse.exe accessing tzres.dll and tzres.dll.mui 100s of times each second.

Bluto

[bob3160]

I've reported this topic to Avast let's see if that get's a reply from Avast.

[bluto32]

Did you hear back from Avast?

I sent them a ticket about the problem shortly after you, but haven't had a response other than an automatic reply. Of the four people I know personally who use Avast, all four experience the same issue. I'm guessing it's very widespread.

Bluto

[Asyn]

I sent them a ticket about the problem shortly after you, but haven't had a response other than an automatic reply.

Post your ticket-ID.

[pk]

Hi guys,
we have fixed this issue in Browser Cleanup component and it'll be delivered through an emmergency update on Monday. We'll let you know when it's released.

Thanks

[bluto32]

Many thanks for the info (I have also seen your email reply now) - much appreciated.
Look forward to the update.
Bluto

[pk]

We just released minor update for this issue (for Avast 12.3.x version) -- it'll update AvastUI.exe file within 4-6 hours or immediately after several minutes when a user logs in to Windows. System restart is required to apply the patch, because AvastUI.exe process is running in background. Please verify the change and let us know if it helped.

Opening tzres.dll very frequently isn't critical, because this file is small and already cached in system memory, but I agree Avast should avoid using WMI queries to cause these side effects in system.

[bluto32]

I have just rebooted and can confirm that the fix seems to have done the trick.
The build is showing as 12.3.3154.22 now (rather than .21) and wmiprvse is behaving itself.

Many thanks for resolving this,
Bluto