Nsis Install Vcredist
Question: You previously posted lists of command line switches to perform silent and unattended installations of the and the. How can I perform silent and unattended installations of the Visual C++ 2010 redistributable?
If we now arrived at needed Visual C++ 2010 runtimes, maybe this could be a hint for how to detect by the nsis-standalone installer? Unlike the Visual C++ 2005 and 2008 redistributable packages, there are registry keys that can be used to detect the. Not using the correct (x86 or x64) version of the Visual Studio command prompt. Not copying/downloading the correct version of vcredist_xYY.exe. Smart Copies are created in the same way as Junctions, select a folder, click the Action button, choose Pick Link Source from the action menu.
Answer: The Visual C++ 2010 redistributable packages (vcredist_x86.exe, vcredist_x64. Sap Ecc Crack there. exe and vcredist_ia64. Hauppauge Software Alternative there. exe) support the following command line installation options. The examples below use the file named vcredist_x86.exe, but you can substitute the x64 or ia64 versions of the EXEs with equivalent command lines to achieve the same behavior for them as well. Silent install This option will suppress all UI and perform an install. Vcredist_x86.exe /q /norestart For example, if you download vcredist_x86.exe to a folder named c: vc2010redist, then the command line would look like this: c: vc2010redist vcredist_x86.exe /q /norestart Unattended install This option will display a progress dialog (but requires no user interaction) and perform an install.
Vcredist_x86.exe /passive /norestart For example, if you download vcredist_x86.exe to a folder named c: vc2010redist, then the command line would look like this: c: vc2010redist vcredist_x86.exe /passive /norestart Silent repair This option will suppress all UI and perform a repair. Vcredist_x86.exe /q /repair /norestart For example, if you download vcredist_x86.exe to a folder named c: vc2010redist, then the command line would look like this: c: vc2010redist vcredist_x86.exe /q /repair /norestart Silent uninstall This option will suppress all UI and perform an uninstall. Vcredist_x86.exe /q /uninstall /norestart For example, if you download vcredist_x86.exe to a folder named c: vc2010redist, then the command line would look like this: c: vc2010redist vcredist_x86.exe /q /uninstall /norestart A note about reboots All of the examples above use the /norestart switch to suppress reboots after the setup process completes. The /norestart switch does not eliminate the need to reboot entirely – it just gives the calling process control over when to schedule the reboot if one is needed due to files being in use during setup.
If you run the Visual C++ 2010 redistributable setup and use the /norestart switch, you must check the exit code returned by the setup process and handle it accordingly in the calling process. Here are the possible exit codes: • Exit code 0 means that setup succeeded and no reboot is needed. • Exit code 3010 means that setup succeeded and a reboot is needed to complete installation. • Any other exit code means that setup failed. Related link •.
Thanks Aaron for responding!! When I tried to install VCRT 10 at PC that has no VS2010 installation and Windows XP Service Pack 3 It installs under C:WindowsSystem32 folder and registers under registry. So programmatically checking out at Software Microsoft VisualStudio 10.0 VC VCRedist x86 is ruled out. When I tried to install at PC where no VS 2010 and SP3 (i.e. WIN XP SP2) then it has given following message ————————— Microsoft Visual C++ 2010 x86 Redistributable Setup ————————— Windows Installer version 3.1 or higher is required to perform this installation. Please visit to obtain the appropriate version of Windows Installer 3.1 for your system. ————————— OK ————————— So, it requires minimum WIN-XP SP3 or WIN-XP SP2 + Windows Installer 3.1 (Minimum) so it will not work with Windows Installer 2.0 Now my task is to find out whether VC10 RTLs are installed or not In VC8 we are checking by whether ATL80.dll exist or not at C:WINDOWSWinSxSx86_Microsoft.VC80.ATL_XXXXXXXXXXATL.dll where XXXXXX is Version String e.g.C:WINDOWSWinSxSx86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_6e805841 folder, so it is giving specific version for RTLs but in VC10 it is copying at System32 folder without specific to any version.
Comments are closed.