A Stranger Case of Windows .Net Error 0xE0434352

This posts's original problem was isolated and corrected. It was due to a missing DLL in the installation directory. Apparently, the missing DLL caused the application not to run from the Windows scheduler when it was scheduled to run.

Until I patched the installation directory with the missing DLL I got the .Net Error 0xE0434352 when the application tried to run as scheduled. But why did the application run successfully on-demand from within the scheduler (right-click run), and if I just ran it from the desktop?