I can tell you don't really program by that statement. So let me explain..... Within Pinballx's main thread there is a call create a Direct2D.Direct2d.Surface object, this takes a filename (derived from the visual pinball.xml) and some other params.... This trickles down to a call to System.Drawing.Bitmap which throws an exception because the file is not a vaild bitmap. (In my case, it was a corrupted transfer from my file server to my cabinet which left a zero length file.) Now a good way to handle this is to catch the execption and log "File XXXXXX.png is not a valid image file" and you *could* fallback to to the "No table image" or "no wheel image file" and continue as normal. Or spit up a MsgBox. Or log it and exit.... Give the user some semblance of what the problem is. The incorrect way to handle it is not catch the exception and crash out of the program give the user no indication on why the program crashed. You don't have to code in every image combination that could possible be used in order to validate them, you just need to catch a generic exception and handle it gracefully. Anyway, the bug was reported and the author said his piece that it won't be fixed..... Not much I can do about it.