When Windows tries to “check for a solution” after a program crashes, what is it actually doing and why does it never seem to work?
We’ve all seen the dialog, but what actually happens? Mark Phaedrus, developer at Microsoft, gives the answer.
When Windows tries to “check for a solution” after a program crashes, what is it actually doing and why does it never seem to work?
We’ve all seen the dialog, but what actually happens? Mark Phaedrus, developer at Microsoft, gives the answer.
There’s actually been a couple of times where it actually provided helpful information – once it recommended compatibility settings, another time it gave me a link to a patch for the program I was using.
The link leads to 404. Did he say anything that could ban him?
Need to remove the “answer/Mark-Phaedrus” portion of the url:
https://www.quora.com/When-Windows-tries-to-check-for-a-solution-after-a-program-crashes-what-is-it-actually-doing-and-why-does-it-never-seem-to-work/
Basically it creates a signature of the error, and checks in with Microsoft. If there is a solution with that signature in Microsoft’s database then it responds to the user with that solution. If the error is new then Microsoft takes a note of it. If many people have the same problem, a bug is generated and assigned to a developer.
Sounds like a good plan. Hope it improves with time.