This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WMI Host Provider high CPU when running Garmin Express

This was also reported in the thread about GE using 20% CPU, but I thought the WMI-specific issue should be highlighted in its own thread. The problem was also reported in the Forerunner 945 forum. I had been trying to figure this out for a while until I saw that post. Sure enough, quitting out of GE made the high WMI CPU usage stop.

GE 6.19.3.0

Top Replies

All Replies

  • Former Member
    0 Former Member over 5 years ago

    Same issue, even after updating to 6.20.0.0.  I've had this problem for months now, and probably more than four GE updates failed to fix this issue.  Come on Garmin Developers - This is really annoying!

  • For what we know, the developers aren't even working on it nor they know about it. 

  • The best way to ensure they do know about it is to report the problem directly to the support people.

  • I did raise this - just to be on the safe side - with Support nearly two weeks ago only to be told:

    "This is something we are looking into, but not something we have managed to replicate on our side at this point"

    Talk about real-world scenarios when QA tests are executed!

    Needless to say that GE 6.21 released very recently exhibits exactly the same problem - and I did let Support know about it earlier today.

  • Aside from the non fix, it is also annoying that each update reenables the software to run in the background.

  • Yeah, I passed that on as well - but I'm not hopeful that anything will be done about it.

  • I do have same problem and the update to 6.21 did nothing to solve this.

  • I have same problem. I wondered that troubles with WMI occurs from GE :(

  • Former Member
    0 Former Member over 5 years ago

    I too have found WMI to be affected by this problem. Interestingly, before finding GE to be an issue, I restarted WMI service, and this solved it also (not that I want to do that every time I boot). WMI then used even less CPU than it did with just quitting GE, which is interesting.

  • Same behavior Garmin Express v. 6.21.0.0 on windows 10.

    Even after quitting from Express WMI continue consuming CPU for a minute.

    No Express running - CPU is ok.

    I see a lot of logs in event viewer like this:

    Operation = Start IWbemServices::ExecNotificationQuery - root\cimv2 : select * from __InstanceDeletionEvent within 2 where TargetInstance ISA 'Win32_Volume' AND TargetInstance.DriveType = 2; 

    IMHO, GE bombards WMI with this request. That's why WMI is overloaded.