Hello, (In this example program 2 depends on successfull installation of program 1. Both programs are in the same package) I know that a Task Sequence doesn't automatically carry out installation of dependent programs. However I get the "Dependency Not Run" error even if run program 1 from an Install Software Task before running program 2 from another one. I've placed a sleep between the tasks and confirmed that the successinfo is written for the package before running program 2, under: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\System\.... I get the same error when chaining the programs using "Install Multiple Applications" and Base Variable method. I this a known issue?

SCCM is not smart enough to detect and run the dependent program, if we receive this error code, it means a task sequence Install Software Action step cannot be run because the step has a child program which has not been run before.Could you please check smsts.logPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thats what I wrote :)) The issue is that the same error occur even when running the dependant program before the main program.

Does anyone from Microsoft have any updated information on this problem? The issue occur both when using "Install single application" and "Install multiple applications". The Install Program Task fails with E_FAIL_DEPENDENCY_NOT_RUN even if I explicitly run the dependent upon program first.

is it possible that the program needs a restart before allowing you to continue with the next dependancy ? does the smsts.log file reveal anything ? wouldn't you be better off pulling the programs apart from the package and installing them as separate steps in the TS rather than chaining them (although i'm sure i've heard that it works..) cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks for answering. I found the problem... I had the "Always run this program first" set. That's actually the way I want to chain them so maybe i'll have to wrap the installations in a vbscript anyway.