d1774393@urhen.com

Hello, old topic, but I thing I found the issue. The task sequence execution engine starts the next installation before the current one is finished. The engine waits for an exit code from msiexec and starts the next installation right away, but in some cases msiexec is still doing stuff. You get this error in the TS status messages, but the actual application exit code received is 1618. That was it in my case at least. Hope this helps