New LabVIEW 2025 Q3 VIs in the Lossy Stream-str library of Channel Instances conflict with my company's IT policy

[brnbs]

Hi, I just upgraded from LabVIEW 2025 Q1 to Q3, and I can't get LabVIEW to reload the Lossy Stream-str library into the LabVIEW Data\..\ChannelInstances folder.  This seems to be tied to my company's IT policy for the KeepLossyStreamLogicClassInMemory.vi.  Is there any way to get a similar Channel Instance library without the new VIs of Q3?

 

[RTSLVU]

Sounds to me like you need to have a long talk with your IT department as this is basically a "false positive" in whatever antivirus or security software they are using.

[brnbs · Accepted solution]

I couldn't get any resolution from IT.  I was able to change all of my Lossy Stream VI references to the LabVIEW 2024 library, which worked just fine.  My project still comes up with an error because it tries to rebuild the class objects each time LabVIEW 2025 Q3 loads, but at least it runs and compiles with the references pointing to the LabVIEW 2024 version.

[Kyle97330]

Are you sure that this has to do with your IT policy specifically for one VI, or is it a policy specifically due to your IT policy on files in your "My documents" folder?

My company decided that all users should have their "My documents" folder added to their OneDrive sync, whether or not they want it to be, and this has the odd effect that it means LabVIEW channel instances that get stored there also get synced, whether or not that's helpful or desired.

It's not actively caused a problem yet for me, but if this is part of or related to the problem, you may be able to get around it by making LabVIEW store your files elsewhere.  Find the Tools menu, click Options, find the "Paths" option, and change "Default Data Directory" to your choice of alternate location.  It will rebuild the channels one more time the next time it loads, but after giving them a new home that is potentially free of IT meddling it may work without coming up with errors or the like each time.