10-13-2025 06:20 PM
I seem to have installed or uninstalled something and have broken my shortcut menu plugins. It appears that none of the VI's actually run when they're supposed to. I had a couple glitches a while back but apparently didn't notice that NONE of them were working until today.
If I remove them from the PopupMenus folder, the entries disappear (and reappear when I bring them back) so it's seeing the plugins folder, but it's not actually running anything when they're called. Also, it appears that most (but not all) of the LLB's in the "edit time panel and diagram" folder show up as Windows folders with the text ".llb" at the end, but using the LLB Manager to convert them to an actual LLB doesn't seem to fix things. Not sure if that's related.
Anyway, I can't seem to get any of the "Execute [plugin].vi" to run at all, as evidenced by no breakpoints triggering and no popups added will result in a popup window showing. I can't seem to figure out what's actually CALLING the plugins to see what's failing.
Any tips?
Solved! Go to Solution.
10-13-2025 07:00 PM
Have you tried using NI package manager to run a "repair" on the LabVIEW install in question?
Also, what version of LabVIEW?
10-14-2025 04:05 AM
Isn't there some caveat that those files must have debugging disabled or set to auto-run or some such?
10-14-2025 10:40 AM
Running 2023 q3. I haven't tried a repair yet but one's running now, thanks for the suggestion. I was hoping there was some "caller" VI that either logged things or would let me debug easier, but I'll see if a repair fixes it. Thanks for the idea.
@Yamaeda wrote:
Isn't there some caveat that those files must have debugging disabled or set to auto-run or some such?
I believe the "menu creator" ones need debugging disabled, but as I understand it the "Execute [stuff].vi" can have debugging enabled. If there's another requirement I'm not aware of it. I've never done a custom right click plugin myself. That said, I tried both with and without debugging but it didn't seem to make a difference.
As best as I can tell, the functions aren't getting called at all, so it's likely whatever is supposed to CALL those functions isn't running (or is throwing an error).
Fingers crossed the repair fixes things 🙂
10-14-2025 02:37 PM
Well, I got through the Repair process after a few hours, and it said it could repair everything.... except LabVIEW 2023 😞 I'm hoping I don't have to do a reinstall, because it takes forever...
Anyway, I did find this article:
Apparently, new plugins are supposed to just be folders, not actual LLB's, but it doesn't seem to matter too much which one they are. So, that was a bit of a red herring.
I'll keep digging...
10-22-2025 05:26 PM
Any news on this? I'm still on 21.0.1f2 for now but having the same problem. I have several plugins installed, and most (?) aren't working at all. Even something as simple as Create Constant on a color input doesn't do anything, and hasn't for a few months at least. No Change to Array, no Bundle or Unbundle shortcut, no Replace Comparison... I really miss these features! 😄
10-23-2025 10:50 AM
Nope. None of my right click plugins work. That's not to say none of my right click options work- they do- it's just anything installed as a "plugin" isn't running at all. I can't figure out what's supposed to be calling them, and I can't repair my installation (it throws an error), so I'm just gritting my teeth until I need to do a manual uninstall and reinstall of LabVIEW.
It's extremely obnoxious but isn't a full showstopper, so who knows when I'll find the time 🙂
10-23-2025 02:30 PM
Try replacing the following VI with the one I've attached here:
[LabVIEW 2023]\resource\plugins\PopupMenus\support\Call Popup PlugIn Execution VI.vi
Then mass compile the PopupMenus folder. Restart LabVIEW and see if the menu plugin Execute VIs start working again.
10-23-2025 03:41 PM
HOLY COW THANK YOU!
Although I didn't replace anything... that VI simply wasn't there! I have no idea how that would've been removed. My only guess is some plugin installer tried to replace it with something else and failed for some reason. I can't recall anything particularly weird plugin-wise that I've installed. Or maybe there was a glitch trying to update LabVIEW versions? Who knows.
Anyway, thanks a ton Darren! This also explains why, after looking through there, I couldn't seem to find any VI that actually called any plugins... because there wasn't one!