Formatters & Code

Windows Autopilot CSV Validator

Check Windows Autopilot hardware-hash CSV files locally. Inspect headers, encoding and duplicates, then combine eligible exports into device batches.

Device exports & upload profile

Up to 20 files, 10 MB each, 50 MB total. Original three-column exports and optional Group Tag / Assigned User columns are checked in order.

File errors, duplicate devices or account/service problems?

File findings identify local formatting and identifier problems. Repeated identifiers may represent the same device, but this checker cannot see any tenant registration. If the file passes and registration fails, inspect the exact Intune error, tenant ownership, permissions and Microsoft service health. An outage is not repaired by changing the CSV.

Results

What the result means

Select or drop your original device CSV exports. The checker reads their bytes locally, checks the header layout and record structure, and compares serial numbers and hardware hashes across the selected files. Review the findings using file numbers and CSV record numbers. Eligible exports can be combined into batches of up to 500 devices, preserving identifiers and emitting plain ASCII without a Unicode marker. No record is silently deduplicated or repaired. Download the diagnostic report separately from import batches. A clean file cannot establish hash authenticity, tenant ownership, account permissions or service health; investigate those in Intune if registration still fails.

Related tools

Guides

Advertisement

Questions

Can this fix an Intune or Microsoft service outage?

No. It checks local files only. A registration failure may require investigation of tenant ownership, permissions or service health.

Can I merge several original hardware-hash exports?

Yes, if the selected files pass blocking checks. The tool preserves values and creates import batches of at most 500 device records. Duplicates need manual resolution.

Does a valid Base64 hash prove the device is valid?

No. The checker recognises encoding syntax, not the internal hardware record or its authenticity. Registration remains an account-side operation.

Need help with a tool or found a bug?

Report an issue directly to engineering. No accounts required — all client data remains private on your device.

Report an Issue →