Windows 10: 100% Disk: WPR_Initiated_DiagTrackAotLogger_WPR System Collector.etl

I made an account just so I could thank you. I have been dealing with this issue for hours. I work from home and even my small work program wouldn't open. I had tried everything. This is the only thing that helped me. Thank you so much!

 

You're welcome. Please be sure to open the Feedback app, and either UpVote relevant feedback or create your own. We need to make sure Microsoft gets feedback through that app.

 

Would everyone agree I can mark this as solved? We have a work-around that works...

 

NO.

A workaround is NOT a solution. We don't know the cause, and we don't have a solution. Please do not mark as solved.

 

ok Jacob, calm down and please don't raise your voice at me (or anyone else for that matter)...I asked a question because I didn't know the answer, where I come from that is how we do things. The post will remain as is.

 

Just registered to chime in; this worked for me as well. It may only be a temporary fix, but the fix is appreciated nonetheless. I'll be forwarding this info on to Microsoft. Thank you!

 

Thanks. *Smile
Where I come from, we don't sweep things under rugs. We FIX them. And I didn't yell at you, BUT YOU'D KNOW IT IF I DID! *Tongue

I'm actually a Windows 10 Insider, and have never seen this issue on any of my fast-ring insider partitions. The issue just happened on one of my PCs, on its Release partition. So bizarre, hope Microsoft figures it out! Happy holidays!

 

Jacob, I am new to this forum and I did not know the rules for marking things as solved, again, so I asked - no one is trying to sweep anything anywhere. You may want to simply admit that you got a bit out of hand and leave it at that, I know it's tough, but I know you can do it.
What's done is done and we can leave it at that. Happy Holidays to you as well.

 

I'm new here too! And I don't consider my response as "out of hand". It's just quite a bit unnerving to me, to call a workaround as a solution. I've seen it all too often, and it's part of the reason why software has so many bugs these days. We can drop this discussion about it, though.

So, DiagTrack service causes the WPR to be initiated? That's interesting... I wonder if it will complete after a while - ie: If we let WPR thrash the disk for several hours/days, will it eventually complete? Another good test would be to uninstall the most recent update, and see if the problem goes away.

 

Same issue here, that's super weird. I thought it was just doing something else and let it sit for a while. Killed the service and solved for now.

 

I love you jack, I was beginning to lose hope, after 2 hours of searching and trying multiple fixes, I found this thread by sheer luck. I LOVE YOU *Biggrin

 

So I'm not the only one who's experiencing this issue. I'm glad that I've found this thread, this 100% disk usage is very annoying, hope MS gets the message and fixes this ASAP. For now I'm just gonna leave everything as it is just to see if it resolves the issue, buy anyways thank you Jacob for posting workaround.

 

I had the same problem and looked into it. I wanted to let people here know... I found more info about DiagTrack here: Microsoft renames Diagnostic Tracking Service to Connected User Experiences and Telemetry - gHacks Tech News
Apparently it's some Microsoft service that goes under the name "Connected User Experiences and Telemetry service". The linked post shows how to disable it. If you don't it may start up again on a reboot and you get the 100% disk usage issue again.

 

Hi!

If you go into "Privacy" -> "Feedback & Diagnostics", if you change it to Enhanced or Basic, it should remove the problem. The really cool thing is if you let it set for a while (not sure how long), it will eventually remove the two WPR *.ETL files by itself. I restarted in Enhanced mode, then switched back to Full and now my machine is back to normal! "

Work!

 

if you are looking for DiagTrack in services.msc it has been renamed to Connected User Experiences and Telemetry service.

I have disabled this and stopped the service, disk usage is down to acceptable levels but I am still seeing intermittent spikes of 100%