Solution
This issue is a known bug.
The root cause occurs when the “Modify project library file after removing unused members” option is selected in the VI Options.

When this option is enabled, LabVIEW internally updates the parent–child class relationships stored in the .lvlib file.
During this update process, LabVIEW may encounter stale class objects—objects that were replaced by newer versions but had not yet been fully cleared from memory.
Accessing these stale objects can lead to a crash during the build process, which ultimately causes the TestStand Deployment Utility to fail with:
Error -19034: TestStand Deployment Utility Unable to Execute Files
It will be fixed in later LabVIEW release.