Here are the three most likely causes:
1) Your package includes a change to the PATH variable. On certain packages this is solved by removing the change to PATH, and adding an AppPath for the executables that includes the changes made to PATH. This only affects some packages with
Path changes and we don't know why.
2) You are using the 5.1 RTM Sequencer. Try it with the MDOP 2017 fall update.
3) A very unlikely possibility: You are sequencing on 32-bit OS and testing on x64 OS and the primary exe is of type "AnyCPU".
Tim
Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "PowerShell with App-V 5 (5.1 Edition)", "The Client Book (4.x)" and "OSD Reference Book" (http://www.tmurgent.com/Books )