Home

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

%3CLINGO-SUB%20id%3D%22lingo-sub-881167%22%20slang%3D%22en-US%22%3Eimprove%20telemetry%20feature%20in%20windows%2010%20to%20be%20able%20to%20detect%20problems%20better%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-881167%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20the%20Telemetry%2C%20Error%20reporting%20and%20diagnostics%20services%20inside%20Windows%2010%20(Insider%20or%20not)%20are%20not%20good%20enough%20to%20catch%20the%20problems%20and%20bugs.%20specially%20those%20bugs%20that%20don't%20cause%20system%20crashes%20or%20bugs%20that%20cause%20some%20thing%20in%20Windows%20not%20to%20work.%3CBR%20%2F%3Efor%20these%20type%20of%20bugs%20and%20problems%2C%20Microsoft%20relies%20on%20people%20to%20report%20them%20but%20most%20of%20the%20time%20either%20people%20don't%20report%20them%20or%20they%20fail%20to%20specify%20how%20to%20produce%20that%20problem%2Fbug.%3C%2FP%3E%3CP%3EWindows%2010%20needs%20such%20a%20robust%20Telemetry%20and%20diagnostics%20services%20that%20would%20do%20its%20job%20regardless%20of%20people%20reporting%20a%20problem%20or%20not.%3CBR%20%2F%3Ethis%20Telemetry%20and%20diagnostics%20services%20must%20be%20even%20more%20thorough%20in%20Insider%20builds%2C%20they'd%20have%20to%20be%20so%20deep%20into%20Insider%20builds%20so%20that%20they%20produce%20very%20clear%20and%20thorough%20reports%20for%20Microsoft%20to%20identify%20the%20problems%20and%20things%20that%20don't%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpvote%20this%20Feedback%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FAA65fmf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FAA65fmf%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-881167%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ediagnostics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFeedback%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EInsider%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETelemetry%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-881227%22%20slang%3D%22en-US%22%3ERe%3A%20improve%20telemetry%20feature%20in%20windows%2010%20to%20be%20able%20to%20detect%20problems%20better%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-881227%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3Babsolutely%20agree%2C%20especially%20in%20a%20wake%20with%20the%20latest%20bugs%20in%20fixes%20which%20are%20intended%20to%20fix%20problems%20in%20previous%20fixes%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Ffacepalm_40x40.gif%22%20alt%3D%22%3Afacepalm%3A%22%20title%3D%22%3Afacepalm%3A%22%20%2F%3E.%20If%20u%20are%20decided%20to%20be%20an%20insider%20then%20u%20are%20HAVE%20to%20be%20agree%20with%20THOROUGH%20telemetry%20options.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-889695%22%20slang%3D%22en-US%22%3ERe%3A%20improve%20telemetry%20feature%20in%20windows%2010%20to%20be%20able%20to%20detect%20problems%20better%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889695%22%20slang%3D%22en-US%22%3EYes%2C%20Insiders%20don't%20have%20problem%20with%20better%20telemetry.%20in%20fact%2C%20they%20would%20welcome%20it%20because%20that%20means%20their%20work%20is%20not%20in%20vain.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-895174%22%20slang%3D%22en-US%22%3ERe%3A%20improve%20telemetry%20feature%20in%20windows%2010%20to%20be%20able%20to%20detect%20problems%20better%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-895174%22%20slang%3D%22en-US%22%3EThe%20issue%20is%20that%20the%20data%20you'd%20need%20to%20identify%20the%20source%20of%20a%20crash%20is%20often%20multiple%20gigabytes%20big.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20opened%20a%20case%20with%20Microsoft%20in%202016%20due%20to%20a%20bug%20in%20Edge%20when%20roaming%20profiles%20is%20configured%20for%20AD%20user.%20Edge%20would%20simply%20crash%20after%20the%20second%20time%20you%20log%20on%20to%20windows%20(basically%2C%20when%20you%20sync%20the%20profile%20from%20the%20server%20the%20first%20time).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20sent%20about%2020%20x%202%20gigabytes%20of%20raw%20memory%20dumps%20to%20Microsoft%20until%20this%20was%20fixed.%20And%20this%20was%20only%20Edge%20crashing.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20guy%20talks%20more%20about%20the%20issue%20at%20hand.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DS9kn8_oztsA%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DS9kn8_oztsA%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-895178%22%20slang%3D%22en-US%22%3ERe%3A%20improve%20telemetry%20feature%20in%20windows%2010%20to%20be%20able%20to%20detect%20problems%20better%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-895178%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20same%20person%20explains%20how%20Telemetry%20fails%20to%20catch%20bugs%20in%20Windows%20insider.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.ghacks.net%2F2019%2F09%2F23%2Fformer-microsoft-employee-explains-why-bugs-in-windows-updates-increased%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.ghacks.net%2F2019%2F09%2F23%2Fformer-microsoft-employee-explains-why-bugs-in-windows-updates-increased%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3Eraw%20memory%20dumps%20are%20Not%20always%20necessary.%20Microsoft%20runs%20telemetry%20and%20diagnostic%20reporting%20on%20All%20Windows%2010%20versions%2C%20insider%20or%20not%2C%20and%20they%20get%20their%20telemetry%20information%20in%20small%20chunks%20of%20data%20that%20can%20vary%20between%20few%20KBs%20to%20few%20MBs.%20so%20raw%20or%20full%20crash%20dump%20is%20not%20necessary%20for%20them%20to%20identify%20the%20problems%20and%20bugs.%20that%20wouldn't%20be%20smart%20anyway%20to%20waste%20all%20those%20Internet%20bandwidth%20and%20overload%20their%20own%20servers.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3Ethey%20need%20a%20smarter%20Telemetry%20system%20where%20even%20less%20data%20is%20required%20to%20identify%20the%20problem%20and%20that%20Telemetry%20system%20should%20be%20more%20integrated%20and%20thorough%20in%20Insider%20versions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
HotCakeX
Respected Contributor

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 crashes or bugs that cause some thing in Windows not to work.
for these type of bugs and problems, Microsoft relies on people to report them but most of the time either people don't report them or they fail to specify how to produce that problem/bug.

Windows 10 needs such a robust Telemetry and diagnostics services that would do its job regardless of people reporting a problem or not.
this Telemetry and diagnostics services must be even more thorough in Insider builds, they'd have to be so deep into Insider builds so that they produce very clear and thorough reports for Microsoft to identify the problems and things that don't work.

 

Upvote this Feedback:

https://aka.ms/AA65fmf

4 Replies

@HotCakeX absolutely agree, especially in a wake with the latest bugs in fixes which are intended to fix problems in previous fixes :facepalm:. If u are decided to be an insider then u are HAVE to be agree with THOROUGH telemetry options.

Yes, Insiders don't have problem with better telemetry. in fact, they would welcome it because that means their work is not in vain.
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

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-inc...

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.

 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies