Yep, that did fix it. Not sure what went wrong. Maybe it's because I used the Update method of installation, and the client decided "well it's already updated because this version is also available," yet somehow still decided to change the file name? I dunno.