Hi, I have noticed a process called WMI Provider Host is taking always 2-3% of my core i7 Devils Canyon CPU. If i uninstall avast this process disappear and my CPU returns to 0%.
I use Windows 8.1 Pro with the latest December updates, Avast is 2015 SP1 2208.
So please avast team, can you take a look on that an fix it? Thanks.
It can be caused by malware.
Please follow the instructions:
https://forum.avast.com/index.php?topic=53253.0
Tried what you say. In any case this is not the problem. I can see the same problem on friend´s laptops with avast, and even worse because laptop processors are less powerful so i´m talking about 10 % CPU usage of WMI Provider Host, that dissapear when uninstalling the latest avast antivirus.
Today i´m going to format the pc with the latest windows 8.1 with update 3 iso. I´ll comment later.
May be what Eddy says or issue with Microsoft: https://social.technet.microsoft.com/Forums/windowsserver/en-US/b3ae538c-35cc-4669-be85-b09724ff1015/wmi-provider-host
Use clean boot to troubleshoot rather than uninstall avast!
Ok, I have formated the pc with the latest windows 8.1 iso with update 3, clean install. Inmediatly after avast is installed, WMI Provider Host is here again but this time changing between 0-0,4% of CPU. So I think it´s clear that avast has a problem with windows 8.1. Please some moderator can report this to the avast team? Thanks
The only solution at the moment is changing to another antivirus. I feel sad about that because I like avast. Hope avast team fix that…
Sounds like you may have something else going on ???
http://www.screencast-o-matic.com/screenshots/u/Lh/1419376569101-32065.png
Ok, I have formated the pc with the latest windows 8.1 iso with update 3, clean install. Inmediatly after avast is installed, WMI Provider Host is here again but this time changing between 0-0,4% of CPU. So I think it´s clear that avast has a problem with windows 8.1.No, it only shows that it is working fine now. It doesn't say anything about the cause of the problem which could have been malware as I said before.
You came here asking for help, but you have refused to accept help. >:(
What? As i say before i run malwarebytes as you say. No malware in my pc. Did a clean install and the problem came again after installing avast. So yes, it is a problem with the latest version of avast 2015. If I came here is because i like avast and i don´t want to change my antivirus.No one from avast team in this forum take note of that, and try to solve it in a future version. Sorry but avast 2015 is shit, you came here to help me, but you have refused to accept that it is avast fault. Due to all this things i have to change to eset.
That´s what i say. WMI provider host always with 1% or similar. No problem if I return to avast 2014. And as i say before no malware on my pc.
My screenshot is from my system. Windows 8.1 Avast free 2015. as you can see, no problems with excessive use.
What? don´t you see the 1,2% of WMI Provider Host? 1,2% by the face, thanks to avast 2015. Common…
And what makes this a problem ???
Oh yes…I bought a core i7 devils canyon to waste CPU on absurd processes…
If it’s slowing down your i7 them maybe there’s another problem.
It certainly isn’t hampering the i7 I’m using.
I have encountered the same problem after formatting my PC for unrelated reasons. I saw reduced battery life right after installing Avast. WMI increased CPU usage from 0% to 3% on my ultrabook. While I wouldn’t give a rat’s ass on a desktop, this prevents CPU from going into low-power state.
If you restart the service, CPU usage is back to 0%, until computer reboots. Such behavior indicates that it’s a bug.
uninstalling Avast also causes WMI to chill out.
Please look into it.
Seeing that this page has >500 views, it’s a commonly encountered problem. For those of you who still want to use avast on mobile computers, you can do as follows:
Create a text file, and enter the following:
net stop Winmgmt /y net start Winmgmt
Change the extension from .txt to .bat
If you don’t know how to change extensions you probably should not proceed with the tutorial
Running batch file with admin privileges will cause Windows Management Instrumentation service to restart.
It will also shut down all services that depend on WMI, and some do not restart automatically.
Check Local Services > Windows Management Instrumentation > Properties > Dependencies Tab
https://akopyan.me/meh/AvastForum/10.PNG
Those services must be restarted
You need to find service in the list, it’s name is shown here:
https://akopyan.me/meh/AvastForum/11.PNG
My bat file looks at follows:
net stop Winmgmt /y net start Winmgmt net start TPCHSrv net start "TOSHIBA eco Utility Service" net start iphlpsvc net start wscsvc
Note that you need quotes if the service name has spaces.
Also note that if you install some software that uses WMI services you will need to add it to the list later.
Now we need to make the script run on startup. This is done using the task Scheduler.
Choose “Create task” on the right side of the window,
Name it as something identifiable
Select “Run whether user is logged on or not”
You must tick “Run with the highest privileges”
https://akopyan.me/meh/AvastForum/12.PNG
In Triggers tab Choose “at user logon” and choose to delay task 1 minute.
In Actions tab choose the batch file we just created
In Conditions untick “Run only on AC power”
You are done! Now WMI will be restarted after your computer boots and will stop killing your battery life.
Why are you defending avast? A bug is a bug, no matter what percentage of CPU is wasting, that should be fixed.
I’m not defending at all. I just don’t know if it’s really as serious as you seem to lay it out to be.
I’ve alerted the Moderators and hope Avast will respond to your report.
I’d encourage anyone who has the problem, and has appropriate technical skills, to help us analyze the issue. I still think Avast is kind of innocent in this (or, more precisely, its presence may work as a trigger for something else, but it’s not Avast that is actively doing it). But I’d be happy to be proven wrong here.
To start, it would be good to use Process Explorer to get more info on the WMI Provider Host process instance. If you right-click the offending process in PE and select Properties, you should see the “WMI Providers” tab. What does the list on that page say? And also, if you go to the Threads tab, you should see which thread is taking the CPU, and you can even display its stack trace (assuming you have the debugging symbols properly configured in PE).
Thanks
Vlk