God damn it! I've already bumped your limits to 5x the initial value! What the fuck you you want again!! Piss of you WMI-retard-host!

What limits

@nitwhiz of handles or whatnot.. IDK, did it half a year ago

Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = DESKTOP-PQ27RFF; User = NT AUTHORITY\SYSTEM; ClientProcessId = 9212; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT * FROM Win32_PerfRawData_PerfOS_Memory; ResultCode = 0x80041017; PossibleCause = Unknown

Well of course! How didn't I think of that.. It's all clear, written in black on white in system Events' journal!!

/s

15 years Windows user here, never had any problem, never set any limit.

@nitwhiz yeah, that helps, thanks :) /s

@netikras no problem, happy to help!

@netikras You need to find the actual culprit here - the process which uses WMI in a bad way. Raising limits on WMI will not help.

Check here: https://answers.microsoft.com/en-us...

Or here for even more details: https://support.microsoft.com/en-us...

@bjoer751 The process is a Baloon Service. It's pid and select are in the 2nd comment of mine in this thread.

Still it does not help me in any way. I can kill it ofc, but that means I'll loose the memory balooning feature

@netikras So the Windows instance is a VM? Which Hypervisor?

And it's the VMs resources you've increased?

@bjoer751 libvirt, qemu.

I haven't changed vm properties/settings grom hyprrvisor layer. Only made changes inside guest os

> "my vm's cpu is being eaten by the WMI host"
> windefend still enabled and eating 10% of the CPU

(if my phone's softkeyb would stop having button bounce issues that'd be great)

@Parzi windefend is the least of my problems here :D

@netikras yeah but that's 10% of the CPU WMI could be using.

@Parzi true that 😁😁😁