From the ResourceMonitor activity, it can be seen that this issue is originating from the Diagnostic Tracker service built into Windows. As an optional service, it does not affect any of your running or existing programs or Windows itself. The service is used to monitor and track Windows functional activities as part of the user experience program, where Microsoft aims to improve Windows by collecting diagnostic information. Therefore, disabling the diagnostic tracker temporarily until Microsoft pushes another update is the best workaround so far. Alternatively, it can be left disabled regardless of updates.
Method 1: Disable the DiagTrack Service from Command Prompt
Method 2: Disable the DiagTrack Service from the Services Console
Method 3: Use WPR -cancel
Previously, a similar issue struck, affecting a large number of users. We published a post detailing and listing the most useful methods to address this issue. Before trying any of the steps listed in this post, I would suggest trying the steps listed under system and compressed memory. If the issue has not yet been resolved, then try the steps listed below:
