Export of Device Link Timed Out: Device Prep USB Fix

You’re at the Windows Autopilot menu in OOBE, you pick Export device information, and the device returns:

Export of device link information timed out. Please try again.

The network looks fine. The Autopilot menu opened. Intune is waiting for a CSV. The failure is on the USB stick, not in the tenant.

Microsoft’s Device Preparation troubleshooting FAQ lists this exact message and names the cause: the USB drive is formatted as FAT32, or it contains both FAT32 and NTFS partitions. The fix is a separate USB drive with a single NTFS partition. I have not reproduced the timeout on a live device for this article. The steps and wording below come from the Microsoft Learn pages linked inline.

Key takeaways

• The timeout string is a Device Prep device association export failure in OOBE. It is separate from Intune enrollment HRESULTs and from ESP failures.
• Microsoft’s documented cause is the USB file system: FAT32, or a drive that has both FAT32 and NTFS partitions.
• Use a separate USB with one NTFS partition, then run Export device information again.
• The Device Prep tutorial recommends NTFS for this export before you hit the error.
• After a clean export, upload the CSV under Devices > Enrollment > Device association > Devices in Intune. One device per CSV.

Free and read-only: the Kit 1 beta scripts cover Autopilot and Device Preparation tenant and on-device checks. They do not format USB drives or validate the export path, so use them alongside the USB checks below.

Quick Fix checklist

1. Read the on-screen text. Confirm it is Export of device link information timed out. Please try again.
2. Remove the USB drive you used for the failed export.
3. On a working PC, create or pick a USB drive with a single partition formatted as NTFS. Do not leave a FAT32 partition on the same stick.
4. Boot the target device to OOBE and stop at the region selection page. Do not finish OOBE.
5. Press the Windows key five times quickly to open the Autopilot menu.
6. Insert the NTFS USB, select Export device information, wait for the CSV, then remove the USB.
7. Copy the CSV to a machine that can reach the Intune admin center and upload it under Device association.

What the error means

Device association is an optional Windows Autopilot device preparation feature. It binds a physical device to your tenant before enrollment by writing a tenant affinity marker into UEFI, and it unlocks OOBE customizations and device naming that only associated devices get. The first device-side step is exporting device information from OOBE so an admin can pre-associate the device in Intune.

The timeout message appears during that export. Microsoft does not map it to an enrollment error code, a TPM attestation failure, or an ESP phase. If you start by re-creating the Device Preparation policy or chasing ESP logs, you are in the wrong place.

Microsoft’s Device Preparation troubleshooting FAQ states the export might fail with:

Export of device link information timed out. Please try again.

The same entry continues:

This issue can occur when the USB drive is formatted as FAT32 or contains both FAT32 and NTFS partitions. Use a separate USB drive that contains a single partition formatted with the NTFS file system, and then try the export again.

The Device Preparation tutorial for device association adds the same guidance up front: “We recommend using a USB drive formatted with the NTFS file system.”

Why the obvious diagnosis can be wrong

The Autopilot menu and the word “timed out” push people toward network or service problems. Device Prep also has other OOBE failures that look adjacent: the experience never launches and ESP shows instead, apps report Skipped, or the device group will not save. Those are separate Microsoft entries with different fixes (registration precedence, app assignment, Intune Provisioning Client ownership). None of them is the documented cause for this export timeout.

The Autopilot menu’s Scan QR code option is a common detour. Microsoft says Intune currently supports uploading only the CSV from Export device information. The QR path is for a custom app that calls Microsoft Graph. Scanning a QR code will not give you the CSV Intune’s Import CSV page expects.

My recommendation: treat the first hit of this message as a media problem. Prove the USB layout, then retry the export once. Only after a clean NTFS export still fails should you look at OOBE state, hardware, or support.

Evidence: prove the USB layout

On the PC you use to prepare the stick (not the OOBE device), check the file system before you walk back to the build station.

# Read-only. Lists removable volumes and their file systems.
Get-Volume | Where-Object DriveType -eq 'Removable' |
  Select-Object DriveLetter, FileSystem, FileSystemLabel, Size, SizeRemaining |
  Format-Table -AutoSize

What you want:

I have not run this against a failed export. The pass/fail table is how I read Microsoft’s FAT32 and “both FAT32 and NTFS” wording. If Get-Volume is unclear, open Disk Management (diskmgmt.msc) and confirm the removable disk shows a single NTFS volume.

To rebuild a stick cleanly on a technician PC (this does erase the USB drive):

1. Back up anything you need from the stick.
2. In Disk Management, delete the existing volumes on that removable disk.
3. Create one new simple volume, format it as NTFS, assign a drive letter.
4. Eject, then use that stick only for the Device Prep export.

Do not format the OOBE device’s internal disk. Only the USB media used for Export device information.

Verified fix: export again, then pre-associate

After the USB is a single NTFS volume, follow Microsoft’s export path:

1. Power on the device and boot into OOBE. Stop at the region selection page.
2. Press the Windows key five times quickly. The Autopilot menu opens with Scan QR code and Export device information.
3. Insert the NTFS USB.
4. Select Export device information. Wait until the device information file is saved to the USB.
5. Remove the USB and copy the CSV to a computer that can sign in to the Microsoft Intune admin center.
6. In Intune: Devices > Enrollment > Device association > Devices > Add.
7. Browse to the CSV, continue, optionally assign a Device Preparation policy, review, then Add.

Microsoft notes that only one device per CSV is allowed at this time. Upload a separate CSV for each device.

