Forum Discussion

MVP

Sep 29, 2019

improve telemetry feature in windows 10 to be able to detect problems better

Currently the Telemetry, Error reporting and diagnostics services inside Windows 10 (Insider or not) are not good enough to catch the problems and bugs. specially those bugs that don't cause system c...

Iron Contributor

Oct 05, 2019

The issue is that the data you'd need to identify the source of a crash is often multiple gigabytes big.

I opened a case with Microsoft in 2016 due to a bug in Edge when roaming profiles is configured for AD user. Edge would simply crash after the second time you log on to windows (basically, when you sync the profile from the server the first time).

I sent about 20 x 2 gigabytes of raw memory dumps to Microsoft until this was fixed. And this was only Edge crashing.

This guy talks more about the issue at hand.
https://www.youtube.com/watch?v=S9kn8_oztsA

HotCakeX
MVP
Oct 05, 2019
The same person explains how Telemetry fails to catch bugs in Windows insider.

https://www.ghacks.net/2019/09/23/former-microsoft-employee-explains-why-bugs-in-windows-updates-increased/

raw memory dumps are Not always necessary. Microsoft runs telemetry and diagnostic reporting on All Windows 10 versions, insider or not, and they get their telemetry information in small chunks of data that can vary between few KBs to few MBs. so raw or full crash dump is not necessary for them to identify the problems and bugs. that wouldn't be smart anyway to waste all those Internet bandwidth and overload their own servers.

they need a smarter Telemetry system where even less data is required to identify the problem and that Telemetry system should be more integrated and thorough in Insider versions.