Automatically Restart Crashed Or Hanged Applications

Don’t you hate it when programs hang or crash? I find it especially annoying when a background application like an IM client or a bandwidth monitor silently crashes – sometimes I only notice the problem hours later when I’ve already missed a bunch of messages. I’m sure you’ve encountered a few “Not responding” errors and some irritatingly crash-prone applications yourself.

If you have an unstable program that you absolutely need to run at all times, but don’t want to waste your time monitoring and manually restarting it every time it croaks, I might have something interesting for you.

Restart on Crash is an monitoring tool that will watch the applications that you specify and automatically relaunch any program that hangs or crashes. You can add any number of applications to monitor, enable/disable them individually and edit the command line that will be used to restart an application.

Restart on Crash doesn’t require installation and stores all it’s configuration data in a “settings.ini” file in the program’s folder, so it’s portable. It should be compatible with most NT-based Windows versions.

Download Restart on Crash (1.4 MB)

Screenshots & Documentation

Main application window

The main window

  • To add a new application to monitor, click the “Add” button or press the Ins key.
  • To delete on or more applications from the list, select them and click “Delete” or press Del.
  • To edit the per-application configuration, double-click the correspoding row. This will open the editing dialog (see below).
  • You can also access the RoC configuration by clicking “Settings” and view the activity log by clicking “Show Log”. The log contains information about crashed/hanged applications, executed commands, and so on.
Editing the monitor settings for an application

Editing the monitor settings for an application

Well, this one should be pretty self-explanatory 🙂 One detail to keep in mind is that enabling the “It isn’t running” option will make Restart On Crash treat the application as if it has crashed even if you have purposefully it closed it. You can get around this by disabling the monitoring of the application before you close it.

The configuration dialog. Yes, that's it.

The configuration dialog. Yes, that’s it.

“Grace period” is how long Restart on Crash will wait before trying to terminate/restart an application that it has just terminated/restarted. This is intended to prevent a scenario where RoC kills a hanged program, restarts it, decides it has hanged again (e.g. if the program is non-responsive while starting up) and wrongfully terminates it again.

Known Issues

  • If you configure RoC to automatically kill a hanged application, it will terminate all instances of that application when doing so. This may be fixed eventually.
Related posts :

423 Responses to “Automatically Restart Crashed Or Hanged Applications”

  1. Jānis Elsts says:

    @ Echo: Maybe it would be possible to detect the crash by looking for the error message? Is it displayed in a separate pop-up/dialog/message box, and is it part of the same process or is it displayed by a different application?

    @ Daniel: Sorry, could you rephrase that? Do you meant that you want to automatically minimize an application?

  2. Ron says:

    Anyway to save the settings in ROC? I need to be able to restart the PC or an application suite and retain the ROC configurations. Am using it to keep a communications application alive which tends to drop at odd times. Part of a suite of programs.
    Since it does not itself save the settings if I reboot the pc or otherwise close ROC down I have to re-enter the setup info again.
    Need to automate as much as possible and having everything come to a stop waiting for someone to manually re-enter settings is counter productive.
    Also is there a way to open this without having to reopen the zip file?

  3. Jānis Elsts says:

    RoC automatically saves settings in a “settings.ini” file in its directory. If that doesn’t happen then that probably means the directory where it’s installed is not writable. Try moving it to a writable directory.

    If the RoC directory must remain read-only, you could temporarily make it writable to allow RoC create the settings.ini file and then make it read-only again.

    Also is there a way to open this without having to reopen the zip file?

    You can just copy the .exe from the ZIP file and paste it in a more convenient location. You don’t have to run it from the archive.

Leave a Reply