Showing results for 
Search instead for 
Did you mean: 

LabView 2017 upgrade leads to loss of CVI Shared Run-Time Engine 2013 SP2

As a user of very early versions of LabView I am always reluctant to upgrade to the latest version of LabView.  I recently upgraded from LabView 2016 to 2017 and NXG only to find that I could not successfully build my application.  A number of components were unavailable which were linked to the "NI LabWindows/CVI Shared Run-Time Engine 2013 SP2" collection.  It seems that these were replaced by the "LabView / CVI Shared Runtime 2017" components, but lacked the resources.  These being:

(1) ActiveX Container Support

(2) Real-Time Utility Support

(3) Visual C++ 2008 Redistributable

(4) Visual C++ 2010 Redistributable

(5) Visual C++ 2008 Runtime

(6) Meas Graphics Support

Is there a reason as to why this is being implemented during the upgrade?  I've had to rollback the installation and I am using LabView 2016 to enable me to continue with my work.  Has anyone else encountered this issue?

0 Kudos
Message 1 of 1