WMI Provider Host | Razer Insider
Skip to main content
I keep getting 100% CPU utilization with bulk coming from WMI Provider Host (60-70%). After seeing a lot posts indicating the problem was Synapse, I killed the Raser process and reinstalled, problem solved, for a few hours. The only thing that works: disabled Razer Synapse 3 from startup and do NOT load the software.



RazerSynapseInstaller_V1.11.0.379



So after multiple re-installs, I've disabled Razer Synapse 3 from startup so I can at least use my system. Sadly, that means Razer macro, chroma and everything else don't work.



My System:

Motherboard MSI MPG Z390 EDGE AC

Processor Intel Core i5 9600k 6 Core 4.6GHz

Memory (4x8GB) DDR4 3200MHz G.SKILL Trident Z-32GB

Graphics Card NVIDIA RTX 2070 8GB GDDR6 -

HDD/SSD Xidax Performance SSD 500GB -

2nd HDD Western Digital Black 2TB - 7200RPM 3.5" HDD -

OS Windows 10 Professional 64-Bit -





Example of multiple reports on the issue:

This post is from 4 years ago with last response 7 months ago agreeing it is Razer Synapse.

https://www.reddit.com/r/pcgamingtechsupport/comments/c9xs3b/solution_wmi_provider_host_taking_up_all_my_cpu/

Please somebody help me. I just can’t make this s*** program works. I tried everything. The last try was installing a older version (RazerSynapseInstaller_V1.0.126.160.exe) but still do not work, but at least i can see the tray icon. But the main window of the Synapse was all black, and the program just updated by itself, make everything broken again.

 

The program simply do not open no matter what.


same here


Same problem here after the last update.

I noticed my fan’s where speeding up with the machine in idle state, when I check the task manager the WMI was at top cpu processes, and when that appens, it’s because some software it’s bugging.

Since the last software update was the Synapse, I closit and WMI desappeared.

Since Ive check it’s everyone with the same problem, I hope that Razer will fix this ASAP.


thought I was losing my mind lol, nice to see it isn’t just me.


Same issue since update 20230210.
RazerCentralService takes 6% of CPU now consistently and raises my CPU temp a good 15/20%
It did not do this before the update, 100% sure and nothing else has changed on my rig.
Please fix Razer, right now the only solution is to kill everything and when I do it freezes my explorer when I refresh “My PC” (I have no idea why!).
Restarting WMI service, etc. doesn’t do anything for me.


Maybe we need to raise a support ticket on this issue. This forum may not be monitored by Razer support team.



https://mysupport.razer.com/
Same problem since yesterday. Razer, say something.
Can Razer support please confirm this thread is monitored?
Massive issue for me as causes unacceptable battery drain on my laptop while I'm mobile.



(Unfortunately not the first time a Windows update and/or Synapse update has caused runaway Synapse CPU use!)



Temp fix is obviously to uninstall Synapse - kills lighting, sound etc. though!



If like me you need the lighting to see your keyboard caps there is a work around however:

Search for OpenRGB on gitlab (Author is Adam House) - will let you control your backlight to enough of a degree as to be useable. (May work for other peripherals, but I haven't tested).
Same issue, please fix this asap. Where can I get an earlier version from in the meantime?
Same issue.
my contribution post.
For your additional info, my WMI repository is consistent with no errors, as well as sfc scan result.



C:\\>winmgmt /verifyrepository

WMI repository is consistent



C:\\>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
There are multiple error lines like below in the logs. Please pass this to your engineering team for further investigation.



It seems Synapse is continuously polling to get certain process info and failed.



[indent]Synapse 3\\Razer GameManager (GMS2) Logs\\GameManagerService.log:120:2023-02-10 00:22:38,251 [4] DEBUG GameManager [(null)] - ProcessExtractor: Error getting path for PID (19292) using WMI: Cannot process request because the process (19292) has exited.



Synapse 3\\Razer GameManager (GMS2) Logs\\GameManagerService.log:139:2023-02-10 00:22:41,125 [4] DEBUG GameManager [(null)] - ProcessExtractor: Error getting path for PID (9152) using WMI: Cannot process request because the process (9152) has exited.



Synapse 3\\Razer GameManager (GMS2) Logs\\GameManagerService.log:5470:2023-02-10 11:43:12,948 [14] DEBUG GameManager [(null)] - Ignoring processes with the process name: WmiPrvSE.exe



Synapse 3\\Razer GameManager (GMS2) Logs\\GameManagerService.log:5970:2023-02-10 22:35:02,817 [12] DEBUG GameManager [(null)] - Ignoring processes with the process name: WmiPrvSE.exe



Synapse 3\\Razer GameManager (GMS2) Logs\\GameManagerService.log:6964:2023-02-11 11:03:20,182 [12] DEBUG GameManager [(null)] - Ignoring processes with the process name: WmiPrvSE.exe



[/indent]
Razer.Zionzedd
Can you gather the Synapse logs by following the steps here and share them with me through PM using Google Drive? I will forward it to the software team so they can investigate the cause of the issue and replicate it if necessary.




Can you kindly confirm where Razer software team is looking at the issue?
HGMRB
I too have noticed that after installing the latest version, there is a constant use of the CPU by WMI, even if in my case luckily it's only limited to 8/9% but already enough to make my laptop fan audible. However, when synapse is turned off, the usage drops to 0%.


Yes same issue.
I tried to use an older version of the installer, but it will always download the latest version, which makes rolling back impossible after the update.



Is there any way to roll back?
I too have noticed that after installing the latest version, there is a constant use of the CPU by WMI, even if in my case luckily it's only limited to 8/9% but already enough to make my laptop fan audible. However, when synapse is turned off, the usage drops to 0%.
the_St.
Latest version of Synapse 3 is seriously broken.

Not sure of exact versions, but the updater states I'm currently usining version 20230113 which works great, but the latest version is 20230210 which is serioulsy broken!!!

WMI CPU usage goes through the roof and Blade 17 fans go crazy with version 20230210.

20230210 automatically updated on me - I had to revert to last weeks image restore of my Blade 17 and turn off auto-updating in Syanpse 3.

Repeated several times and same thing - DO NOT AUTO-UPDATE to 20230210 version of Synapse 3.


Thank you, to be honest I didn't face any issues before so I didn't have any information regarding to avoid current updates on Synapse, by the way, do you may have the stable version of Synapse in order to reinstall using that installer ?

Thank you
Latest version of Synapse 3 is seriously broken.

Not sure of exact versions, but the updater states I'm currently usining version 20230113 which works great, but the latest version is 20230210 which is serioulsy broken!!!

WMI CPU usage goes through the roof and Blade 17 fans go crazy with version 20230210.

20230210 automatically updated on me - I had to revert to last weeks image restore of my Blade 17 and turn off auto-updating in Syanpse 3.

Repeated several times and same thing - DO NOT AUTO-UPDATE to 20230210 version of Synapse 3.
Any updates on this ?, because I'm running the latest Synapse version (3.8.209.20311), and the issue is still there
Same problem here! After last recent update.
if you suspect something, investigate the persistent wmi:

*with the command prompt

wmic /namespace:\\\\root\\subscription PATH __EventFilter get/format:list

wmic /namespace:\\\\root\\subscription PATH __EventConsumer get/format:list

wmic /namespace:\\\\root\\subscription PATH __FilterToConsumerBinding get/format:list
Can you gather the Synapse logs by following the steps here and share them with me through PM using Google Drive? I will forward it to the software team so they can investigate the cause of the issue and replicate it if necessary.

Reply