Windows: What are the general install methods? Together with one "example install" to be named correctly

This is a confusion from https://stackoverflow.com/questions/63163178/installed-cuda-without-conda-can-pytorch-use-a-non-conda-cuda-toolkit.

Here is the example question at first, just one correct install name is asked for the following installation method:

• If conda cudatoolkit from https://anaconda.org/anaconda/cudatoolkit is a binary install,

• and something that compiles the source code on the local system is a source install according to https://stackoverflow.com/questions/5280906/difference-between-groovy-binary-and-source-release,

• what kind of install would you call the non-conda cuda-toolkit available at
  https://developer.nvidia.com/cuda-toolkit?

This question should be answered, together with a general list of all Windows install methods.

Some good hints come from Ask Ubuntu Stack Exchange. They seem highly applicable to Windows installation methods, see https://askubuntu.com/questions/123077/installing-applications-from-source/123087#123087.

Ubuntu offers a variety of installation methods:

1. Centralised packaging system: This is the preferd method in ubuntu (but personally I don’t like it) software-centre, synaptic, and
   aptitude are examples

2. Standalone deb package: This method is simpler as in the case of windows, just double click the file and press install button, for
   example: Gdebi package manager

3. Binary software: These are very similar to windows .exe installation, offering a variety of gui for installer, these are
   usually .bin files. You can use bit rock or similar tools to make such
   packages.

4. Autopackage and similar tools : these are third party package managers created to support various Linux distributions

5. Source code: This is the first method in the software installation. In this method the source code is converted into the binary
   executables, installation instructions for these softwares are usually
   attached with source code, and these are valid for open source s/w
   only

Perhaps there are specific Windows installation methods or namings. You might call the Ubuntu "Standalone deb package" on Windows a "standalone install". A "Windows binary install" might be the same as an "executable". Or the like, clearing up the synomyms and Windows specific names.