Thanks. The PML can now be unshared (for privacy reasons).
The following app is causing the issue.
"C:\Program Files\Adda52_2.0\Adda52_2.0.exe"
Please terminate the app, uninstall it, or rename the executable.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hey! I have got a new build - Ryzen 7950x w 128GB RAM and a NVIDIA 4060 GPU. Motherboard: ROG STRIX X670-E-E GAMING. Main problem I have been facing is the WMI Activity levels for the CPU were getting up to 80-90% clogging the functionality of my PC.
My previous details about how it started and the intensity of the problem: https://answers.microsoft.com/en-us/windows/forum/all/wmi-provider-host-high-cpu-usage/da16f098-ec32-45ba-8527-3a080f37ab7b
Now, I have managed to execute some solutions mentioned in the above linked post and then some routes I have mentioned properly in this sheet I made for the same purpose; the major route I have chosen is to take note of PID's in Operational Logs of WMI Activity and tackle them one by one.
Details here: https://docs.google.com/spreadsheets/d/1QZ1BLoRiwY9USNcwSJb2dpQGacYCu\_XnusYGnH10jJA/edit?usp=sharing
I have marked the processes that have been "solved" and did not occur again as green and the ones still coming up as errors in the operational logs as red.
The processes giving me WMI Errors in a ranked manner in terms of frequency of errors:
The situation as of now is it's gotten better; the WMI Activity doesn't go more than 20% as of now but as far as I know, this process shouldn't take up any of the CPU which means some programs/processes are still interfering which I want to fully solve. Also, there have been periods of no issues and then suddenly it crops up again so I want to fully eliminate it.
Also let me know; my last resort being a reboot to downgrade to Windows 10 and how would that fare as the last possible solution if I can't figure out how to eliminate the interfering programs/processes?
Thank you, eagerly waiting for a response. :)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thanks. The PML can now be unshared (for privacy reasons).
The following app is causing the issue.
"C:\Program Files\Adda52_2.0\Adda52_2.0.exe"
Please terminate the app, uninstall it, or rename the executable.
I didn't quite get you.
Thank you very much for your reply.
I will answer your questions from top to bottom first, of course in my mind you have become an engineer after this question!
I think there are two possibilities.
(1) Malwarebytes has bundled the WMI service invisibly to cause the problem, and the WMI service cannot be shut down without shutting down the Malwarebytes service.
This also corresponds to the use of Malwarebytes to detect malware as mentioned in your follow-up reply.
From a technical point of view I would suggest that you try to remove it, but to “cleanly remove” Malwarebytes you may need to borrow some other methods. Generally speaking, the usual uninstallation methods may not be able to uninstall it completely, because some antivirus programs can modify the registry and leave files or registry residues.
(2) In addition to this, there is also “System error 5 has occurred”, generally speaking, this error is reported that the user does not have the right to make changes, which is not because it is not run with administrator privileges. This is not because it was not run with administrator privileges, but because of the following possibilities:
2.1 The blocking value has been tampered with by an application, e.g. Malwarebytes.
2.2 Some services are located in the system32 directory, and the current account is not the “Super Administrator account” (just a possibility).
So I have a few suggestions to face this problem:
(1) Turn off the WMI service and Malwarebytes service at the same time. Unfortunately, since I personally do not have Malwarebytes on several test machines, I can't tell you the exact name of the service, so you can find it manually and turn it off.
Click “Windows Logo Key” to open the search bar -> type “Services” and open it with administrator privileges -> find all Malwarebytes related services in the list, change “Startup Type” to “Manual” and “Service Status” to “Stopped”.
(2) “Cleanly uninstall” Malwarebytes, please make sure to “cleanly uninstall” it!
(3) If you still can't execute the command to close WMI after closing Malwarebytes related services or clean uninstallation, please enable the Super Administrator account and log in.
Click “Windows Logo Key” to open the search bar -> Enter “cmd” in the search bar and open it with administrator privileges -> Please enter the following commands
net user administrator /active:yes
WMI is used by many applications for system monitoring, management and control, so it is indeed possible that the NVIDIA Container process you mentioned is the cause of the high WMI CPU activity.
Updating the BIOS works for the most part, but could potentially cause the problem to get worse.
However, in the current case, the fact that you removed the NVIDIA program but the problem still exists suggests that NVIDIA calls are not the only ones causing the problem, but there may be other applications or services that are constantly calling.
Generally you can do this:
(1) After running only half of the services to turn on the system, use the computer normally for a period of time to see if the WMI service is highly active
(2) If not, run the other half of the service.
Although clean boot uses only the smallest drivers and startup programs of Windows, it actually does not affect too much normal use. It is just possible that some applications are restricted or some external devices are restricted to avoid causing problems.
So you can open your poker session normally after clean start. Then just repeat the OK again.
For monitoring you can set up a new set of data collectors and log WMI and other metrics by using the Performance Monitor.
Please note: In addition to backing up your data, downgrading from Windows 11 to Windows 10 may cause driver compatibility issues, which will require you to install the corresponding and compatible drivers.
I hope the information I've spent a lot of time testing will help you my friend without any problems :)
I look forward to hearing back from you.
Best Regards
Arthur Sheng | Microsoft Community Support Specialist
Hey Arthur! Before I get to the points you've mentioned, just want to share an update - mentioning all things that I think could be of relevance.
I played a small session today and had my Task manager open at all times - WMI Activity was there sporadically but mostly topping off at 15%. Is there any % considered normal btw for WMI? Or it should just not take any CPU at all in a "normal" scenario?
At 15% - there's literally no lags in the PC barring sometimes just say if I'm typing, the text would appear in a second or so randomly in between.
Linking the video of the Event Viewer logs: https://gyazo.com/162e7526fe6907375cc4ba8acd1fa786
Things to note:
.
1 - I would definitely do as you suggested for MalwareBytes but before that I still want you to know it's only been say 10-12 days since I installed the MB program. The WMI issue has been since the start. In fact, MalwareBytes was an attempt to remove malware which could be causing a problem.
I understand you're thinking of it as a threat/cause of the problem (my guesstimate was on the same lines) because it showed up as an "obstruction" when we tried stopping WMI through CMD. That is the thesis behind our decision to cleanly remove MB, right?
Also, just struck me when I was scrambling through YT finding a solution and I remember there was one solution which included CMD and typing these commands, probably these are WMI related processes:
I remember probably 3-4 of these didn't go through something similar to System Error 5 came up. This too was after installing MalwareBytes though - 2 days after.
Also, until and unless there are new solutions on the table to try based on the new info I gave; I should first - remove MB cleanly through your steps and THEN try recreating the problem and if it still persists we move to -> clean boot and then stress test in the same environment and last resort being the downgrading to Windows 10. Right?
Thank you for the additional information my friend.
WMI-Activity Event ID:5858 ResultCode:0x80041032
Since this involves a lot of highly technical jargon, I have personally summarized it to make it as understandable as possible for you.
Combining all our previous information, we can conclude that the cause of the problem is due to an application (WMI caller) calling and then retrieving the full result set and releasing it. But the client releases the termination link and then logs it once in the event viewer.
Such frequent logging indicates that there are unusual calls and their frequency is very high leading to similar problems. This also corresponds to what I illustrated in (1), that the more or more often an application calls and queries WMI, the higher the footprint.
I think we can start with this:
(1) Go to Event Viewer and log “ClientProcessid = \*\*\*\*\*” in Error.
(2) “Ctrl + Shift + Esc” to open Task Manager, enter this PID and search for it to find out which service or application is running (should include Express VPN, ASUS Com Service and NVIDIA Container as you mentioned).
(3) Try right-clicking to disable it and wait a while to see if it still calls. (But considering that there is a VPN that you may need for your poker game, it is recommended that you just try it for now to find out why.)
Actually, there is a solution to this problem, but I think it's a bit too technical and may not be particularly convenient.
The link is: WMI-Activity Event 5858 ResultCode 0x80041032 - Windows Client | Microsoft Learn.
Clean start and clean uninstall MB is not the same program, clean uninstall MB is to prevent the third-party antivirus software has been uninstalled on the surface, but the registry and file residues still exist.
So I have these suggestions:
I sincerely hope that the above solution will solve your problem.
I look forward to hearing back from you.
Best Regards
Arthur Sheng | Microsoft Community Support Specialist