100% Disk: WPR_Initiated_DiagTrackAotLogger_WPR System Collector.etl

xraiderv1 said:

jack hit on a workaround! well done jack!

Looks like everyone is in the same boat so it's probably a bad Windows update since I know some virgin customers haven't been able to connect to the internet when they downloaded the latest update (I'm not of those by the way). I've done this workaround and it solves the problem for now anyway and the disk isn't jack-rabbiting

xraiderv1 said:

...jack rabbiting..that is certainly one way of putting it.

how many here have used the feedback hub to report this?

I had been planning to do but whether they'll take in the workaround or even listen to the complaint I'm not sure

Jacob Klein said:

Same issue here, too. Very curious! For me, it happened right after upgrading to 14393.479, and only on 1 of my PCs I think.

Note: I found a quick workaround to stop it until next reboot:
Start Command Prompt (Admin), then type: WPR -cancel
... but for me, after rebooting, the WPR logging started right up again.

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!

tufa4311 said:

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.

Thanks. :)
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!

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!