You can’t attach logs here. can you paste the contents of the transaction log?
Just on note,
1) Many times i have seen weird things, where the transaction logs and job run status shows failed but the actual deployment went correctly.
2) In DEPOT, the permission to access the BL Package from GUI might deny
3) Review the permissions of the file in /apps/nsh/storage to make sure everything is fine. (UID should be same for all app servers)
I think this is nor related to permissions on the depot object or the apps/nsh/storgae
Rather, it looks like some of patches are returning exit code 1, which is treated as failure.
e.g this one Windows6.0-2008-SP2-KB971486-x64.msu, task 7 is returning as exit code1.
If this 2008, this can happen due to the local user mapped for this deployment.
This is a long shot but I tried to deploy a msu but it failed because Windows Update service was not running. After restarting Windows Update it worked. This was Win 2008 64-bit. However, in my case I could clearly see a message in the log file that a required service didn't run which I can't see in yours.
Iirc some patches required the Application Layer Gateway or Application Experience service to be running.