^ That explains how to make the patcher run as admin automatically, for all those that have been asking. It requires the Windows SDK (which is free) to do so, but it only take a few minutes to set it up.
By the way, Aeomin, there seems to be some kind of issue with the newest version (184.108.40.206) giving corrupt patches. I know for a fact that the files I'm patching aren't corrupt (if I put them in a GRF myself they work fine, and even viewing in Windows via thumbnail shows up fine), but as soon as I patch them using the latest Thor they'll be corrupt. It only happens with a few select files, but if I try to re-patch them (again, using the clean, non-corrupt files), they'll still be corrupt. If I try patching those same files in again with a new file name, they'll suddenly be okay.
Which leads me to 2 questions:
1) Is there a known issue with certain files or file names not being packed properly by Thor? It seems to happen with various file types (.spr, .bmp, etc), so I'm not sure exactly what causes the corruption. It's definitely not a problem with the original files, though.
2) Does the new patcher have some kind of check to avoid duplicate files being patched in? It seems odd that I can't just re-patch the clean files to fix them, and doing multiple patches so I can rename corrupt files is a little excessive.
As a note, I previously used version 220.127.116.11 and never had a single corrupt patch go through that one, so it's definitely something that was changed in the patcher in one of the more recent updates.