How to Check and Combine Windows Autopilot CSV Exports

Start with original device exports

Keep the source files unchanged. If someone edited an export in a spreadsheet, retain that version separately and obtain the original device-generated file where possible. Work in a controlled local folder with a clear naming convention, then select the files in a known order. The findings identify inputs by file number, so keep the displayed file list available while reviewing the report.

Resolve uncertainty before combining

Do not choose between duplicate device records simply because one appears first. Investigate where both records came from and whether they describe the same device. When the checker cannot establish a safe character encoding, obtain a known original rather than blindly converting the bytes. A plausible hash string is not evidence that the device data is genuine.

The tool intentionally separates file problems from registration problems. A missing identifier is something you can investigate in the source. A device already associated with a tenant requires account-side investigation. A platform incident is outside the scope of CSV repair. Keep the exact registration error with your operational notes.

Separate diagnostic reports and import batches

A diagnostic report documents review findings; a combined batch contains device identifiers intended for import. Store each appropriately and inspect the import file in a plain-text editor. Do not replace hardware data with demonstration values. Use your approved registration process and check the actual account result. If the file changes during review, run the check again before using the combined output.

References

Use the linked specifications and product documentation to check behavior in your own environment.