Open KrypticChewie opened 3 years ago
Running the code with the actual command commented out works correctly. Perhaps USMTUtils is returning something other than 0 even though the log has a return of 0. It is possible something else is setting the error level after USMTUtils runs.
Seems the issue is really to do with how errorlevel is handled. If an error level is set to other than 0 it may not be changed back to 0 is a 0 is later returned.
When scanning the verification using USMTUtils does not display a correct message. It displays NoMessageSet indicating that the variable was not set when USMTUtils completed its scan. The scan does complete as the log for it shows.