Batch File Automated a Clean-Up Job, Then Fouled Itself by Deleting the Wrong Directory
The Register, Monday, August 24th, 2026
A maintenance batch script meant to defrag Exchange deleted critical Windows NT 4 system files instead.
An IT professional wrote a batch file to automate Exchange server maintenance by stopping services, compacting the database with eseutil, and deleting temporary files.
It passed testing, won management approval, and was scheduled for Friday nights. Unfortunately the script contained DEL *.* without specifying a directory, so when run from System32 it wiped that directory and crippled the Windows NT 4 server. The administrator spent most of the weekend rebuilding and restoring - though he did collect double time for the emergency work.