AIUI, there is a "pause" button that can be used in such a circumstance, followed by the up/down arrows.

Being able to nuke+retry a download would be useful. Currently, if you get the corrupt file notice, you can either continue the download and get a probably-worthless file, or stop it. If you stop it, all you can do is kill it and then to make another attempt to get the file you have to search for it again, unless the search or host-browse you got it from in the first place is still open. Searching again may fail to find it and burdens the network unnecessarily (your machine already knows of sources for the file). Leaving a search open until everything you wanted from it downloads limits your options in various ways: less other searches you can run in the meantime; limewire tends to perform poorly if search tabs are left open for an extended time for some reason (and slows the rest of the machine down, even when its cpu priority is lowered!); and you can't close limewire without losing the search tab in question. Letting completed searches and host-browses be saved and loaded, or "put away" and "brought back out" at least, would alleviate this a bit, but really there needs to be a third option for corrupt files: retry. In fact, any file should be retryable. Retry would be a right click option from a download pane item. It would a) halt the download, if in progress; b) delete the incomplete file; and c) resume it, causing it to be queued and eventually start downloading from byte zero. It would be the default option on the corrupt file dialog, with the other options being kill download and continue. (The useless "File Corrupt" status would be gone; you may as well just kill in that case, once you can retry from the file corrupt dialog.) Completed and partial files that aren't explicitly flagged as corrupt are sometimes also in need of a "retry" option, owing to Limewire's woefully poor ability to detect corrupt files reliably. Frequently a file is not as advertised, despite being a valid search result -- I've several times told it to get a batch of sequentially numbered files resulting from a specific search for specific subject matter and found most, on arrival, to be what they were supposed to be but one or two of them to have gotten substituted with spam or damaged somehow -- without the file corrupt dialog occurring, and without the search results being the common spoofed ones that are just "y_o_u_r__s_e_a_r_c_h__t_e_r_m.wmv"n or similar (those I just ignore). I presume that these result from a spammer/spoofer/vandal participating in the download mesh for the file, and Limewire trusting the host that sends the file to send the correct hash as well, instead of the hash coming with the search result instead (stupid; bittorrent is much, much smarter in this area; the scheme Limewire uses seems to be good at detecting accidental corruption but bad at detecting intentional corruption by a client in a file's mesh that is acting in bad faith and attempts to avoid being discovered until you've wasted your time fully downloading the file).