Jump to content

Recommended Posts

Hi

I have Windows 10 64 bit pro. And Eset internet security.

About once a week in action center I see WMI provider (maybe provisioner) stopped responding.

I tried everything to try and resolve. When I installed the May 2020 2004 update it continued.

I thought I would be try without Eset for a while and the reports have stopped?

Always used on default settings.

Anyone else see this?

Thanks.

Link to comment
Share on other sites

The only thing I see in my Win10 WMI-Activity Event log related to anti-virus is shown in the below screen. These entries in multiple successive sequence have appeared as long as I have been on Win 10. Also not sure these are related to Eset or instead possibly, the Windows Defender to Eset AV use hand off at system start up time. Never seen any Win 10 Action Center alerts either.

Check your Win 10 WMI-Activity Event log for entries related to these Action Center notifications you have been receiving. These might provide further details on what is going on.

Eset_WMI.png.bd8e53ce328a4e879904d95fb343e575.png

 

Link to comment
Share on other sites

I will keep my eyes open.

I really shouldn't have deleted them all.

I was positive more would appear.

They didn't.

The entries in action center were not very informative.

Thanks for the reply.

Link to comment
Share on other sites

  • 1 month later...

@itman where I can find that Event Log, in event viewer? I saw it for the first time in Reliability Monitor. What I did was uninstalling Kaspersky Internet Security and installing ESET Internet Security:

 

image.png.879c7803d816f5207e517851bb89470e.png

 

Edited by r1man
Link to comment
Share on other sites

7 minutes ago, r1man said:

@itman where I can find that Event Log, in event viewer? I saw it for the first time in Reliability Monitor. What I did was uninstalling Kaspersky Internet Security and installing ESET Internet Security:

Did you reboot after uninstalling Kaspersky? If not, this plus the subsequent install of Eset might have cause WMI "to flake off."

Does the WMI issue persist today assuming you have rebooted since 7/9/2020 6:41 PM?

Link to comment
Share on other sites

Thank you so much @itman for your reply. Yes, I did reboot after uninstalling Kaspersky, also did reboot (if I am not wrong) after Installing ESET Internet Security.

No, it didn't happen today. I fully turn off the PC every night as well. 

Thanks.

Link to comment
Share on other sites

I never solved this.

Windows 10 pro on desktop and home on laptop.

Would appear about once every three days.

Reverted to defender on both now.

Couldn't work if out.

Link to comment
Share on other sites

8 minutes ago, Wrogg said:

I never solved this.

Periodic WMI crashes have occured before: https://support.microsoft.com/en-us/help/959493/the-wmi-provider-host-program-wmiprvse-exe-may-crash-on-a-windows-serv

So I  suspect an issue exists in Win 10 2004 given all its problems to date. Why this might manifest with Eset installed remains to be determined.

Link to comment
Share on other sites

30 minutes ago, bobcat said:

I have had this problem at least once daily since I installed the latest update to ESET NOD32 on July 7.

Have you upgraded to Win 10 2004?

Link to comment
Share on other sites

@itman I had WMI stopped working today after the day of 7.9.2020 that when I installed ESET Inernet Security.

Maybe today it happened because I did a full scan?

image.png.b4bc4bdeefc65b8d1168b0633f2278c5.png

Link to comment
Share on other sites

4 hours ago, r1man said:

Maybe today it happened because I did a full scan?

Doubtful that was the cause. After the latest Eset upgrade, I ran a registry and WMI scan. No WMI crash as a result or for that matter, at any time previously.

Link to comment
Share on other sites

Here's an article on WMI issues from Microsoft: https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-common-symptoms-and-errors/ba-p/375483

Possible crash reasons:

1. High Memory Usage by WMI Service or Wmiprvse.exe

  • Lower than normal available memory on the system
  • Instance of wmiprvse reaching or exceeding 512 mb on Vista and newer, or 128 mb on XP or Windows 2003: Quota Violation issue
  • Large repository C:WindowsSystem32WbemRepository folder and objects.data file is 1gb or larger

2. High Handle Count on WMI Components

Source: Microsoft-Windows-WMI
Event 5612 Wmiprvse.exe exceeding handle quota limit Event

WMI has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4

Link to comment
Share on other sites

15 minutes ago, r1man said:

@itman 

Marcos posted:

 

 

Like I posted previously, I have run multiple WMI scans in testing today and WMI never crashed on my device.

Link to comment
Share on other sites

I had this on two different PC's for nearly a year

I waited to see if the May update fixed things that's when I gave up.

If that helps

Below is on Defender

 

Action.jpg

Edited by Wrogg
Link to comment
Share on other sites

For anyone having WMI issues; notably crashes, refer to this: https://www.thewindowsclub.com/how-to-repair-or-rebuild-the-wmi-repository-on-windows-10/

To begin, open up an Admin level command prompt window and enter this:

winmgmt /verifyrepository
Quote

If the repository has an issue, it will respond “repository is not consistent,” if not then its something else causing the issue.

 

Link to comment
Share on other sites

I got this:

image.png.ea857b2971683e545bb167b755693105.png

 

But I have WMI crashes in case I run a full scan in ESET Internet Security.

Edited by r1man
Link to comment
Share on other sites

42 minutes ago, r1man said:

I got this:

image.png.ea857b2971683e545bb167b755693105.png

Good.

Now it needs to be established if Eset ver. 13.2.15 is the source. With intermittent WMI crashes spread across multiple days, this will be difficult to prove.

Edited by itman
Link to comment
Share on other sites

  • ESET Insiders

For me, the WMI does not crash during a scan

 

Edit: The WMI crashes are a Windows problem, I've already read about them in some forums and since the users there are only running Defender, I don't think it is Eset's fault.

Edited by SlashRose
Link to comment
Share on other sites

10 minutes ago, r1man said:

Also WMI crashes aren't "a big deal" if they are intermittent in nature. As noted in the Microsoft article referenced in my posting:

Quote

After the issue occurs, you can just ignore the report about the crash in the WMI host program because the process will restart with the next request by itself.

 

Edited by itman
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...