When Launchy is fetching favicons it does not seem to follow HTTP redirects. This results in a number of .ico files in the %userprofile%\AppData\Roaming\Launchy\weby-icon-cache\ folder that contain HTML code (the redirect response) such as the following:
--en.wikipedia.com.ico
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://en.wikipedia.org/favicon.ico">here</a>.</p>
</body></html>
--en.wikipedia.com.ico--
Note also:
A number of web sites use .gif, .jpeg, .png files for their favicon.ico files - is Launchy actually checking that the MIME type of the favicon is image/x-icon (of sniffing the image data) and converting it appropriately if it is different?
eg: GIF89a, http://ajaxify.com/favicon.ico
eg: JPEG, http://au.toyotaownersclub.com/favicon.ico
eg: PNG, http://auspost.com.au/favicon.ico