WmiPrvSE.exe using high memory when I use Chrome, is this normal?

I don't know if I am being paranoid or what. But ever since installing Windows 10 I have observed this behaviour. WmiPrvSE.exe is taking in excess of over 20MB RAM in task manager. I am also seeing double of these instances running in task manager.

May I know whether this is normal? I don't experience this when I try using Microsoft Edge. But on Google Chrome the RAM is going in excess of 20MB.

I think I noticed this in Home version as well as the Pro version. But in Home I felt that this actually disappeared after some time. But in Pro version this WmiPrvSE.exe does not disappear!

I have chrome and i dont see not even one instance of that running during use of chrome , if you are sure it only fires with chrome then try to disable all extensions , end task of all those instances and load chrome .

Then you can do a 1 by 1 load to extensions to know which one utilize it .

Finally the possibility why you see it over different PCs might lay in Chromes Sync ability that can even Sync extensions installed across devices .

Just made the experiment on my mums Windows 7 Home Premium PC. Actually it is the latest Google Chrome update to blame on this occasion not Windows 10... It is a big coincidence indeed to see this happen just as I upgraded to Win 10. Never ever seen this happen before!

I was getting paranoid for a moment. Actually at first when I was using Google Chrome on her PC the WmiPrvSE.exe was only using like 2 MB and it was only a single instance of it. I then updated her Google Chrome to the latest version as an experiment and immediately I noticed the exact same behaviour even after restarting the computer!!

Two instances of WmiPrvSE.exe as well as WmiApSrv.exe (WMI Performance Adapter) running in task manager. And it is consuming over 20+ MB RAM.

Try updating your Google Chrome to the latest Version 74.0.3729.108 (Official Build) (64-bit)
You'll probably see the same issue being triggered on your system too. LOL, I was about to reformat Windows 10 thinking it is a Win 10 fault but now at least I know it is latest Google Chrome to blame..

Ok,I forcefully upgraded to 74.0.3729.131 , so yea there appears 3 instances of WMiPrvSE.exe one is 22 MB the other two is less than 2 MBs , after few minutes of operation the smaller instances self terminate and the bigger one remains .

According to this link http://batcmd.com/windows/10/services/wmiapsrv/ the service aims at providing statistical data about your pc performance to whomever calls it to the network .

So apparently google is yet collecting more data about global hardware that use them , most probably to tailor advertisement so yea these people are known for their crave to collect data .

If you hate that you can try to close it from task manager or just rename the file so whatever triggers it can't find it, windows can live without it yes .

I experimented by uninstalling the the latest Google Chrome browser and decided to test to see if the Google Chrome Beta version produces the same behaviour.

Google Chrome is up to date Version 75.0.3770.18 (Official Build) beta (64-bit)
Unfortunately the latest beta version produces the same results. WmiPrvSE.exe happens to reappear in the same way even after latest Windows 10 Update.

However, upon PC restarting/ startup this behaviour does not occur. Sometimes WmiPrvSE.exe does appear on Windows startup but after several seconds it will disappear.

The moment you launch Google Chrome official or Beta version immediately WmiPrvSE.exe will start with 20+ MB RAM. A single one of this instance will disappear and the memory will drop to about 16 MB RAM and then 8 MB RAM.

After some while of use Wmi will disappear from task manager while using the browser. But the moment you relaunch it again or any of the created short-cut icons it will launch again.

Also even after you close the web browser, you have to wait a few minutes before WmiPrvSE.exe disappears.

I haven't experimented with other web browsers other than Edge yet. On Edge it doesn't happen or even if it does it doesn't consume more than 2 MB RAM. I'm going to have to see if this behaviour is exclusive to Google Chrome or whether it happens with a few other web browsers.