Solution
This is a known issue in LabVIEW 2016 and has been addressed in the f1 patch. Install the LabVIEW 2016 f1 patch to fix this known issue (the 64-bit f1 patch can be found here).
Optionally, you can update to a newer LabVIEW 2016 patch, which will include all previous patch fixes, like the f1 patch. You can find the LabVIEW 2016 f5 patch here (64-bit).