Windows 11 Diagnostic Policy Service CPU usage

AmiBroker
1

Does anyone have problems with the Windows 11 Diagnostic Policy Service hogging up the CPU usage when running AmiBroker optimizations? I have a fairly new PC, running the latest Windows 11, 64 Gb of RAM, Inter i9-13900KF 3.0 GHz processor. The Diagnostic Policy Service is a perennial hogger of CPU resources, slowing down AmiBroker, and most of the things I have tried to alleviate this (stopping the service etc) don't seem to work (it restarts almost straight away, even when it's set to manual start).

Any insights would be helpful.

2

This is not AmiBroker question. The service is provided by Microsoft and as reported by many pages across the web it tends to consume upto 30% of CPU

https://www.google.com/search?q=Windows+11+Diagnostic+Policy+Service+CPU

3

Yes, not specifically an AmiBroker question, but it affected my ability to run AmiBroker.

In any case, I thank you for the pointer. I had run previous queries myself, without finding a solution that worked. One of the links in your post (windows 10 - How do you fix the Microsoft Service "Diagnostic Policy Service" taking up about 4GB memory and about 1 cpu core at 100%? - Super User), though, was able to steer me through to the solution.

I managed to find the SRUDB.dat file in "C:\Windows\System32\sru", which turned out to be 22 Gb in size. When I deleted this file, after stopping Diagnostic Policy Service, my PC started running normally again. I could restart Diagnostic Policy Service, and it did not hog the CPU usage.

1 Like