Script Error when click on Find Example in LabVIEW Help

[altenbach]

Great detective work. Maybe MS, not NI needs to fix this, maybe with another windows update..... 🙂

(The article mentions an update to scripting ...)

[Ben]

Additional note...

I do not see the problem running Windows 7...

and I only apply updates when forced to do so.

Ben

[altenbach]

Ben, are you fully updated? Billko above saw it in W7.

[Ben]

---

@altenbach wrote:

Ben, are you fully updated? Billko above saw it in W7.

---

No Sir!

I only apply updates when there is a reason to do so.

I have seen too many problems when I let updates happen.

Ben

[altenbach]

---

@Ben wrote:

---

@altenbach wrote:

Ben, are you fully updated? Billko above saw it in W7.

---

I have seen too many problems when I let updates happen.

---

... such as this one 😄

[altenbach]

---

@ToKa1971 wrote:

As suggested by @altenbach, windows update KB4462919 seems to be the problem: 

---

The only updates I see are: KB4464330, KB4465477. (Depends on what version of windows you are running (Fall, spring update, etc.))

Uninstalling KB4464330 did not fix the problem. Will try a few more things.

[RavensFan]

---

@ToKa1971 wrote:

As suggested by @altenbach, windows update KB4462919 seems to be the problem:

https://support.microsoft.com/en-us/help/4462919/windows-10-update-kb4462919

After removing this update from my Windows 10 computer LabVIEW help finally works.

---

I went and checked this out and saw I had the same problems.  I had a KB 4462918 in my windows update history.  When I removed that one, the problem went away.

The description for 4462918 seems similar to 4462919.

[yanyi]

Same problem here, except I don't have 4462918 or 4462919, time to roll back updates one by one....

[altenbach]

---

@yanyi wrote:

Same problem here, except I don't have 4462918 or 4462919, time to roll back updates one by one....

---

Yes, the exact KB depends on the W10 version you are running. I still hope that Microsoft can do a forward fix. they must be aware of it by now. Breaking a decade+ worth of an installed base of commercial software should force some priority to this. You'd think!

[Novgorod]

---

@Ben wrote:

I do not see the problem running Windows 7...

I can confirm the bug definitely happens on WIndows 7 (x64) with the latest updates.