Useful Windows command-prompt checks for support

Know which shell you are using

Batch scripts run in cmd.exe, not PowerShell or Bash. Save the downloaded file with a .bat extension and review it before running. Environment fields should contain ordinary paths, never a pasted command or a password.

Start with read-only checks

Record OS and network details for the affected device. Time-service queries can explain authentication problems caused by clock drift. Recovery-environment status is useful before maintenance, but a registered recovery image is not proof that a backup can be restored.

Handle failure explicitly

Inspect command exit codes and stop when a required query fails. Some diagnostics require administrator rights; obtain authorisation rather than automatically elevating. Keep the diagnostic output private until you have removed account names, addresses and internal network details.

Related tasks in the library

Two designated scripts per desk are included with a free account. Other scripts are preview listings while membership is coming soon.

• Check the Windows command processor version
• Inspect the Windows time-service source and status
• Check Windows Recovery Environment registration

Reference documentation

• ver documentation
• w32tm documentation
• reagentc documentation

Written by Tradescore Labs. These are diagnostic starting points, not a guarantee of compatibility or a replacement for your change-control process.