darktjm: I mean, most downloaders, even the crappy default web browser ones, can continue aborted downloads, so I guess I don't understand the big deal.
I think it still depends on how the download server works. At least I've had numerous cases where e.g. Firefox hasn't been able to resume the download (that was interrupted for an unknown reason), and if you exit the download "screen", Firefox will automatically delete the partial fire.
There was a rather complicated workaround for that (at least on that particular download site; not sure if it'd work in e.g. GOG):
1. Do not exit the FF download screen (so that you still have the partial file).
2. With File Explorer, copy the partial file somewhere else.
3. Exit the download screen, and restart the whole download. This will recreate that partial file.
4. Pause that download manually, copy the original (bigger) partial file over the new one, and resume the download.
darktjm: Using FAT32 for a multi-TB drive is insane. Windows users should also immediately reformat such drives with NTFS (prefereably multi-partition with a small FAT at the beginning for use with devices that only support FAT).
exFAT is supposed to be the solution, FAT without e.g. the 4GB restriction, and still more lightweight than NTFS, without features that are probably not needed on USB drives and such, like file ownerships, group policies or whatever there is in NTFS.
darktjm: I guess timppu's argument that it's for faster virus scanning holds some merit as well. It's not something most non-Windows users do by default, I guess. There are other, better ways to protect against such things rather than pattern scanning every executable.
I've seen that behavior myself at least in Windows 7 (with Microsoft's own antivirus), with those GOG game installers where the .exe is big, like several hundred megabytes. There has been a long pause when you run the installer, before anything happens. I think others have reported it as well.
With those divided games where the first .exe file is small, no such problem (ie. the pause is very short).
I can't tell for sure now if that behavior still exists in Windows 10 and 11... I could test it, I guess.