It seems only the older MSI's use LaunchConditions, it's getting more common to use CustomActions I've noticed - probably to try and prevent people like us from doing exactly this - ha! In this case with the NOD v4.1 Beta MSI, it's the CA "InstSuppPrepareInstall" which uses InstSupp.dll [inside the MSI] to do somesuch nonsense to, well, prepair the system I guess.
I spent about an hour figuring this one out, and was even trying to hack the InstSupp.dll, but after some random experimentation I found the way to get around it with just Orca.Under the table "InstallUISequence", drop the row "InstSuppPrepareInstall". Thats it!
EDIT: Also had to do this as I found it would fail install...Under the table "InstallUISequence", drop the row "InstSuppApplyUIChanges". NOW thats it!
Hope it works for you, it does for me =D Peace!!!