01-09-2015 09:39 AM
Hi all,
I am trying to install a program by running its installer in a PC running on W7. At the very Part 1 of 97 into the installation I am getting the following error over and over:
"The NI VC2005MSMs x64 installation has failed with the following error: Error 1935. An error occured during the installation of assembly 'Microsoft.VC80.OpenMP, type='win32',version='8.0.50727.4053' publickey token='1fc8b3b9a1e1e3b', processorArchitecture='amd64' Please refer to Help and Support".........but there is no real help and support.
Anyway 1) I've verified that the TrustedInstaller exists in c:\Windows\serviciing 2) tried fsutil resource setautoreset true C:\ 3) there are no weird registries in the PC 4) ran as Admin. Tried everything suggested in the community forum on this topic.
Can anybody tell me what the issue is about by the type of error it shows?
Any ideas?
Solved! Go to Solution.
01-09-2015 11:16 AM
01-09-2015 11:27 AM
Hi Dennis,
I am trying it with an installer that I created from a LV project. Other than those you mentioned, I added NI Serial and NI VISA. I've tried installing it in another computer/laptop and it works fine, the installation goes to completion. It is with this brand new PC (a DELL Precision T7810 minitower to be precise) that would not allow the insllation completion with the error I mentioned. I do not think it is a LabVIEW (2009) issue, to me it an problem with the PC that I hope someone could have faced before when installing a custom LV program and got a quick way to resolve. I wonder if the anivirus could be causing this but it does not make too much sense as other computer allow installation.
Thanks for replying.
-j
01-09-2015 11:39 AM
01-09-2015 11:42 AM
Did that too..... Repaired, Uninstalled, installed....but nothing.
thanks for showing interest in this.
-j
01-12-2015
12:06 AM
- last edited on
07-25-2025
11:20 AM
by
Content Cleaner
Hello JoseRivero,
Have you tried this?
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kH3nSAE&l=en-US
There are another possible solutions, but I would like to start with this first.
Please keep me up to date, best regards.
01-12-2015 07:36 AM
Hi DavidPrrs,
Thanks for for pitching in.
The issue, now that it is resolved, dealt with a McAffee feature...DeepDefender, that had to be removed from the PC I am working on by the company's IT group. The company I work for take computers and format them with a corporate pc image, so it iturned out this image is somehow very restrictive (with W7).
Thanks you so much for you comments and suggestions.
-j
02-22-2016 03:31 PM
I had a same problem. The cause was windows update had updates pending. Reboot and upates install solved the problem.