Windows Scripting

WshShell.Run drops the child's exit code unless you call it with parentheses

A Windows box running about thirty unattended jobs reported success through three months of failures, because each exit code had to survive a VBScript launcher and a .cmd shim before the scheduler ever saw it.