Jump to content

Featured Replies

Posted
  • Popular Post

Info: Microsoft Visual C++ 2005/2008/2010/2012/2013/2014/2015, Microsoft Visual F# 2.0, Microsoft Visual J# 2.0 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow)

Same as above but excludes F# & J# runtimes

 

Info: Microsoft Visual C++ 2005/2008/2010/2012/2013 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow)

Some tools and resources for (re)creating your own installer

 

Visual AIO SFX Maker v6 (installer repacker):http://adf.ly/1713566/visualsfxSilent "No GUI" SFX alternative v4:http://adf.ly/1713566/visualsfxngKB2538242 MST Windows Update fix v1.7:http://adf.ly/1713566/wufix5mstKB2538243 MST Windows Update fix v3:http://adf.ly/1713566/wufix8mstMsiTran.Exe -a <transform>.MST <installer>.MSI:http://adf.ly/1713566/msitranSlim down your vcredist 2005/2008 installers:http://adf.ly/1713566/msislim"Extra" Visual Basic/C runtimes installer sourceshttp://adf.ly/1713566/vbcsourceIf you cant find a hotfix try using the KB number w/ this URLhttp://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=1234567

Hotfix list

 

 

2005: 2643995

2008: 2834565

2010: 2821701

2012: Release 4

 

Also includes:

 

 

 

name            version/*-- Microsoft Visual Basic Runtimes -----------------------------------*/ comct232.ocx        6.0.98.39comct332.ocx        6.7.0.9839comctl32.ocx        6.0.98.39comdlg32.ocx        6.1.98.41dblist32.ocx        6.1.98.39mci32.ocx        6.1.98.39mscomct2.ocx        6.1.98.39mscomctl.ocx        6.1.98.39mscomm32.ocx        6.1.98.39msdatgrd.ocx        6.1.98.39msdatlst.ocx        6.1.98.39msflxgrd.ocx        6.1.98.39mshflxgd.ocx        6.1.98.39msinet.ocx        6.1.98.39msmask32.ocx        6.1.98.39msstdfmt.dll        6.1.98.39msstkprp.dll        6.1.98.39mswinsck.ocx        6.1.98.39   picclp32.ocx        6.1.98.39richtx32.ocx        6.1.98.39sysinfo.ocx        6.1.98.39tabctl32.ocx        6.1.98.39vb40032.dll        4.0.29.22/*-- Microsoft Visual Basic Runtimes (16bit) ----------------------------*/vb40016.dll        4.0.24.22vbrun100.dll        <none>vbrun200.dll        2.0.9.8vbrun300.dll        3.0.5.38/*-- Microsoft Visual Basic Virtual Machine -----------------------------*/msvbvm50.dll        5.2.82.44/*-- Microsoft Visual C Runtimes ----------------------------------------*/atl70.dll        7.0.9975.0atl71.dll        7.10.6119.0mfc70.dll        7.0.9975.0mfc70chs.dll        7.0.9975.0mfc70cht.dll        7.0.9975.0mfc70deu.dll        7.0.9975.0mfc70enu.dll        7.0.9975.0mfc70esp.dll        7.0.9975.0mfc70fra.dll        7.0.9975.0mfc70ita.dll        7.0.9975.0mfc70jpn.dll        7.0.9975.0mfc70kor.dll        7.0.9975.0mfc70u.dll        7.0.9975.0mfc71.dll        7.10.6119.0mfc71chs.dll        7.10.6119.0mfc71cht.dll        7.10.6119.0mfc71deu.dll        7.10.6119.0mfc71enu.dll        7.10.6119.0mfc71esp.dll        7.10.6119.0mfc71fra.dll        7.10.6119.0mfc71ita.dll        7.10.6119.0mfc71jpn.dll        7.10.6119.0mfc71kor.dll        7.10.6119.0mfc71u.dll        7.10.6119.0msvci70.dll        7.0.9955.0msvcp70.dll        7.0.9466.0msvcp71.dll        7.10.6052.0msvcr70.dll        7.0.9981.0msvcr71.dll        7.10.7031.4msvcrt10.dll        <none>

 

  • Replies 456
  • Views 433k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

Posted Images

  • Author
?: Why is this nearly double the size of Yumeyao's addon? Just wondering.

Silent installer with both x86 and x64 runtimes, yumeyaos is a true addon with only x86 runtimes (minus msdia*.dll)

Would it be appropriate to add in some of the old VB runtimes that are occasionally needed for old software compatibility, or not?

Cheers and Regards

  • Author

I was about to do that, but I was planning a secondary installer just trying to decide what installer engine to use. I think a inno setup (that creates no uninstall entries) is best because of restart replacement and file registration, I can also probably add some user choices weather to install old 16bit vb runtimes and only offer them on 32bit installs

  • Author
So no updating a live system with it?

HUH!?!?

You want the old runtimes uninstalled you have to manually uninstall them, you want a installer that does this automatically use burfadels aio vc installer

I dont add it because I dont know how effective it would be scanning the registry with a 32bit installer on a 64bit system and I see no need for this so called "feature"

LOL - OK - I was thinking about the case if a new update comes out for 2010 next month. You can just run the updated installer on a live system and everything will work just fine, right? Or does it need to have the existing one uninstalled or not? Sorry, I'm a little bit confused.

Cheers and Regards

  • Author

Lets say hypothetically a new vc 2008 redist hotfix comes out, I have to apply my mst (changes the productcode property) to fool WU into thinking its KB2538243. For the new package to install successfully you have to uninstall the current vc 2008 redist (because it also has the same productcode,) then to install you would use the updated installer with

VCRedist_AIO_x86_x64.exe /ai8

BTW do you guys think I should add Visual F# and Visual J# Runtimes?

You would be able to skip them during gui install with SHIFT or unattended install with /ai

Yes I agree. In fact, it seems to me to make sense to have one pack for all the Visual Runtimes, the way that RogueSpear used to have, but I'm sure others might disagree.

Thanks for the explanation, Rick, about needing to uninstall the previous runtime redist prior to installing the new one. But since that is true, then I'm not sure I understand your point about the uninstaller being an unneeded "feature". Unneeded for a fresh install, but it seems needed for an update on a live system, or am I missing something?

Cheers and Regards

  • Author
I got an error code 2337 on F# 2.0 runtime when installing the AIO installer on VM (Win7 x64).

Do you have .net2 or .net4 installed?

BTW: updated rev2 to fix hidden uninstall entry of vj# x64 (removed ARPSYSTEMCOMPONENT from property)

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...