Association state should show Pre-associated. Association itself completes when the device connects to a network in OOBE, or when a technician triggers it from the Autopilot menu after the pre-associate step. Microsoft describes a successful on-device result as Association complete.

Existing devices past OOBE

If the device already left OOBE, you cannot open the Autopilot menu. Microsoft’s tutorial says to collect Autopilot diagnostic logs and retrieve the DeviceLink CSV from those diagnostics instead. One documented command-line option is:

MdmDiagnosticsTool.exe -area Autopilot -cab C:\Diagnostics\Autopilot.cab

That path is for devices that are already past OOBE. It is not Microsoft’s documented remediations for the OOBE export timeout string. Use it when you need a DeviceLink CSV without the Autopilot menu, not as a substitute for fixing a FAT32 stick in OOBE.

What not to waste time on

• Rebuilding the Device Preparation policy or the Entra device group because of this message. Microsoft’s entry for the timeout names only the USB layout.
• Chasing ESP or IME logs. Device association export happens before enrollment finishes, and Device Prep does not use ESP the way classic Autopilot does.
• Relying on Scan QR code to feed Intune’s Import CSV flow. Microsoft says Intune supports the CSV from Export device information.
• Retrying the same FAT32 or mixed-partition stick. The FAQ’s fix is a different USB layout, not another click on the same media.
• Confusing this with Device Prep “never launches” cases where ESP appears. That branch means a classic Autopilot profile is in play; see Autopilot Device Preparation not running? ESP shows instead.

Prevention checklist

• Stock technician kits with a dedicated NTFS USB labeled for Device Prep export only.
• Keep vendor recovery or dual-partition sticks out of the association workflow.
• In the build runbook, put “confirm NTFS, single partition” before “press Windows key five times.”
• After upload, confirm Pre-associated in Device association before you send the device back through OOBE for association and enrollment.
• If personal enrollment is blocked in Intune, remember Microsoft’s rule: configure corporate identifiers or device association for each device. Associated devices are marked corporate-owned automatically, so you do not need both for the same device.

How I put this together

• Sources: Microsoft Learn only, retrieved 2026-11-06. Each load-bearing claim links the page it came from.
• Commands: Get-Volume is standard PowerShell inventory. MdmDiagnosticsTool.exe -area Autopilot comes from the Device Prep association tutorial. I have not run either against a device that showed the timeout.
• Opinions: where I recommend treating the first failure as a media problem, the text says so. Nothing here is a measured result from a real tenant.

Related Device Prep reading: security group membership failures, local administrator settings skipped, and the broader Device Preparation failures guide. For classic Autopilot ESP timeouts after association is done, use the ESP Triage Checklist.

Get the Deployment Doctor

Kit 1 founding presale is open: $39 (regular $49). The Autopilot + Device Prep Deployment Doctor checks your tenant, read-only, for the config that breaks ESP and Device Preparation. You pay now and get the files by Tuesday, December 1, 2026, sooner if they’re ready. Full refund any time before delivery, then 14 days after delivery. The founding price runs until Friday, December 4, 11:59 PM MT.

Want to look first? The free, read-only beta scripts are on GitHub: autopilot-deployment-doctor-beta. Its README says they haven’t been run against a live tenant.

FAQ

What does “Export of device link information timed out” mean?

It is the OOBE error Windows shows when Export device information fails during Windows Autopilot device association. Microsoft documents the cause as a USB drive formatted as FAT32 or a USB that contains both FAT32 and NTFS partitions.

Does this mean Device Preparation or Intune enrollment failed?

Not by itself. The message is about exporting the device link file to USB so you can pre-associate the device in Intune. Enrollment and the Device Preparation apps or scripts come after association and sign-in.

Why does Microsoft want NTFS instead of FAT32?

Microsoft does not publish a low-level file-system reason on the troubleshooting page. It states the failure condition (FAT32 or mixed FAT32 and NTFS partitions) and the remediations (a separate single-partition NTFS USB). The Device Prep tutorial also recommends NTFS for the export.

Can I use the QR code option instead of the CSV export?

Microsoft says the Autopilot menu includes Scan QR code and Export device information, and that Intune currently supports uploading only the CSV created by Export device information. The QR option is described for a custom app that calls Microsoft Graph.

The device is already past OOBE. How do I get the DeviceLink CSV?

Microsoft’s tutorial says to collect Autopilot diagnostic logs (Settings export, MdmDiagnosticsTool.exe -area Autopilot, or Intune Collect diagnostics) and retrieve the DeviceLink CSV from those diagnostics. That is a different path from fixing the OOBE USB timeout.

Sources

All retrieved 2026-11-06.

• Windows Autopilot device preparation troubleshooting FAQ, Microsoft Learn: exact timeout message; FAT32 and mixed-partition cause; single NTFS USB fix.
• Windows Autopilot device preparation user-driven Microsoft Entra join - Step 7 - Associate devices, Microsoft Learn: NTFS recommendation; Windows key five times; Export device information; Import CSV; one device per CSV; existing-device DeviceLink path; MdmDiagnosticsTool.exe -area Autopilot.
• Overview of Windows Autopilot device association, Microsoft Learn: what device association is; pre-associate / associate / remove; OOBE customization benefits; corporate-owned marking.
• Collect MDM logs, Microsoft Learn: mdmdiagnosticstool.exe usage for Autopilot-related diagnostics.
• Get-Volume, Microsoft Learn: PowerShell cmdlet used in the USB inventory example.