Jump to content
ricktendo

[AIO] Microsoft Visual B/C++/F#/J# Redistributable x86/x64

Recommended Posts

The "problem" is not a problem and has nothing to do with this installer. Its photosop wanting to install the original vc10, it fails because there is a newer version installed, then it craps out... Other than removing the latest runtime and replacing it with rtm I cannot do anything about this, you will need to uninstall the latest, install photoshop, let it install older runtimes, uninstall those and re-run this installer with /aiX to ONLY install the vc10 runtimes

Share this post


Link to post
Share on other sites

The "problem" is not a problem and has nothing to do with this installer. Its photosop wanting to install the original vc10, it fails because there is a newer version installed, then it craps out... Other than removing the latest runtime and replacing it with rtm I cannot do anything about this, you will need to uninstall the latest, install photoshop, let it install older runtimes, uninstall those and re-run this installer with /aiX to ONLY install the vc10 runtimes

 

Photoshop only tries to installs it's own VC10 if i'm using the AIO-Pack if i install the orginal Visual C++ 2010 SP1 than Photoshop won't try to install it's own VC10.

Edited by SuperLOL

Share this post


Link to post
Share on other sites

OK now I understand the cause of the error, it was because after I apply the MSP update to the MSI it changed the Package Code, if I change it back to what RTM had it photosop will attempt to install and it will simple do a repair install of the current installed vc2k10 (I do a similar thing with my .net packs)

Updated

Share this post


Link to post
Share on other sites

is there any easy way to have the installer keep the original uninstall display names for all entries added to control panels programs and features directory?

Share this post


Link to post
Share on other sites

When installing on Windows 7 SP1 x64 I'm getting the following error on the 2005 and 2008 x64 / x86 libraries:

 

"An error ocurred during the installation of assembly"

 

For more details of the error, please see the attached filed.

post-57037-0-53481600-1397435413_thumb.j

Share this post


Link to post
Share on other sites

In this case I was trying to install it on my fresh Windows 7 installation, but I forgot the silent /y and /gm2 switches, will it make any difference? If so, can't it be installed on Windows 7 fresh installations?

 

I had other installer which worked fine, but didn't had the 2012 libraries your installer had.

 

Only those 2 failed, the F#, J#, 2010, 2012 & 2013 libraries installed with no problems.

Edited by Neo2x

Share this post


Link to post
Share on other sites

Neo2x, if I understand correctly, I think Rick was asking exactly when, or by what means, are you triggering the installer?  He explained that those errors occur when the install is attempted before log in has completed.
 
Cheers and Regards

Share this post


Link to post
Share on other sites

Ok, I just want to know if there is any place your installer could work on a Windows 7 DVD. I just want to automate the install process.

Edited by Neo2x

Share this post


Link to post
Share on other sites

Ok, I just want to know if there is any place your installer could work on a Windows 7 DVD. I just want to automate the install process.

 

You can stick it in your autounattend.xml file.  I do it like this:

 

1. Create the $OEM$ folder in the Windows source to dump the switchless into the %SystemRoot%\Temp folder, like so:

(Windows installer source root)||-- $OEM$  |  |-- $$    |    |-- Temp

2. Copy the switchless to "Temp".

 

3. Set up your autounattend.xml to do a "SynchronousCommand" under "FirstLogonCommands" in the "Microsoft-Windows-Shell-Setup" settings, "oobeSystem" pass.  Here's a snippet from my autounattend.xml (Win7 Ultimate x64) using the VB/C++-only installer:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend">    <settings pass="oobeSystem">        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">            <FirstLogonCommands>                <SynchronousCommand wcm:action="add">                    <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai</CommandLine>                    <Description>Microsoft Visual B/C++ Redistributables (AIO)</Description>                    <Order>1</Order>                </SynchronousCommand>            </FirstLogonCommands>        </component>    </settings>    <cpi:offlineImage cpi:source="wim:c:/win7dvd/grmculxfrer_en_dvd/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

You can run multiple commands as well if you only install certain components.  For example, to do VC++ 2005 and 2008 only executing the /ai5 and /ai8 switches:

            <FirstLogonCommands>                <SynchronousCommand wcm:action="add">                    <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai5</CommandLine>                    <Description>Microsoft Visual C++ 2005 Redistributable</Description>                    <Order>1</Order>                </SynchronousCommand>                <SynchronousCommand wcm:action="add">                    <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai8</CommandLine>                    <Description>Microsoft Visual C++ 2008 Redistributable</Description>                    <Order>2</Order>                </SynchronousCommand>            </FirstLogonCommands>

Add as many commands as you need, just bumping the "<Order>" number for each successive entry.

 

 

Notes:

-- You can change the install directory to whatever you want, so long as you put it in the proper $OEM$ folder structure.  I chose Windows\Temp so the installer gets auto-deleted after use.

-- It must go under the "oobeSystem" pass to launch after user creation, or else you'll get the same errors as before.

-- Same method should work for most programs that have the same requirement of being run after user creation.

-- There are probably other methods of doing it which other posters could elaborate, but this one has worked flawlessly for me with this particular switchless.  And is good if you already use autounattend.xml and want to keep things nicely consolidated there.

-- WSIM automates creation of autounattend.xml graphically if you don't want to deal with raw XML syntax.  Download the Windows ADK from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=30652) if you need that tool.

Share this post


Link to post
Share on other sites

I did what you suggested, created the same autounattend.xml (on the root of my DVD) as the one on step 3 (only changed the switch to /y) but after Windows installation and restart it didn't do anything. The only thing I noticed was that the VBCRedist_AIO_x86_x64.exe ended up in c:\windows\temp as the $OEM$ folder structure indicated. Another thing I changed was the "cpi:offlineImage cpi:source" to:

"wim:d:/sources/install.wim#Windows 7 ULTIMATE", but don't know what is the criteria for this property (my Windows is also Win 7 Ultimate x64).

 

BTW I'm using WinToolkit to integrate updates and silent installers into Windows.

Edited by Neo2x

Share this post


Link to post
Share on other sites

I did what you suggested, created the same autounattend.xml (on the root of my DVD) as the one on step 3 (only changed the switch to /y) but after Windows installation and restart it didn't do anything. The only thing I noticed was that the VBCRedist_AIO_x86_x64.exe ended up in c:\windows\temp as the $OEM$ folder structure indicated. Another thing I changed was the "cpi:offlineImage cpi:source" to:

"wim:d:/sources/install.wim#Windows 7 ULTIMATE", but don't know what is the criteria for this property (my Windows is also Win 7 Ultimate x64).

 

BTW I'm using WinToolkit to integrate updates and silent installers into Windows.

 

The cpi:offlineimage line would be unique to your installation and what folder you use for building your image, so mine probably isn't applicable.  Likewise, the syntax on the component name line can differ depending on whether you're doing an x86 or x64 image, and possibly by edition.  I'd use WSIM or some other off-shelf autounattend.xml generator to set up a default file for your installation.  Maybe just doing some placeholder setting in oobeSystem > Microsoft-Windows-Shell-Setup to make sure there's no syntax differences there, either.  Then if you want to raw-edit the XML just template and build it out from there.

 

If it's dropping the file in the correct $OEM$ folder you should be able to execute it with any switch as if it were a normal command line if set up as a FirstLogonCommands > SynchronousCommand execution.  The only thing that does is time the execution after user creation when you're safely in the clear to install any of the packages in this switchless installer; what you execute and what command line switches you use are no different at that point than they'd be with any other standard means of integrating a switchless into Win7/8.

 

 

 

I built mine in WSIM on Win7 Ultimate x64 as the first-and-only command in FirstLogonCommands, so I can confirm that method + the correct $OEM$ placement produces a working switchless installation.  I don't use WinToolkit myself, opting instead for a combo of Windows Hotfixes Downloader for update/driver integration, WINNT True Integrator for addons and switchlesses, and WSIM/autounattend for settings and switchlesses with special post-logon requirements like this one.  If you're having no luck you may want to try creating the autounattend file with WSIM--at least as far as setting up this installer--to produce a reliably working template before doing as you wish with the rest of your XML file via manual edit or adding/merging to it in some other program.  That's the most fail-safe troubleshooter I can suggest, since I'm not terribly adept at writing or debugging XML by hand.

