Came to my computer and saw this dialog box:
"WerFault.exe?" Couldn't this have a more meaningful name?
Try to dismiss it and it keeps coming back. Clicked OK a dozen times and still sitting there as the "foreground" window even as I am typing this.
Search for it and get this:
Yup. The thing that has crashed is the program that wants to report a Windows error (crash). Except that it is crashing itself! So gets stuck in an infinite loop, crashing while it is trying report its own crash.
Why, oh why errors that are reported to users are still in computer jargon.
Microsoft is not the only one of course. Error messages do not get "usability tested" as they are assumed to never happen. But happen of course.
With probably millions of them in the OS, it is an impossible battle to clean them all up but at some point, you have to take your trash out.
Anyway, I have to reboot my machine so that I can type without looking at the error message window above!
Grumpy in Seattle,
Amir
"WerFault.exe?" Couldn't this have a more meaningful name?
Try to dismiss it and it keeps coming back. Clicked OK a dozen times and still sitting there as the "foreground" window even as I am typing this.
Search for it and get this:
Yup. The thing that has crashed is the program that wants to report a Windows error (crash). Except that it is crashing itself! So gets stuck in an infinite loop, crashing while it is trying report its own crash.
Why, oh why errors that are reported to users are still in computer jargon.
Microsoft is not the only one of course. Error messages do not get "usability tested" as they are assumed to never happen. But happen of course.
With probably millions of them in the OS, it is an impossible battle to clean them all up but at some point, you have to take your trash out.
Anyway, I have to reboot my machine so that I can type without looking at the error message window above!
Grumpy in Seattle,
Amir
Last edited: