I was having a similar problem. The compiled EXE would always begin by asking me to browse for dependencies. The solution was to rename the main VI, i.e. move it to an unrestricted destination on my C drive. So I think the problem was caused by the main VI being saved inside the driver folder at C:\Program Files (x86)\National Instruments\LabVIEW 2018\instr.lib
How to ensure lvlibs and their VIs really end up inside the executable
in Application Builder, Installers and code distribution
Posted
I was having a similar problem. The compiled EXE would always begin by asking me to browse for dependencies. The solution was to rename the main VI, i.e. move it to an unrestricted destination on my C drive. So I think the problem was caused by the main VI being saved inside the driver folder at C:\Program Files (x86)\National Instruments\LabVIEW 2018\instr.lib