HOWTO: How To Change Hard Error Popup Handling in Windows NT

In an unattended environment, you may want to automatically dispatch hard error popups that require user intervention. This article gives you the code you need to change the hard error popup mode.

Windows NT allows the user to change the handling of hard error popups that result from application and system errors. Such errors include no disk in the drive and general protection (GP) faults.

Normally, these events cause a hard error popup to be displayed, which requires user intervention to dispatch. This behavior can be modified so that such errors are logged to the Windows NT event log. When the error is logged to the event log, no user intervention is necessary, and the system provides a default handler for the hard error. The user can examine the event log to determine the cause of the hard error.

Registry Entry

The following registry entry controls the hard error popup handling in Windows NT:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode

Valid Modes

The following are valid values for ErrorMode:
Mode 0

This is the default operating mode that serializes the errors and waits for a response.
Mode 1

If the error does not come from the system, this is the normal operating mode. If the error comes from the system, this logs the error to the event log and returns OK to the hard error. No intervention is required and the popup is not seen.
Mode 2

This always logs the error to the event log and returns OK to the hard error. Popups are not seen.
In all modes, system-originated hard errors are logged to the system log. To run an unattended server, use mode 2.

Read more: MS Support

Posted via email from .NET Info