Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

event viewer spammed with errors while SDC is on #194

Open
lunarball opened this issue Jun 22, 2024 · 1 comment
Open

event viewer spammed with errors while SDC is on #194

lunarball opened this issue Jun 22, 2024 · 1 comment

Comments

@lunarball
Copy link

started since the last update 4 days ago, been over 50k of them on event viewer so far. this might or might not be the reason for my system lags, too.

asfdf

tested it several times and errors do go away if SDC is off.

@msasanmh
Copy link
Owner

WmiProviderSubSystemHostJob is WmiPrvSE.exe Windows API.
Using this API too frequently cause high CPU usage, that's why SDC uses this API only when it's necessary:

  • Listing Network Adapters
  • Getting the Network Adapter's status (Tab 3)

So if SDC is causing this warning you shouldn't be able to see your network adapters on tab 3.

What can cause this warning?

  1. You have a running process or an application that using this API but it doesn't have sufficient permissions or administrative rights. (You have permission issue)
  2. Security software interference:
    • Security software like antivirus or internet security tools might block or restrict access to certain system objects, causing this warning.
  3. WMI configuration issues:
    • Misconfigurations within the WMI service might lead to access problem.

What can solve this warning?

  1. Check permissions: Running the process as an administrator might resolve the issue.
  2. Examine security software: Temporarily disable any security software to check if it is causing the issue.
  3. Check WMI Service: Verify the health and configuration of the WMI service:
    • Check WMI service status: sc query winmgmt
    • Rebuild WMI Repository: winmgmt /resetrepository

Conclusion: 99% the issue is on your side and related to permissions, not SDC.
but let me know if you could gather more information on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants