Daily Intune News
Aboutmerill.net
Windows Autopilot
Device enrollment

Manually Register Devices with Windows Autopilot | Microsoft Learn

30 October 2026Doc update+78 / −78 lines

In brief

The page was updated with revised wording for hardware-hash collection, CSV registration, prerequisites, permissions, and related links. Metadata and documentation links were also refreshed.

What Intune admins need to know

Administrators can use the updated guidance; no required configuration change or deadline is stated.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diffView on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Manually Register Devices with Windows Autopilot | Microsoft Learn

Within an organization, Windows Autopilot device registration requiredrequires the following actions:

  1. Manually collecting the hardware identity of devices, known as hardware hashes.hashes.
  2. Uploading the hardware hash information in a comma-separated-comma separated values (CSV) file.

Capturing the hardware hash for manual registration requires booting the device into Windows. For this reason, this process is primarily for testing and evaluation scenarios.

UpYou can manually register up to 500 devices can be manually registered viaby using a CSV file uploaded through the portal. Before proceedingyou proceed with additionalmore devices, check that the previous CSV file batch is successfully registered. If transferring devicesTo transfer device hashes from one tenant to another tenant, see Support tip: How to transfer Windows Autopilot devices between tenants for additional guidance.

Device owners can only register their devices withby using a hardware hash. Other methods (PKID, tuple) are available through OEMs or CSP partners.partners provide other methods, such as PKID and tuple.

This article provides step-by-step guidance for manual registration. For more information about registration, see:

Requirements

Required permissions

Device enrollment requires Intune Administrator or Policy and Profile Manager permissions. AYou can also create a custom Windows Autopilot device manager role can also be created by using role-based access control (RBAC). Windows Autopilot device management only requires only that you enable all permissions under Enrollment programs are enabled,, except for the four token management options.

Note

In both Intune Administrator and role-based access control methods, the administrative user also requiresneeds consent to use the Microsoft Intune PowerShell and Microsoft Graph PowerShell enterprise applications.

Collect the hardware hash

TheUse the following methods are available to harvestcollect a hardware hash from existing devices:

  • UsingUse Microsoft Configuration Manager.
  • UsingUse Windows PowerShell.
  • During the out-of-box experience (OOBE) by using, use the Diagnostics Page (Windows 11 only).
  • Directly on the device usingdevice, use the Access work or school pane in the Settings app.

For a description of each method, select the link for the method.

Note

HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\UserOOBE

To ensure that OOBE hasndidn't restartedrestart too many times, change this registry key value to 1.

Configuration Manager

Microsoft Configuration Manager automatically collects the hardware hashes for existing Windows devices. For more information, see Gather information from Configuration Manager for Windows Autopilot. TheYou can extract the hash information can be extracted from Configuration Manager into a CSV file.

PowerShell

TheYou can access the hardware hash for an existing device is available through Windows Management Instrumentation (WMI). TheUse the PowerShell script Get-WindowsAutopilotInfo.ps1 can be used to get a device's hardware hash and serial number. The serial number is useful forhelps you quickly seeingidentify which device the hardware hash belongs to.

To use the Get-WindowsAutopilotInfo.ps1 script, download it needs to be downloaded and then run it on a device by using either of the following methods:

  • Save the hardware hash locally on a devicesdevice as a CSV file - thefile. The Get-WindowsAutopilotInfo.ps1 script saves the hardware hash locally on the device as a CSV file. ThisUse this method is normally used on devices that already underwentwent through Windows Setup and OOBE.
  • Directly upload the hardware hash to a mobile device management (MDM) service such as Intune - theIntune. The Get-WindowsAutopilotInfo.ps1 script directly uploads the hardware hash to the MDM service. This method is normally used on devices that are undergoing Windows Setup and OOBE.

Note

The Get-WindowsAutopilotInfo script used in this section was updated in July of 2023 to use the Microsoft Graph PowerShell modules instead of the deprecated AzureAD Graph PowerShell modules. Make sure toEnsure you use the latest version of the script. The Microsoft Graph PowerShell modules might require approval of additional permissions in Microsoft Entra ID when you first use the modules are first used.modules. For more information, see AzureAD and Important: Azure AD Graph Retirement and PowerShell Module Deprecation.

Save the hardware hash locally on a device as a CSV file

SavingSave the hardware hash locally on a device as a CSV file is normally done onfor devices that already underwentwent through Windows Setup and OOBE. To capture and save the hardware hash locally on a device:

  1. Sign in to the device.

  2. On the device, open an elevated Windows PowerShell prompt.

    On first run, the Get-WindowsAutopilotInfo.ps1 script prompts to approve the required app registration permissions.

The commands save the hardware hash is saved locally on the device in the directory C:\HWID with the filename AutopilotHWID.csv. TheYou can then use the CSV file can then be used to import the device into an MDM service such as Intune.

Instead of running the PowerShell commands directly on devices, theyyou can instead be run them remotely on devices as long as the remote device meets the following requirements are met on the remote device:requirements:

  • WMI permissions are in place.
  • WMI is accessible through Windows Firewall on the remote device.

Directly upload the hardware hash to an MDM service

Directly uploading the hardware hash to an MDM serviceservice, such as Microsoft IntuneIntune, can be done on any device, but itdevice. It's especially useful for a device currently undergoing Windows Setup and OOBE. To directly upload the hardware hash for a device:

  1. On a device that is:

    • Currently undergoing Windows Setup and OOBE:

      1. At the sign-in prompt after OOBE starts, open a command prompt window with the keystrokeby using Shift+F10.

      2. In the command promptCommand Prompt window that opens, start PowerShell by running the following command:

        powershell.exe

    Get-WindowsAutopilotInfo -Online

    
If prompted to do so,prompted, agree to install **NuGet** from the **PSGallery**.

  2. When the last command of Get-WindowsAutopilotInfo -Online runs, a Microsoft Entra ID sign-on prompt is displayed. Sign in with an account that is at least an Intune Administrator.

    Note

    On first run, the Get-WindowsAutopilotInfo.ps1 script prompts to approve the required app registration permissions.

  3. After the sign-in is successful, the device hash uploads automatically.

  4. Verify that the hardware hash uploaded successfully and the device is showing as a registered Windows Autopilot device using the instructions in the sectiondevice. See Verify the hardware hash uploaded.

  5. For devices undergoing Windows Setup and OOBE, restart the device. The device should pick up the Windows Autopilot profile and OOBE should run through the Windows Autopilot provisioning process.

    Note

To confirm the hardware hash for the device was uploaded into Intune and that the device shows as a Windows Autopilot device:

  1. Sign in to the Microsoft Intune admin center.
  2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.
  3. In the Devices | Overview screen, under By platform, select Windows.
  4. In the Windows | Windows devices screen, under Device onboarding, select Enrollment.
  5. In the Windows | Windows enrollment screen, under Windows Autopilot, select Devices.
  6. In the Windows Autopilot devices screen, in the toolbar, select Sync in the toolbar..
  7. Wait for the sync to finish. The sync might take several minutes.
  8. After the sync completes and the device appears in the device list in the Windows Autopilot devices screen in Intune, the device is ready for a Windows Autopilot deployment as long as a Windows Autopilot profile is assigned to the device.

Note

Microsoft recommends registering devices through Microsoft Intune viaby using a 4K hardware hash only for testing or other limited scenarios for the following reasons:

  • Availability of free and inexpensive accounts in Intune that lack robust vetting.
  • 4K hardware hashes contain sensitive information that only device owners should maintain.

Diagnostics page hash export

To export a hardware hash by using the Windows Autopilot Diagnostics Page, the device must be running Windows 11.

Windows Autopilot Diagnostics are available in OOBE.

During OOBE, enter the keystrokeselect CTRL + SHIFT + D to bring upopen the Diagnostics Page. From this page, you can export logs can be exported to a thumban external drive. The logs include a CSV file with the hardware hash.

Desktop hash export

Sign in to the device where you want to export the hardware hash needs to be exported. Once signedhash. After you sign in to the device, open the Accounts > Access work or school pane in the Settings app by selecting the following link:

Or

Or

  1. Right-click on the Start menu and select Settings.
  2. In Settings, select Accountsin the left hand pane.pane, select Accounts.
  3. In the Accounts page, select Access work or school.

OnceAfter you open the Access work or school pane is open in the Settings app, export the log files:

  • Windows 11: In the Export your management log files section, select the Export button..
  • Windows 10: Select the Export your management log files link.

The logs include a CSV file with the hardware hash. LogThe process exports log files are exported to the C:\Users\Public\Documents\MDMDiagnostics directory.

For more information, see Collect MDM logs.

Ensure that the CSV file meets requirements

Device information in theThe hardware hashes CSV file should include:include the following device information:

Item Required Optional
Group tag ❌ ✅
Assigned user ❌ ✅

TheUse the following methods to collect the required items of serial number and hardware can be collected intohash for an individual device CSV file using the following methods:file:

  • The Get-WindowsAutopilotInfo script documented in the Save the hardware hash locally on a device as a CSV file section.
  • The Desktop hash export documented in the Desktop hash export section.

TheYou can use the information from the individual device CSV files can be then used to create a CSV file with multiple devices to import multiple devices at once into an MDM service such as Intune.

The multiple devices CSV file can have up to 500 rows of devices. The header and line format must have the following format:

,,,,


Keep these other requirements in mind for the CSV file in mind:file:

- Extra columns arenDon't allowed.include extra columns.
- Quotation marks arenDon't allowed.include quotation marks.
- OnlyUse only ANSI-format text files are allowed. Unicode isnfiles. Don't allowed.use Unicode.
- Headers are case-sensitive.

Important

Use a plain-text editor such as Notepad withto edit this CSV file. Don't use Microsoft Excel. Editing and saving the CSV file withby using Microsoft Excel doesn't generate a usable file for importing to Intune.

When you upload a CSV file is uploaded to assign a user, make sure toensure you assign a valid User Principal Names (UPNs)Name (UPN). If you upload an invalid UPN/UPN or incorrect username is uploaded,username, the device might be inaccessible until you remove the invalid assignment is removed.assignment.

During upload of a CSV file, Microsoft only validates that the only validation that Microsoft performs ondomain name in the `Assigned User` column is to check that the domain name is valid. Microsoft doesn't performvalidate individual UPN validationUPNs to ensure that an existing or correct user is being assigned.

## Add devices

OnceAfter you capture the hardware hashes are captured in a CSV file, Windows Autopilot devices can be added by importing the file. To import the file by using Intune:

1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. In the **Home** screen, select **Devices** in the left hand pane.pane, select **Devices**.
3. In the **Devices | Overview** screen, under **By platform**, select **Windows**.
4. In the **Windows | Windows devices** screen, under **Device onboarding**, select **Enrollment**.
5. In the **Windows | Windows enrollment** screen, under **Windows Autopilot**, select **Devices**.
6. In the **Windows Autopilot devices** screen, in the toolbar, select **Import** in the toolbar..
7. In the **Add Autopilot devices** screen:

    1. browseGo to the CSV file that lists the devices that needyou want to be added.add.
    2. Select **Import** to start importing the device information. Importing can take several minutes.
8. After the import is complete,finishes, in the **Windows Autopilot devices** screen, select **Sync** in the toolbar.

    A message says that the synchronization is in progress. The process might take a few minutes to complete, depending on how many devices are being synchronized.
9. Select **Refresh** in the toolbar until the new devices appear.

## Edit Windows Autopilot device attributes

After you upload a Windows Autopilot device is uploaded,device, you can edit certain attributes of the device can be edited:device:

1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. In the **Home** screen, select **Devices** in the left hand pane.pane, select **Devices**.
3. In the **Devices | Overview** screen, under **By platform**, select **Windows**.
4. In the **Windows | Windows devices** screen, under **Device onboarding**, select **Enrollment**.
5. In the **Windows | Windows enrollment** screen, under **Windows Autopilot**, select **Devices**.
6. In the **Windows Autopilot devices** screen, select the device that needsyou want to be edited.edit.
7. In the pane on the right of the screen, edit the following items can be edited:items:

    - Device name.name
    - Group tag.tag
    - Username (ifUsername, if a user is assigned).assigned
8. Select **Save**.

Note

DeviceConfigure device names can be configured for all devicesdevices, but are ignored in Hybrid Microsoft Entra deployments.deployments ignore them. The device name still comes from the domain join profile for Hybrid Microsoft Entra devices.

## Delete Windows Autopilot devices

You can delete Windows Autopilot devices that aren't enrolled in Intune can be deleted:Intune:

1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. In the **Home** screen, select **Devices** in the left hand pane.pane, select **Devices**.
3. In the **Devices | Overview** screen, under **By platform**, select **Windows**.
4. In the **Windows | Windows devices** screen, under **Device onboarding**, select **Enrollment**.
5. In the **Windows | Windows enrollment** screen, under **Windows Autopilot**, select **Devices**.
6. In the **Windows Autopilot devices** screen,, select the devices that need deletion,to delete, and then select **Delete** in the toolbar. The deletion process can take a few minutes to complete.

Completely removingTo completely remove a device from a tenant requirestenant, you need to delete the device records in Intune, Microsoft Entra ID, and Windows Autopilot to all be deleted. TheseAutopilot. You can perform these deletions can all be done from IntuneIntune, but you need to be done in the followingfollow this order. For more information, see [Deregister a device](registration-overview#deregister-a-device).

## Troubleshooting registration failures

1. **StorageError**: This error is a generic error that can occur for various reasons. Most of the time ittime, you can's not possible tot determine the exact cause of the error until further investigation is done.you investigate further. If you encounter this error is encountered, the best course of action is toerror, try again later. If the issue persists, contact support.
2. **ZtdDeviceAssignedToAnotherTenant**: This error occurs when the uploaded hardware hash matches a device that is's already registered to a different tenant. If this error occurs, search for the serial number corresponding to the duplicate in the CSV file. Then, search for the serial number in the **Windows Autopilot devices** pane in Intune. If the device is already registered, don't import it again.
3. **ZtdDeviceAlreadyAssigned**: This error occurs when the uploaded hardware hash matches a device that is's already registered to the tenant. If this error occurs, search for the serial number corresponding to the duplicate in the CSV file. Then, search for the serial number in the **Windows Autopilot devices** pane in Intune. If the device is already registered, don't import it again. If the device isn't registered, ityou can be importedimport it again.
4. **ZtdDeviceDuplicated**: This error occurs when there are duplicate hardware hashes in the CSV file. Only one of the duplicates is processed, and the others result in this error. If this error occurs, look for the other duplicates of the same device to see what the actual result was. If you find a duplicate that was successfully processed is found,processed, you can remove the duplicate row from the CSV file can be removed.file.
5. **InvalidZtdHardwareHash**: This error occurs when one or more fields in the hardware hash are invalid or empty. BothYou need to include both the manufacturer and serial number information need to be included.information. If theyyou don're not, the devicet include them, you can't be registeredregister the device for Windows Autopilot. To check the serial number and manufacturer information, open a PowerShell prompt and run the following command:

    ```powershell
    Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer, SerialNumber
Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…