Script Error when click on Find Example in LabVIEW Help

[Bob_Schor]

Bruno,

     LabVIEW underwent a significant change in 2017 (and LabVIEW 2017) with the introduction of the NI Package Manager, and the new LabVIEW NXG "Next Generation" release.  There have been several discussions of problems involving installations of LabVIEW versions that "cross" the 2016/2017 boundary.  Furthermore, I recently learned that NI seems to consider 5 years the largest "gap" in LabVIEW Versions that one should consider using.  That is, if you are using LabVIEW 2011, you "should not" install any LabVIEW version newer than 2011+5 or LabVIEW 2016.

Unfortunately, once you install LabVIEW 2017 or 2018, selective removal of just those versions will probably prove difficult.  The safest way forward involves a "fresh" install, meaning starting with a system without LabVIEW and installing the Versions you want to use, oldest first (as LabVIEW prevents installing an older version "on top of" a newer one).

Bob Schor

[billko]

---

@Bob_Schor wrote:

Bruno,

     LabVIEW underwent a significant change in 2017 (and LabVIEW 2017) with the introduction of the NI Package Manager, and the new LabVIEW NXG "Next Generation" release.  There have been several discussions of problems involving installations of LabVIEW versions that "cross" the 2016/2017 boundary.  Furthermore, I recently learned that NI seems to consider 5 years the largest "gap" in LabVIEW Versions that one should consider using.  That is, if you are using LabVIEW 2011, you "should not" install any LabVIEW version newer than 2011+5 or LabVIEW 2016.

Unfortunately, once you install LabVIEW 2017 or 2018, selective removal of just those versions will probably prove difficult.  The safest way forward involves a "fresh" install, meaning starting with a system without LabVIEW and installing the Versions you want to use, oldest first (as LabVIEW prevents installing an older version "on top of" a newer one).

Bob Schor

---

Isn't that the same gap used for driver compatibility?  Maybe that's the reason?

[ToKa1971]

I´ve actually got two different computers / LabView / Windows versions which both experience the same LabView Help Script Error after Windows Update.

LabView 2011 Home on Windows 7 (work license)

LabView 2014 Home on Windows 10 (student edition for experimenting at home)

[_Bryan]

I have 2017 and 2018 on a Win 7 x64 box that has the script issue.  I also have 2011 installed on a win 7 x64 and win 7 x32 machines with the issue.

But I did find a XP Pro virtual machine running 2012 that works fine..He He

[RavensFan]

Probably because MS is no longer deploying updates for WinXP.  But still are for Win 7.  The update that breaks the help dialog is a relatively new update.

I believe your observations help confirm that.

[_Bryan]

---

@RavensFan wrote:

Probably because MS is no longer deploying updates for WinXP.  But still are for Win 7.  The update that breaks the help dialog is a relatively new update.

---

That is why I added "He He" at the end.  I guess I should have just used

I also wanted to subscribe for when there is a fix or more information.

[BoKnows]

As I don't see this posted here, I wanted to point out Microsoft released updates recently.  The following list of fixes should correct the scripting behavior we're seeing.

Windows 10, version 1703: KB4480959

Windows 10, version 1709: KB4480967

Windows 10, version 1803: KB4480976

For Windows 7 there is an “Preview of Monthly Rollup” KB4480955 from January 17, 2019

[TeraTech]

@BoKnows Thanks for posting!  I'm the original poster - I just ran MS updates and it appears to have fixed the problem! I am running Windows 10 and LabVIEW 2017 17.0f2 (32 bit)

[_Bryan]

---

@BoKnows wrote:

As I don't see this posted here, I wanted to point out Microsoft released updates recently.  The following list of fixes should correct the scripting behavior we're seeing.

Windows 10, version 1703: KB4480959

Windows 10, version 1709: KB4480967

Windows 10, version 1803: KB4480976

For Windows 7 there is an “Preview of Monthly Rollup” KB4480955 from January 17, 2019

---

I am running Win 10 version 1809 and it is still broken.  I tried 2017 and 2018.

[TeraTech]

Sorry to hear that. I unmarked your post as the solution.

More details on my install:

Windows 10 Pro for Workstations

Version 1803

Build 17134.556

Listing the KBs for to allow searches: KB4480976, KB4100347, KB4477137, KB4465663, KB4456655, KB4230204, KB4343669