I have an extensive set of CMD scripts for an automation suite.
In the console using CMD.exeeverything is working fine. After installing the update for Windows Creator, when PowerShell becomes the new default Windows shell using the Explorer menu options, my scripts are interrupted randomly. I cannot provide any meaningful code for playback for two main reasons:
- Missing obvious error; my automated scripts just hang in the end
- The stop does not even occur in the same place every time
I can tell you that the package is highly dependent on exit codes using findstr.exeand type.
I know that macros such as Windows macros, for example, %Var%are incompatible, but I assumed that since the only call I made was in the file .bat, the behavior .batwould be the only thing I needed to worry about.
If this is not the case, should my starter .batstart direct instance execution CMD.exewith my parameters? If so, what is the best way to do this, PowerShell-friendly?
source
share