I had already tried that approach, but adding the batch file as a Post Build Step gave me odd results.
I appears as though instead of running the batch file, CW 10.1 opened the batch file and tried to process the commands it'self, which isn't what I was after.
My batch file was called test.bat and I added it as a Post Build Step. This is the Error I received:
"C:\Windows\System32\ExtractsS19.exe" is not recognized as an internal or external command.
This is the first line in my batch file.
Note: The batch file works correctly if I run it manually.