VC2008MSMs x86 will not install

[u87]

Hello,

Am trying to install labview 2015 on a Windows 7 SP1 64bit computer.  Always get the following error message:

The "NI VC2008MSMx x86" installation has failed with the follwoing error:

Error 1935. An error occurred during the installation of assembly component {A56F98C7-0365-395D-8CA0-58F15463809}. HRESULT:0x8007371B
 

I can ignore this error but LabVIEW will not launch when the install completes.

Things that have been tried:

Running setup as administrator.

Doing a force install from the command prompt.

Installing the failing component before running setup.  Interestingly, x64 version installs but x86 does not.

Installing both 64bit and 32bit versions of LabVIEW.

Completely removing Symantec virus protection software.

Turning off Windows Firewall

Completely removing update software(from my company) and turning Windows update off.

Installing the latest version of NETframework

This error box just refuses to go away.

Computer is a new machine brought up specifically for this purpose.  Next thing to try might be a complete reinstall of Windows without anit-virus software.

Any ideas?

[Sam_Sharp]

Did you see these links/articles, they seem related to your issue? Do they help at all?

http://digital.ni.com/public.nsf/allkb/29A5562A9647DC49862579BE001D7195

http://forums.ni.com/t5/LabVIEW/Installation-error-w-VC2008MSMSs-x86-x64/td-p/1728286

[u87]

Thanks for your help, but looks like a fresh install of Windows 7 solved the problem.

It helped to decode the error a bit.  Generally speaking, a 1935 error means something went wrong with trying to put something in the GAC(global assembly cache) directory.  But there could be many reasons for that.  I found out from the Wiki page on HRESULT that this was a fatal Win32 error with error code 371B.  Google'd "win32 error codes" and was brought to the Microsoft website with a list of error codes and explanations.  371B means there was a SXS transaction error because some transaction components missing.  And one possible reasoon for this could be missing files(caused by an update that didn't go right or some other type of corruption in the files), which led me to speculate that something was wrong with Windows.    I do recall one of the automatic updates(a piece of software from my company, not the updater that comes with WIndows) saying it could not complete, perhaps because it was blocked by the NI installer.