AutoPatcher Forum

ViroMan, on 08 April 2012 - 05:21 AM, said:

That's why I'm waiting and watching. The comments about the "Metro" desktop - whatever that is or supposed to be - has delayed any 'do it now' feelings I may have had. Plus, there are many other comments that dual or multiboot will not be permitted.

New system, new install of Win7 Ultimate w/SP1 64bit.

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA5E371C-6333-3D8A-93A4-6FD5B20BCC6E}
DisplayName: Microsoft Visual C++ 2010 x64 Redistributable - 10.0.30319
DisplayVersion: 10.0.30319

InstallSource: C:\ATI\SUPPORT\12-3_win7_64_dd_ccc\Packages\Apps\VC10RTx64\vcredist_x64\

New install of Win7 Ultimate w/SP1 32bit.

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{196BB40D-1578-3D01-B289-BEFC77A11A1E}
DisplayName: Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319
DisplayVersion: 10.0.30319

InstallSource: C:\ATI\Support\12-3_win7_32_dd_ccc\Packages\Apps\VC10RTx86\vcredist_x86\

Comments: Caution. Removing this product might prevent some applications from running.

As I posted above - new hardware and new software installations. I figured I'd try to see if I could find an explanation for the differences in the registry keys I have versus what is in the APM files. I have only started to install the software applicable to my new hardware; mainly Win7, motherboard drivers, sound system drivers, and video card drivers.

When I installed the latest AMD/ATI Catalyst Drivers for my Radeon HD 6970 video card the install routine also installed versions of Visual C++ as indicated above. These keys are NOT the keys defined by the AutoPatcher APM files and are why I was having slightly different results - as reported above.

So, I would have to expect that any and all future AMD/ATI updates could also result in different registry keys - and these keys may also mess with keys created by a previous or later install of the Visual C++ redistributables downloaded directly from Microsoft or installed by other programs install routines.

So, I would assume that future Visual C++ updates and/or AMD/AT updates and/or nVidia video updates ( I have no idea here as to their use of Visual C++ - I just mention the possibility) could have an impact on AutoPatcher ressults and reports.

I hope all this made sense - ask if necessary.

Off to finish insstalling things.

That is an older version of the install. The newer ones from Microsoft are 10.0.40219. Supposedly the newer ones will work for anything that required the older ones so, NOT installing the older ones is recommended.

Yes, not installing the older one is possible but, the comment from AMD/ATI about not removing it could cause problems for some people. To avoid installing the 'older' AMD/ATI version that comes with the update installer program the user would have to remember, every month, to not check the box during the update installation. If the user allowed the AMD/ATI installer to install using the default options then I would have to assume 'older' would overwrite 'newer' - or would this not happen? I have no idea as to the possibility of this happening.

You are correct with your assumption that the older version will overwrite the newer one. I did that by accident on my XP Pro x64.
AMD/ATI are always a bit behind with the version of Visual C++ as they utilize the latest version at the start of writing their software package, even if a newer is available at the time for release they don't rewrite for the newer version.

@DesertJerry.... just extracted the package for nVidia 296.10 and they don't use Visual C++, it's only AMD/ATI that do.
Edited by Whatacrock, 13 April 2012 - 03:03 AM.

I'd been wondering about VC redistributables installing multiple versions before; now I see that i'm not the only one to have noticed this.
Previously, i just deleted the older versions, yet to my annoyance the odd install package would re-install the older versions.
I noted no compatability issues after uninstalling the older versions, IIRC.
This looks like a job for CCleaner!

currently using for x86:

• VC2005 SP1 KB2538242 Redistributable http://www.microsoft...s.aspx?id=26347 aka v8.0.61001
  
• VC2008 SP1 KB2538243 Redistributable http://www.microsoft...s.aspx?id=26368 aka v9.0.30729.6161
  
• VC2010 SP1 KB2565063 Redistributable http://www.microsoft...s.aspx?id=26999 aka v10.0.40219

13 April - test Win7 Ultimate w/SP1 64bit

Opted to use Add/Remove Programs and uninstall Microsoft Visual C++ 2010 x64 Redistributable - 10.0.30319. Opened registry editor and confirmed key shown above was no longer shown. (This is/was installed as part of the AMD/ATI video driver installation.)

