If you run dotNetFx40_Full_x86_x64.exe /?, it will extract the setup files into a temporary directory and then display help text reproduced below. However, setup.exe can't be run directly and will just give you an error message, so the text below appears to be misleading.

/CEIPconsent - Optionally send anonymous feedback to improve the customer experience.
/chainingpackage <name> - Optionally record the name of a package chaining this one.
/createlayout <full path> - Download all files and associated resources to the specified location. Perform no other action. * Disabled *
/lcid - Set the display language to be used by this program, if possible. Example: /lcid 1031
/log <file | folder> - Location of the log file. Default is the process temporary folder with a name based on the package.
/msioptions - Specify options to be passed for .msi and .msp items. Example: /msioptions "PROPERTY1='Value'"
/norestart - If the operation requires a reboot to complete, Setup should neither prompt nor cause a reboot.
/passive - Shows progress bar advancing but requires no user interaction.
/showfinalerror - Passive mode only: shows final page if the install is not successful.
/pipe <name> - Optionally create a communication channel to allow a chaining package to get progress.
/promptrestart - If the operation requires a reboot to complete, Setup should prompt, and trigger it if the user agrees.
/q - Quiet mode, no user input required or output shown.
/repair - Repair the payloads.
/serialdownload - Force install operation to happen only after all the payload is downloaded.
/uninstall - Uninstall the payloads.
/parameterfolder <full path> - Specifies the path to the Setupâs configuration and data files.
/NoSetupVersionCheck - Do not check ParameterInfo.xml for setup version conflicts.
/uninstallpatch {patch code} - Removes update for all products the patch has been applied to.
/? - Display this help.

The above post about "Blocking Issues" when running the setup.exe from the extracted files is respectfully, incorrect. You must add an extra switch, either "/x86" or "/x64" in addition to the options you select.

If you run dotNetFx40_Full_x86_x64.exe /?, it will extract the setup files into a temporary directory and then display help text reproduced below. However, setup.exe can't be run directly and will just give you an error message, so the text below appears to be misleading.

/CEIPconsent - Optionally send anonymous feedback to improve the customer experience.
/chainingpackage <name> - Optionally record the name of a package chaining this one.
/createlayout <full path> - Download all files and associated resources to the specified location. Perform no other action. * Disabled *
/lcid - Set the display language to be used by this program, if possible. Example: /lcid 1031
/log <file | folder> - Location of the log file. Default is the process temporary folder with a name based on the package.
/msioptions - Specify options to be passed for .msi and .msp items. Example: /msioptions "PROPERTY1='Value'"
/norestart - If the operation requires a reboot to complete, Setup should neither prompt nor cause a reboot.
/passive - Shows progress bar advancing but requires no user interaction.
/showfinalerror - Passive mode only: shows final page if the install is not successful.
/pipe <name> - Optionally create a communication channel to allow a chaining package to get progress.
/promptrestart - If the operation requires a reboot to complete, Setup should prompt, and trigger it if the user agrees.
/q - Quiet mode, no user input required or output shown.
/repair - Repair the payloads.
/serialdownload - Force install operation to happen only after all the payload is downloaded.
/uninstall - Uninstall the payloads.
/parameterfolder <full path> - Specifies the path to the SetupÃ¢Â€Â™s configuration and data files.
/NoSetupVersionCheck - Do not check ParameterInfo.xml for setup version conflicts.
/uninstallpatch {patch code} - Removes update for all products the patch has been applied to.
/? - Display this help.

- This example is for x86 machines, I assume you can use the same method for x64 systems (not tested)
- Please note that your system meets the right Prerequisites, like OS service pack, windows installer version, WIC .. (For Win XP SP2 you need MS Installer 3.1 + wic_x86_enu.exe)

- This example is for x86 machines, I assume you can use the same method for x64 systems (not tested)
- Please note that your system meets the right Prerequisites, like OS service pack, windows installer version, WIC .. (For Win XP SP2 you need MS Installer 3.1 + wic_x86_enu.exe)

