The BackgroundContainer scheduled task specifically attempts to start the BackgroundContainer.dll file. As far as I know, all other “The specified module could not be found” startup errors related to the Conduit malware are still being triggered by startup entries somewhere in the registry – so you’ll probably need to apply the Autoruns method recommended in quiertman7’s answer for that same thread. The virtue of quietman7’s method is that using the “file > find” feature should take you directly to the problematic entry, and if we eliminate the need for hunting and guesswork, that should also eliminate the possibility of a misidentification.