Installation: The case of Microsoft Visual C++ 2010 and the 1603 error

I recently had a case in which an Autodesk product was failing because of the following 1603 error:

2012/1/10:13:12:47 USERNAME Laptop Installing Microsoft Visual C++ 2010 Redistributable (x86): C:\Autodesk\Autodesk_Quanitiy_Takeoff_2012_English_Win_32Bit\3rdParty\x86\VCRedist\2010\vcredist_x86.exe /q2012/1/10:13:12:51 USERNAME Laptop Install Microsoft Visual C++ 2010 Redistributable (x86) Failed Installation aborted, Result=1603

To assist in troubleshooting this error, we had to setup a verbose log as noted in this Technial Solution:

http://usa.autodesk.com/getdoc/id=TS1070015

There was also a log file in the %temp% folder:

Microsoft Visual C++ 2010 x86 Redistributable Setup_20120110_131250217

Using these results, we found out that the Microsoft Visual C++ 2010 on the target computer was upgraded to a higher version by the HP Support Assistant to:

 Microsoft Visual C++ 2010 x86/x64 Redistributable - 10.1.40219

The default Microsoft Visual C++ 2010 version is:

 Microsoft Visual C++ 2010 x86/x64 Redistributable - 10.0.30319

The solution was to uninstall the Microsoft C++ 2010 x64 and x86 Redistributable and then install the Autodesk product.

Before doing this, we also setup a Windows restore point.  Please check out this site for details:

http://windows.microsoft.com/en-US/windows7/Create-a-restore-point

http://windows.microsoft.com/en-US/windows7/products/features/system-restore

Thanks to John Peterson for confirming that this tip works.

Additional reference post:

http://upandready.typepad.com/up_and_ready/2012/01/autodesk-suites-building-design-suite-ultimate-will-not-install-at-autodesk-quantity-takeoff.html

Epilogue

For Design Review 2012, you can also download this hotfix:

http://usa.autodesk.com/getdoc/id=DL17570140

Thanks to Alison Gangler for this additional note.

Comments

[Darxis]

Thanks, worked!

[Brad]

It was the C++ Redist. x86 version on 64 bit windows for me. Custom build PC, no HP support assistant. Something else or Windows Update must have upgraded it.

Nonetheless, your fix was accurate. Vault can't deal with newer versions of some items apparently. Uninstall the offending resource, and let Vault re-install the older version.

[Jean]

Thanks. Worked too.