Actually, my answer was not complete.
The launch condition search verifies the minimum version of IIS dictated by the version of the two files. In conclusion, if you select IIS 5 as the launch condition for example, Advanced Installer will automatically add a search for the "w3wp.exe" file on the target machine. In this case, if the found version of the file is lower or the file doesn't exist, your package won't be launched.
Can you please make sure the versions of the .EXE files you copied are higher or equal than the launch condition you have set in your test package?
Also, if you are testing on a 64-bit machine you should add the files in the SysWoW64 folder as the search is always performed in the 32-bit folder.
As a generic observation and as you said yourself, since the launch condition works well on several computers, needless to say is that the one machine is the cause of this issue.
All the best,