There's nothing wrong with the KCLT installer. The installer has a checksum so, if you got a bad download, it wouldn't even start, because it wouldn't pass the initial checksum.
Yes, it's absolutely normal you won't see any scenery if the installer doesn't complete.
No, it's absolutely NOT normal the installer wouldn't complete, and it's surely not a problem of the installer.
These are the things that *might* cause an installer to hang:
- Not enough space on your Windows temporary folder. Regardless *where* you choose to install into, the installer must first uncompress all its files into the Windows temporary folder so, if your Windows disk doesn't have much space left, the installer will hang, no matter how much space you have on the final destination drive.
- Not enough space on the destination driver. Well, this should be obvious but, better add it, just to be sure.
- Not enough space on your SWAP drive. The installer requires some RAM too and, if you are running many application at once, you might be short on RAM. When you are short on RAM, in addition to the system becoming *A LOT* slower, because it's starting to use the Swap file to get additional ram, if you set the swap file to a fixed maximum size, or you disabled it, or you don't have enough space on the drive the swap file is located on, the swap file won't work, so the installer will stop because it has exhausted all available RAM (real or virtual)
- Antivirus still blocking the installer, even when it LOOKS disabled. Yes, I personally witnessed this on several occasions while doing remote assistance. The antivirus looked to be disabled, but its low-level Windows service was *still* doing its (wrong) job of mistakenly blocking files. Sometimes is not really "blocking" files but, it was so slow, that it looked like the system was hang.
That's why we always say to EXCLUDE the Addon Manager folder from scanning, instead of "disabling" it (which might not always works as expected).
