From: jj4public@gmail.com   
      
   On Thu, 15 Jul 2021 17:22:05 -0700 (PDT), Peter wrote:   
   >> I was updating a batch file I wrote to backup one of my PCs. It kept   
   >> crashing at a certain point. ...   
   [snip]   
   >>   
   >> Possible clue: this happens on only one of my PCs. It¢s a new one I   
   >> built about two weeks ago. All else seems to be normal with it. Windows   
   >> 10 Pro 64bit.   
   >>   
   >> Thanks!   
   >   
   > Thank you to those who replied!  Let me clarify a couple of things. 1)   
   > The counter is not the problem.  It's working fine.  2) The problem is   
   > caused by the bottom line shown above.  The batch file terminates when it   
   > hits that line.  If I change it from "wait-Z" to "wait-ZZ" there's no   
   > problem.  I hope this clarifies the issue.   
      
   By "crash", do you meant the batch file (i.e. ends the batch file and   
   returns to command prompt), or the whole CMD.EXE program (i.e. ends the CMD   
   process and closes the CMD window)?   
      
   Can you clarify that, in that one PC, the batch file is run using Windows'   
   own CMD.EXE, instead of other - including a "CMD.EXE" which is not in the   
   Windows' system directory?   
      
   If it's indeed run using Windows' own CMD.EXE, based on the weird batch file   
   behaviour/interpretation, and the clue that only one PC is affected, I could   
   only guess that the cause is either bugged CMD.EXE (e.g. from bad Windows   
   Hotfix), tampered CMD.EXE (e.g. modified by third party software, or virus),   
   or third party software interference (which includes malware).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)