Windows 8 seems to have chosen to silently shutdown applications that misbehave, there is no message informing the user something bad happened and no information on why the application closed.

I heard through the grapevine that employees at Microsoft are tired of customers blaming them for crashes and that they believe when they display an error to the user the user will accuse Microsoft of the crash instead of the app developer. Regardless of whether that is true or not is it really not a good idea to display error messages? I thought that error messages at least give users something to use when they are searching the web for help or talking to customer service. What possible good reason is there for crashing silently and not showing an error message?

  • I guess that your rumor is correct, and this is a marketing ploy. However, we cannot know for sure unless someone blows the whistle. Aug 3, 2013 at 4:44
  • When Windows silently dismisses a crashed app, it's not clear if there was a crash or if the app has somehow been minimized or hidden. The user is now confused and thinks, "What just happened?".
    – Jo Jo
    Nov 12, 2013 at 7:52

3 Answers 3


At work, we use a certain email program that is known to crash from time to time. When it does this, the app displays a "please wait" message box while it submits a crash report, whose only real purpose is to keep me from re-launching the app while an error log is submitted.

Importantly, WINDOWS does not ever display an error message. That's the job of the application, and the operating system has no business leaving the app's window drawn with a "this app is busted" dialog showing.

In general, a user should ONLY be shown an error message when there is something they can do. An application should display an error dialog if there is a reasonable expectation that the user is waiting for the app; if your app is silently running in the background, displaying an error message is likely not relevant.

And Windows 8 silently killing apps is no different than android or iOS doing the same. Especially if it's a "metro" app, which is meant to be largely managed by the OS anyway.

  • I agree with @DougM on this: only show the user a message (or dialog) when they can do something about it. This is an ancient post by now (2000?) but still so very true: joelonsoftware.com/uibook/chapters/fog0000000059.html
    – tamouse
    Aug 3, 2013 at 14:52
  • 1
    Android doesn't silently kill apps, it tells the user either that the app is not responding or has stopped unexpectedly.
    – satur9nine
    Aug 4, 2013 at 0:09

Speaking from my code, and not microsoft's I would say that there are times I might hide errors from users. Usually, these are times when one of several things is true:

  1. There is nothing the user can do with the knowledge

    Imagine that your program hits some limit that it cannot recover from. Regardless of what the user does, you know the program has to be restarted. In this case, sometimes you might hide the cause from the user. BUT, and it is a big BUT, the program really should avoid this line or reasoning if at all possible. Take running out of memory for example. That might be unrecoverable, but if you never tell the user, they can't provide more memory.

  2. My code can reasonably recover and the user can't really help

    This isn't related to the scenario you describe, but there may be times when a program has an issue that it can handle, and not tell the user that it happened. But again, hiding errors like this could hide a deeper problem that the user could avoid in the future.

  3. I don't know the error or handle it

    In your example, Windows 8 may be shutting down "bad" programs. But what is bad (too much memory) and why they are bad are two different things. I could see deciding that it is better to just shut down than it is to provide an overly generic message or a bad one.

In all these cases, I would say that hiding an error from a regular user might be OK, but the error should be logged somewhere for a power user or administrator.


If it is not shown to the end-user, then it must be shown to an administrator (if the computer is managed by a company that owns it, e.g. in a workplace), or an error signature is being collected and uploaded to the Microsoft HQ and then classified into a Winqual bucket.

Apparently, by deciding not to show the error message to end-user, they also decided to secretly collect the error information without giving end-user a choice. This will massively increase the opportunity for collecting software errors on a massive scale.

If the crashing software happens to be Windows-certified, Microsoft can take actions by revoking it, or by implementing special workaround for this particular software, and push out the workaround (again, secretly) to everyone who happen to use it.

This is just my pure speculation.

  • s/collecting software errors/collecting users private information/g Aug 3, 2013 at 4:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.