Proceeded to install from my downloads folder (not yet from within AutoPatcher):
VisualC++2005Redist_x64
VisualC++2005Redist_x64_SecurityPack
VisualC++2005SP1Redist_x64
VisualC++2005SP1Redist_x64_ATLSecurityUpdate
VisualC++2005SP1RedistMFCSecurityUpdate_x64
VisualC++2008Redist_x64
VisualC++2008Redist_x64_SecurityPack
VisualC++2008SP1Redist_x64
VisualC++2008SP1Redist_x64_SecurityPack
VisualC++2008SP1RedistMFCSecurityUpdate_x64
VisualC++2010Redist_x64
VisualC++2010Redist_x86_x64
VisualC++2010SP1Redist_x64

Verfied installation in Control Panel > Programs and Features.

Started AutoPatcher > Windows Addons > All Visual C++ x64 items blue; x86 items black. That to me would confirm my previous comments about the AMD/ATI installation creating a registry key specific to that installation and not the standard one created when the download from Microsoft is installed.

Started AMD/ATI Catalyst Control Center and no problems appeared - so it would seem it is not necessary to install the Visual C++ version that is part of the video driver updates.

I would. therefore, recommend that the user not install the Visual C++ version that comes with the AMD/ATI driver updates. Assuming all my results above are correct/valid and no one has a question the next item would be to install all the x86 versions of the Visual C++ runtimes/redistributables. I won't do the x86 installs for a couple of days - just in case someone has a question that requires an answer from within an x64 install only.

Good detective work DesertJerry.

Booted into Win7 Ultimate w/SP1 32bit

Performed same test as above - results verified - Autopatcher started and all Visual C++ in blue - so, again, not installing the AMD/ATI version is recommended.

I wondered what the point of Security Updates were (for VisualC) when older, perhaps insecure, versions are retained on a system. I understand that this is likely done to ensure compatability, yet MS's seemingly unorthodox methodology has me scratching my head. :/

indeed like I said before... I had like 12 versions of these damn things and it was driving me crazy. These "updates" should detect if there is a newer version already installed and NOT install.

TechDud, on 17 April 2012 - 02:24 AM, said:

I would not necessarily blame Microsoft. As my tests indicated AMD/ATI is also at fault for not designing their software updates to determine if a newer version, in this case, of Visual C++ is installed and should not be overwritten. My guess is there are others also at fault for doing the same thing and, in many cases, the user is unaware an 'older' version is being installed and overwriting a 'newer' version because a list of what is being installed is not provided to the user during installation/upgrading (at least AMD/ATI gives you an option in Custom install).

I note that akin to the ATI installers, the Broadcom WiFi drivers use an outdated version of Visual C++ 2005 (XP) and 2008 (Vista-7).
A copy of the installer is placed in %windir% on Windows XP.
I replaced both x86 & x64 Visual C++ 2005 runtimes on the XP package.

Here is the runtime output on XP_x86 (from bcm_vc80redist.log in %temp%):

Quote

I am unable to test on WinXP_x64. Please post any test results in the DriverPacks forum.

I have a link to this generic 'experimental' pack at the bottom of the following post. --> http://forum.driverp...id=47764#p47764
The installer seems to be clueless of the changes. Remember to backup your wifi settings first (PW, etc.)!
Heck, backup all important data for further safety.
Edited by TechDud, 29 April 2012 - 09:17 PM.

Well right now I don't think we need to worry about older libraries except to remove them if you see them. As far as it seems the newer libraries are completely compatible with the the software that uses the older ones. You only really need to worry about staying up do date. I am pretty sure that since all these different versions can be installed on top of each other that it defaults to the newest install of the libraries.

More Visual C++

Visual C++ Redist for Visual Studio 2012

Go here: http://www.microsoft...s.aspx?id=30679

Didn't I already update the script with the 2012's? ohh right... I updated it and added it to the test list because I have not installed them to get the detections... will do so now.

Derp forgot these only work on Vista and up. Something I lack. If someone has these and can give me the registry detection strings I can update the apm's and make them official.
Edited by ViroMan, 31 August 2012 - 06:28 AM.

Installed Microsoft Visual C++ 2012 Runtimes on Vista x86 and this is what I managed to find in the registry

