Solution
This is a known issue specific to LabVIEW 2022 Q3 and 2023. The problem arises when the source code files are unable to correctly handle instance VIs that are in pseudopaths.
Follow the instructions below to bypass this behavior:
- Copy the _NISVFA file from C:\Program Files\NI\LVAddons\nisvt\1\vi.lib\addons and place it in the C:\Program Files\National Instruments\LabVIEW 2023\vi.lib\addons directory.
- Relink the dependencies.
- Build the project.
Once these steps are completed, LabVIEW will be able to successfully detect the files and build the application.