If an updater is run manually from the command prompt like so:
c:\Whatever\WhateverUpdater.exe /silentall -nofreqcheck
and encounters an error the upgrade program will rollback and cease to run, and then updater process stops running as well.
Running a windows scheduled task to do the same command when an error is encountered during the installation the upgrader will rollback and cease to run correctly, but the WhateverUpdater.exe process continues to run.
The any subsequent time the scheduled task runs it reports "Could not start" result code -536870873 / 0xE0000027
How should we address this?