I encountered the same problem with LabVIEW 2017 64, running under Windows 7 64, just today.
Actual Windows Manager, a windows management tool from Actual Tools, caused the fault.
I am running the latest version of this utility, 8.11.1.
The solution is very simple: exclude LabVIEW generated windows from Actual Manager actions.
There is an exclude page in the setup, which allows the user to exclude windows generated from any program.
Since any version of LabVIEW is called 'LabVIEW.exe', and Actual Windows Manager allows you to define the program that generates the excluded window by its name simply, without specifying the path, the exclusion works for all the LabVIEW versions I installed on my PC (2015 to 2017, 32 and 64 bits).
In Windows XP the problem didn't arise from LabVIEW 7 up to LabVIEW 2015 32.
Actual Windows Manager has also advanced multiple monitor functions, but disabling them didn't solve the problem with LabVIEW (I specify this because I saw that other people had similar problems with UltraMonitor, which I never used).
By the way, I also use TeamViewer latest version (12.0.82216), but it didn't give me any problem with LabVIEW.
I hope that this may be helpful for other people that could have the same problem, because being obliged to pick subVIs and controls by drag and drop is really a time (and patience) consuming workaround.
Luigi B.
