If you have a project where a VI is used on multiple targets, and contains conditional disable structures that vary between the targets (loading Vis that are not compatible with all targets for example) - you may see application build previews fail until you open the affected VIs on the relevant target just to get LabVIEW to update the conditional disable structure.
The actual build is smart enough to do this, but the preview function is not. This has the funny side effect that installer builds can fail when the relevant application builds suceed; because the installer will run a preview on the application builds even though they are already successfully built, and then fail because the preview will fail.
Now, I'm sure the installer build's use of the preview has its good reasons so I will not suggest to remove that, but rather suggest that the issue is resolved by making the preview functionality smarter; If (and only if) it runs into trouble when generating the preview, it should do the same as what the actual application build is now able to do; load the troublesome VI - and see if the issue is easy to resolve on the fly.
Any idea that has not received any kudos within a year after posting will be automatically declined.