First time I've seen this occur. I'm using SCCM 2012 SP1 U2 + MDT 2012 U1 + UDI. I have 8 applications in SCCM that I am installing via the UDI. Each application has been tested and validated on its own via the Application Catalog.

I ran a few image deployments today and noticed 1 or 2 of the applications were failing to install. The TS completes successfully but the app isn't installed. I can see the package downloaded successfully under C:\Windows\ccmcache and I can manually run the installer without any issues.

The MSI logs reveal:

MSI (c) (CC:48) [14:38:57:276]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (CC:48) [14:39:00:286]: Failed to grab execution mutex. System error 258.
MSI (c) (CC:48) [14:39:00:286]: Cloaking enabled.
MSI (c) (CC:48) [14:39:00:286]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (CC:48) [14:39:00:286]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (CC:48) [14:39:00:286]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (CC:48) [14:39:00:286]: MainEngineThread is returning 1618

This seems to indicate another MSI process was still running, preventing the application from installing. I thought UDI handled process monitoring. Why would it be trying to execute another install if 1 is still in progress?

What does smsts.log tell? Any chance that there is something in your task sequence that starts an msi installation asynchronously (which could also be another msi)?

I didn't find anything in the smsts.log regarding these installs. These particular applications are being handled by MDT/UDI through dynamic variables.

In this case I simply added a restart prior to the application having trouble and it appears to have fixed the issue.

• Marked as answer by ImageGuy 15 hours 3 minutes ago