Edited by RP1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By robertcollier4
      Install Instructions
      1. Make sure to have Windows Update service enabled during install. (can disable it after install again).
      2. For Windows 7, update KB4019990 is required to be installed before:
      http://download.microsoft.com/download/2/F/4/2F4F48F4-D980-43AA-906A-8FFF40BCB832/Windows6.1-KB4019990-x86.msu
      http://download.microsoft.com/download/2/F/4/2F4F48F4-D980-43AA-906A-8FFF40BCB832/Windows6.1-KB4019990-x64.msu
      3. Install this Repack .NET 4.7.2 Slim - without the installer junk - installs directly without leaving behind installer files.
      dotNetFx472_Slim_x86_x64(ricktendo2018-05-01).exe
      Alternative Mirror Download
      https://www.mirrored.to/files/K4VQX3HM/NET_Framework_4.7.2_Slim_x86x64_(5-1-2018).exe_links
       
    • By abbodi1406
      Description:

      The Visual C++ Redistributable Packages install runtime components that are required to run applications that are developed by using Visual Studio. These packages install run-time components of these libraries: C Runtime (CRT), Standard C++, ATL, MFC, C++ AMP, OpenMP and MSDIA. read more.

      OS: Windows All

      Versions:
      VC++ 2019: 14.24.28127.4 VC++ 2013: 12.0.40664.0 VC++ 2012: 11.0.61135.400 VC++ 2010: 10.0.40219.473 VC++ 2008: 9.0.30729.7523 VC++ 2005: 8.0.61187 VC++ 2003: 7.10.6119.0 Vc++ 2002: 7.0.9975.0 + Legacy Visual Basic Runtimes Files Contents:
      vcredist_x64_Win7 / vcredist_x86_Win7: All runtimes for Windows 7 SP1 vcredist_x64_2019_WinAll / vcredist_x86_2019_WinAll: Visual C++ 2019 vcredist_x64_2013d_WinAll / vcredist_x86_2013d_WinAll: Visual C++ 2013, 2012, 2010, 2003, 2002 Visual Basic 6.0 Runtimes vcredist_x64_SxS_Win7 / vcredist_x86_SxS_Win7: Visual C++ 2008, 2005 for Windows 7 SP1 vcredist_x64_SxS_Win810 / vcredist_x86_SxS_Win810: Visual C++ 2008, 2005 for Windows 8.1/10 Important Notes:
      # Integrating SxS 2008/2005 addons require launching Wintoolkit with TrustedInstaller privileges, to gain write access to WinSxS directory
      for that, you need to use NSudo (or other similar tools):
      - download and extract latest release Binary.zip
      - launch Win32\NSudo.exe or x64\NSudo.exe, or run NSudo.bat as administrator
      - make sure User is set to TrustedInstaller
      - check "Enable All Privileges"
      - paste Wintoolkit.exe path in the lower box (or Browse to the file)
      - click run
      if you are using Windows 7 Simplix Update Pack, you don't need that, it already handle the required privileges
      # vcredist_x64_Win7 / vcredist_x86_Win7 is AIO addon, mainly to be used with Simplix Update Pack, or else you need Wintoolkit with NSudo
      # VC++ 2019 runtimes are binary compatible and upgrade to VC++ 2015-2017 and cover all VS 2015-2017-2019 programs
      # To complete VC++ 2019 function for Windows 7/8.1, you need to integrate Universal CRT components, which is available with latest Monthly Rollup, or updates KB3118401/KB2999226
      Download:
      vcredist_x64_Win7_20191015.WA
      vcredist_x86_Win7_20191015.WA
      vcredist_x64_2019_WinAll_14.24.28127.WA
      vcredist_x86_2019_WinAll_14.24.28127.WA
      vcredist_x64_2013d_WinAll.WA
      vcredist_x86_2013d_WinAll.WA
      vcredist_x64_SxS_Win7.WA
      vcredist_x86_SxS_Win7.WA
      vcredist_x64_SxS_Win810.WA
      vcredist_x86_SxS_Win810.WA
      you can find latest releases -> here
      SHA1 checksums:
      d13217e04e4c27bdb9b6f462eabf1a10fa852b72 *vcredist_x64_Win7_20190716.WA ef0ba3513031651effc100a1f1828e88d81b5640 *vcredist_x86_Win7_20190716.WA 57585ffad5478d6f0d7ba8238c51d6a26d91464e *vcredist_x64_2019_WinAll_14.22.27821.WA 1de5c09f237a2873b92126c170abf9272d947fdf *vcredist_x86_2019_WinAll_14.22.27821.WA 05e938f354c059d89d846d2e9a7591d05154aa70 *vcredist_x64_2013d_WinAll.WA 534f1e53080819aeb58e3b060d7c6a0a76b4d4d4 *vcredist_x86_2013d_WinAll.WA 8cc9f65fc444a878d8cabd0ad317597edb552f07 *vcredist_x64_SxS_Win7.WA 886faa949e7d51a40dc8d467f65c373f887c2ec3 *vcredist_x86_SxS_Win7.WA 94e267e5e6ff89854bd64b6260333664a266c754 *vcredist_x64_SxS_Win810.WA 206fda69fa2d3fd838dd9e3ee33f35c4cd7a2cae *vcredist_x86_SxS_Win810.WA Credits to ricktendo for original repack AIO
    • By ArjunKumar
      Hell Everyone, Anyone here is senior C++ developer? I have experience of 8 month in C++ programming and I want to build my programming skills high. Can you help me how to do it or provide me any online resources where I can grow my skills. 
    • By ricktendo
      Microsoft DirectX end-user Redistributable (June 2010)
      Version: 9.29.1974
      Supported operating systems: Windows 8, Windows 7, Windows Vista, Windows Server 2012/2008+R2/2003 SP1+, Windows XP SP2+
      Website: http://www.microsoft.com/en-us/download/details.aspx?id=8109
       
       
      x86/x64: removed
      MD5: 2ef61d694dbcb3b3d0f47f1bbc0ca831
      Size: 90.7 MB
      x86: removed
      MD5: 0f51f57cff0bf51aa368f90da1c8b525
      Size: 42.8
    • By mooms
      This is a script to repack JRE (Java Runtimes) setups into a silent 7zip SFX installer.


      Beta version for Java 9/10:
      JAVA-Multi_Maker_4.0b4.zip
      MD5: 203c7e514414c932ff847d3d8dac5fa4
      SHA-1: 93fc856e026fc42298ebc8e76bba338f21c1704a
      Size: 800KB

      How to use:
      You have to download the Java 9/10 setup(s) from here (x64)  | mirror x64 | mirror x64 | mirror x86 .
      - Extract the archive in a work folder with no space in the path.
      - Copy the setup(s) in the "JRE_setups" folder
      - Launch "_JAVA_Multi_Maker.cmd".

      Download function may return when Java 9 will be on the official download page.

      Available switches:
      No switch (dafault) - Silent install without Web plugins. Remove any previous Java version(s).
      -ai   - Silent install with Web plugins. Remove any previous Java version(s).
      -ai1  - Silent install without Web plugins. Remove only previous Java 9 version(s).
      -ai2   - Silent install with Web plugins. Remove only previous Java 9 version(s).

      Tested on Windows 7 & 10 x64, everything works as intended.
      Please test and report how it works for you.


       ------------------------------------
       
      Current version (for Java 8u73 and newer) (could work on XP if you use a custom build of aria2)
      JAVA-Multi_Maker_3.5.zip
      MD5: 7716dddd8c576f0d002e6ddeb43d1ac6
      SHA-1: 495cf642bf73571bca97179e63ab28c88ca2f5f1
      Size: 3.79 MB
       
       How to use:
      - Extract the archive in a work folder with no space in the path.
      - Run the batch file.
      - Choose the version you want to use
      The script will download the newest JRE automatically. If there is a problem with the download (or if you don't have access to Internet), you can also put the desired version(s) in the script's folder, it will always use the greater version found in the folder.

      Notes:
      - To avoid errors, the SFX will uninstall any previous Java version(s) newer than JRE 6.0 Update 22 before installing the new one(s).
      nLite/RVMi Addons are no longer created
      - It's highly recommended to NOT install Java web plugins, they are plagued with many vulnerabilities, but using Java locally is rather safe.
      - You can use the uninstall tool for Java to remove (very) old versions.
       

      Available switches:
      GUI version:
      -ai   - Silent install with Web plugins
      -ai1 - Silent install without Web plugins
       
      noGUI version:
      no switch - Silent install without Web plugins
      -ai            - Silent install with Web plugins
       
       
       ------------------------------------

      Old version (for Java 8u20 up to 8u72) (works on XP)
      JAVA-Multi_Maker_3.0.zip
      MD5: d89eec93311acedd842c6378ed630734
      Size: 1.29 MB
       
       ------------------------------------


      Old version (for Java 6, 7 and 8 before 8u20)
      JAVA-Multi_Maker_1.3a.zip
      MD5: 8d592f99c2b25e2c4404203af0b4d082
      Size: 373 KB
      How to use:
      - Extract the archive in a work folder with no space in the path.
      - Download the x86 and/or x64 Offline setup of Java 6/7/8 and put it in the same folder.
      - Run the batch file.
      The maker will perform an admin install of Java and repack them inside a 7zip SFX.
       
      Notes:
      - The install is passive by default, use a switch if you want silent install.
      - To avoid errors, the SFX will uninstall any previous Java version(s) newer than JRE 6.0 Update 22 before installing the new one(s).
      - Update check and Java quick starter are disabled (JQS doesn't exist in x64 anyway).
      - It's highly recommended to NOT install Java web plugins, they are plagued with many vulnerabilities, but using Java locally is rather safe.
      - You can use the uninstall tool for Java to remove (very) old versions.
       
      Available switches:
      -ai   - Silent install with Web plugins
      -ai1 - Silent install without Web plugins
×
×
  • Create New...