Verify your Deployment Doctor files

Check that the scripts you downloaded are exactly the ones published.

• Scripts v1.4.0 ship in Kit 1 v1.4.4 (paid kit download)
• Scripts v1.2.3 ship in Kit 2 v1.3.3 (win32-deployment-doctor-beta, commit 0d54783)

Kit 2's paid download ships the same files as its beta repo. Kit 1 v1.4.4 is listed from the paid release itself, including the two zip files. Script versions are numbered separately from kit versions; each kit's README Versions table and CHANGELOG are linked below.

How to verify in Windows PowerShell

1. Open Windows PowerShell and change to the folder that holds the file (for example cd .\scripts).
2. Compute the file's hash:

   Get-FileHash .\Invoke-DeviceDiagnostic.ps1 -Algorithm SHA256

3. Compare the Hash value with the SHA256 listed below for that file and kit. Hashes here are in uppercase, matching what Get-FileHash prints (PowerShell's -eq is not case-sensitive anyway). Any difference means do not run the file; download it again.

One-line compare for Kit 1's device diagnostic (prints True when the file matches):

(Get-FileHash .\Invoke-DeviceDiagnostic.ps1 -Algorithm SHA256).Hash -eq '1266F01DDB07FFF0B739581F98176BA31761253F0CAEC6735ABCD96A5B9CAA01'

SHA256 checksums

Paths are relative to each kit repository's root (Kit 1: the unzipped kit). Both kits have files with the same names, so use the list for your kit. Click a hash to select all of it, then copy.