Install Source
C:\ProgramData\Package Cache\{FDB30193-FDA0-3DAA-ACCA-A75EEFE53607}v11.0.50727\packages\vcRuntimeAdditional_x86\

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FDB30193-FDA0-3DAA-ACCA-A75EEFE53607}
KeyName=DisplayVersion
KeyValue=11.0.50727


Uninstall
"MsiExec.exe /X{FDB30193-FDA0-3DAA-ACCA-A75EEFE53607}"
Edited by Whatacrock, 31 August 2012 - 08:03 AM.

It seem that ViroMan has forgotten to post so will do on his behalf...we have the detections for VC++ 2012 x86 but are in need of someone to provide the detections for the x64 version.So if you have VC++ 2012 x64 install please your detection findings here and then the VC++ release can be completed and added to the main list.

Sorry if I jumped onto your toes VM, as you are busy with the upgrade of APUP V1.

Whatacrock, on 28 September 2012 - 06:02 AM, said:

Will see what I can do - have XP x64 and Win7 64 installed - hopefully tomorrow (Saturday). OOps - correction - VC++2012 not compatible with XP - only Vista or later.

Now I know it will be tomorrow.
Edited by DesertJerry, 28 September 2012 - 10:03 PM.

Win7 Ultimate 32bit w/SP1

HKCR\Installer\Products\2B7A37F2E05E6A93A9CBFE984E6CE263
ProductName: Microsoft Visual C++ 2012 Minimum Runtime x86 - 11.0.50727
Version (Decimal): 184600103

HKCR\Installer\Products\39103BDF0ADFAAD3CAAC7AE5FE5E6370
ProductName: Microsoft Visual C++ 2012 Additional Runtime x86 - 11.0.50727
Version (Decimal): 184600103

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{22154f09-719a-4619-bb71-5b3356999fbf}
DisplayName: Microsoft Visual C++ 2012 Redistributable x86 - 11.0.50727.1
DisplayVersion: 11.0.50727.1

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2F73A7B2-E50E-39A6-9ABC-EF89E4C62E36}
DisplayName: Microsoft Visual C++ 2012 Minimum Runtime x86 - 11.0.50727
DisplayVersion: 11.0.50727

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FDB30193-FDA0-3DAA-ACCA-A75EEFE53607}
DisplayName: Microsoft Visual C++ 2012 Additional Runtime x86 - 11.0.50727
DisplayVersion: 11.0.50727

Win7 Ultimate 64bit w/SP1

HKCR\Installer\Products\2B7A37F2E05E6A93A9CBFE984E6CE263
ProductName: Microsoft Visual C++ 2012 Minimum Runtime x86 - 11.0.50727
Version (Decimal): 184600103

HKCR\Installer\Products\39103BDF0ADFAAD3CAAC7AE5FE5E6370
ProductName: Microsoft Visual C++ 2012 Additional Runtime x86 - 11.0.50727
Version (Decimal): 184600103

HKCR\Installer\Products\B8CF35CA81EEC9F3B9950639D7B081C2
ProductName: Microsoft Visual C++ 2012 Additional Runtime x64 - 11.0.50727
Version (Decimal): 184600103

HKCR\Installer\Products\BCA1BC2A2A49AB231AE5D70813F95798
ProductName: Microsoft Visual C++ 2012 Minimum Runtime x64 - 11.0.50727
Version (Decimal): 184600103

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A2CB1ACB-94A2-32BA-A15E-7D80319F7589}
DisplayName: Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.50727
DisplayVersion: 11.0.50727

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC53FC8B-EE18-3F9C-9B59-60937D0B182C}
DisplayName: Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.50727
DisplayVersion: 11.0.50727

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{15134cb0-b767-4960-a911-f2d16ae54797}
DisplayName: Microsoft Visual C++ 2012 Redistributable x64 - 11.0.50727.1
DisplayVersion: 11.0.50727.1

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{22154f09-719a-4619-bb71-5b3356999fbf}
DisplayName: Microsoft Visual C++ 2012 Redistributable x86 - 11.0.50727.1
DisplayVersion: 11.0.50727.1

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{2F73A7B2-E50E-39A6-9ABC-EF89E4C62E36}
DisplayName: Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.50727
DisplayVersion: 11.0.50727

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{FDB30193-FDA0-3DAA-ACCA-A75EEFE53607}
DisplayName: Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.50727
DisplayVersion: 11.0.50727

Should be everything you need.
Edited by DesertJerry, 29 September 2012 - 10:14 PM.