/CEIPconsent â Optionally send anonymous feedback to improve the customer
experience.
/chainingpackage <name> â Optionally record the name of a package chaining
this one.
/createlayout <full path> â Download all files and associated resources to the
specified location. Perform no other action. * Disabled *
/lcid â Set the display language to be used by this program, if possible. Example:
/lcid 1031
/log <file | folder> â Location of the log file. Default is the process temporary
folder with a name based on the package.
/msioptions â Specify options to be passed for .msi and .msp items. Example:
/msioptions "PROPERTY1='Value'"
/norestart â If the operation requires a reboot to complete, Setup should neither
prompt nor cause a reboot.
/passive â Shows progress bar advancing but requires no user interaction.
/showfinalerror â Passive mode only: shows final page if the install is not
successful.
/pipe <name> â Optionally create a communication channel to allow a chaining
package to get progress.
/promptrestart â If the operation requires a reboot to complete, Setup should
prompt, and trigger it if the user agrees.
/q â Quiet mode, no user input required or output shown.
/repair â Repair the payloads.
/serialdownload â Force install operation to happen only after all the payload is
downloaded.
/uninstall â Uninstall the payloads.
/parameterfolder <full path> â Specifies the path to the Setupâs configuration and
data files.
/NoSetupVersionCheck â Do not check ParameterInfo.xml for setup version
conflicts.
/uninstallpatch {patch code} â Removes update for all products the patch has
been applied to.
/? â Display this help.

/CEIPconsent Ã¢Â€Â Optionally send anonymous feedback to improve the customer
experience.
/chainingpackage <name> Ã¢Â€Â Optionally record the name of a package chaining
this one.
/createlayout <full path> Ã¢Â€Â Download all files and associated resources to the
specified location. Perform no other action. * Disabled *
/lcid Ã¢Â€Â Set the display language to be used by this program, if possible. Example:
/lcid 1031
/log <file | folder> Ã¢Â€Â Location of the log file. Default is the process temporary
folder with a name based on the package.
/msioptions Ã¢Â€Â Specify options to be passed for .msi and .msp items. Example:
/msioptions "PROPERTY1='Value'"
/norestart Ã¢Â€Â If the operation requires a reboot to complete, Setup should neither
prompt nor cause a reboot.
/passive Ã¢Â€Â Shows progress bar advancing but requires no user interaction.
/showfinalerror Ã¢Â€Â Passive mode only: shows final page if the install is not
successful.
/pipe <name> Ã¢Â€Â Optionally create a communication channel to allow a chaining
package to get progress.
/promptrestart Ã¢Â€Â If the operation requires a reboot to complete, Setup should
prompt, and trigger it if the user agrees.
/q Ã¢Â€Â Quiet mode, no user input required or output shown.
/repair Ã¢Â€Â Repair the payloads.
/serialdownload Ã¢Â€Â Force install operation to happen only after all the payload is
downloaded.
/uninstall Ã¢Â€Â Uninstall the payloads.
/parameterfolder <full path> Ã¢Â€Â Specifies the path to the SetupÃ¢Â€Â™s configuration and
data files.
/NoSetupVersionCheck Ã¢Â€Â Do not check ParameterInfo.xml for setup version
conflicts.
/uninstallpatch {patch code} Ã¢Â€Â Removes update for all products the patch has
been applied to.
/? Ã¢Â€Â Display this help.

Doing some lab testing for ConfigMgr 2012. I wanted to install App-V 5.0 Beta but it needed the .NET Framework 4 Full as a prereq. So, created the .NET Framework 4 Full application with the following command line:

Doing some lab testing for ConfigMgr 2012. I wanted to install App-V 5.0 Beta but it needed the .NET Framework 4 Full as a prereq. So, created the .NET Framework 4 Full application with the following command line:

With this package, you cannot extract the files out by running dotNetFx40_Full_x86_x64.exe and then looking for the setup.exe where the files were extracted. If you just run setup.exe, you'll get the following error message:

Blocking Issues:
You cannot use this setup program to install the .NET Framework.