Manually Register Devices with Autopilot in Windows 11 or 10
Windows Autopilot is a cloud-based deployment and device management feature from Microsoft that helps organizations configure and prepare Windows devices automatically. Instead of manually setting up every PC one by one, IT administrators can use Autopilot to preconfigure devices so employees can start working quickly with minimal setup.
Normally, device manufacturers or hardware vendors register devices with Autopilot before shipping them to businesses. However, there are many situations where you may need to manually register a Windows device yourself. For example, you may already own existing laptops, desktop PCs, or test machines that were not originally added to Autopilot.
The manual registration process mainly involves collecting the device’s hardware hash and uploading it to the Microsoft Intune Admin Center. Once the registration is complete, the device becomes part of your organization’s Autopilot deployment system.
In this guide, you will learn exactly how to manually register devices with Autopilot in Windows 11 and Windows 10.
What You Need Before Starting?
Before you begin the process, there are a few important requirements you should understand.
You must have a Windows 11 or Windows 10 PC that you want to register with Autopilot.
You also need an active Microsoft Intune or Microsoft 365 Business Premium subscription with administrative permissions.
The Windows device should have an active internet connection because the hardware hash needs to be uploaded to Microsoft services online.
You must sign in using an account that has Administrator privileges on the local PC.
Finally, make sure PowerShell is available on the device because the registration process depends heavily on PowerShell commands.
How to Manually Register Devices with Autopilot in Windows 11 or 10?
To manually register a Windows device with Autopilot, you must first install and run a PowerShell script that collects the device’s hardware hash. After generating the CSV file, upload it to the Microsoft Intune Admin Center under the Windows Autopilot devices section. Once the upload finishes, assign an Autopilot deployment profile to complete the registration process.
Step 1: Open Windows PowerShell as Administrator
The first thing you need to do is launch Windows PowerShell with administrator access. This is necessary because standard user permissions are not enough to collect the device hardware information required for Autopilot.
In Windows 11, click the Start Menu and type PowerShell in the search bar. When you see Windows PowerShell appear in the search results, right-click it and choose Run as administrator.
In Windows 10, the process is very similar. Open the Start Menu, search for PowerShell, then right-click the application and select Run as administrator.
When the User Account Control window appears, click Yes to allow administrator access.
You should now see a blue PowerShell window on your screen. This means you are ready to continue with the next steps.
If you accidentally opened PowerShell without administrator access, close the window and reopen it properly because some commands will fail otherwise.
Step 2: Install the Windows Autopilot Script
Microsoft provides a special PowerShell script called Get-WindowsAutopilotInfo. This script collects the device hardware hash and exports it into a CSV file.
Since many new users may not have this script installed already, you first need to install it from the PowerShell Gallery.
Inside the PowerShell window, type the following command carefully and press Enter:
Install-Script -Name Get-WindowsAutopilotInfo
After running the command, PowerShell may ask whether you trust the repository source. Type:
Y
Then press Enter to continue.
The installation may take a minute or two, depending on your internet speed. Once finished, the Autopilot script becomes available on your computer.
If you receive an error related to execution policies, run this command first:
Set-ExecutionPolicy RemoteSigned
Then choose Y and try the installation again.
Many beginners get worried when PowerShell displays warning messages during installation. In most cases, these are normal security prompts from Windows.
Step 3: Generate the Device Hardware Hash CSV File
Now comes the most important part of the process. You must generate the hardware hash file that uniquely identifies the device to Microsoft Autopilot.
Inside the same PowerShell window, enter the following command:
Get-WindowsAutopilotInfo.ps1 -OutputFile C:\AutopilotHWID.csv
Press Enter after typing the command.
This script scans your computer and collects several hardware identifiers. It then creates a CSV file called:
AutopilotHWID.csv
The file will be saved directly on the C:\ drive.
Depending on your device speed, the process may take a few moments. Do not close PowerShell while the script is running.
Once complete, you can open File Explorer and navigate to the C:\ drive to verify that the CSV file exists.
This CSV file is extremely important because it contains the hardware hash information required for Autopilot registration.
If you plan to register multiple devices, repeat the same process separately on each device.
Step 4: Sign In to Microsoft Intune Admin Center
After generating the hardware hash file, the next step is uploading it to Microsoft Intune.
Open your preferred web browser, such as Google Chrome or Microsoft Edge, and visit the official Microsoft Intune Admin Center.
Sign in using your Microsoft administrator account.
Once logged in, you will see the Intune dashboard interface. This area allows IT administrators to manage devices, security policies, applications, and Autopilot configurations.
If you are using Intune for the first time, the dashboard may look complicated initially. However, you only need to access a few specific sections for Autopilot registration.
Step 5: Navigate to the Windows Autopilot Devices Section
Inside the Intune Admin Center, locate the left side navigation menu.
- Click Devices first.
- After that, select Windows.
- Now choose Windows enrollment.
Under the enrollment section, click Devices inside the Windows Autopilot category.
You should now reach the main Autopilot devices page. This area displays all devices currently registered with Autopilot in your organization.
If your organization is new to Autopilot, this list may appear empty.
Do not worry, because you are about to add your first manually registered device.
Step 6: Upload the Hardware Hash CSV File
On the Windows Autopilot devices page, locate and click the Import button near the top of the screen.
A new upload window will appear. Click the folder or browse option and navigate to the CSV file you generated earlier:
C:\AutopilotHWID.csv
Select the file and upload it.
After selecting the file, click Import to start the registration process.
Microsoft Intune now processes the uploaded hardware information and associates the device with your organization.
This process may take several minutes, depending on Microsoft cloud synchronization.
Do not close the browser immediately after uploading because the import status may still be processing in the background.
Sometimes the status changes from:
Pending
to:
Completed
after a short wait.
Refresh the page occasionally if you do not see updates immediately.
Step 7: Verify the Device Registration Status
After the upload finishes, you should confirm that the device was successfully registered.
On the Autopilot devices page, locate the imported device in the list.
You may see information such as:
- Device Serial Number
- Manufacturer
- Model
- Assigned User
- Deployment Profile Status
If the device appears correctly, the registration process was successful.
Sometimes synchronization delays can occur, especially in large environments. In such cases, wait a few more minutes and refresh the page again.
If the device does not appear at all, double-check whether the CSV file was generated correctly and whether the upload completed without errors.
Step 8: Create or Assign an Autopilot Deployment Profile
Registering the device alone is not enough. You also need to assign an Autopilot Deployment Profile, so Windows knows how the device should be configured during setup.
Inside the Windows Autopilot section, click Deployment Profiles.
If your organization already has a profile, you can assign it directly to the device.
If not, create a new profile by selecting Create Profile.
You will typically choose settings such as:
- User Driven Mode
- Azure AD Join
- Skip Privacy Settings
- Automatically Configure Keyboard
- Allow Pre-Provisioning
These options help automate the Windows setup experience for users.
Once the profile is created, assign it to the registered device.
The profile assignment process may take a little time to synchronize with Microsoft services.
Reset the Device for Autopilot Enrollment
After registration and profile assignment, the device must go through the Windows Out of the Box Experience process to activate Autopilot properly.
If the device is already being used, you may need to reset it.
Open: Settings > System > Recovery, then choose: Reset this PC
Select the option to remove everything if the device is being prepared for a new employee or a clean deployment.
During the next startup, the device should automatically recognize the assigned Autopilot profile once connected to the internet.
Users will then see your organization’s branding and automated setup configuration during Windows setup.
Why Organizations Use Autopilot?
Many businesses use Windows Autopilot because it simplifies device deployment significantly.
Instead of manually configuring every laptop, organizations can automate:
- Device enrollment
- Security policy setup
- Application installation
- Company branding
- Azure AD joining
- User account configuration
This saves a huge amount of time for IT departments and improves consistency across company devices.
Autopilot is especially useful for remote workers because devices can be shipped directly to employees without requiring manual IT setup beforehand.
Tips & Cautions
Always verify that the device has a stable internet connection before starting the registration process.
Never edit the generated CSV file manually because incorrect formatting can cause import failures.
Use administrator permissions during every PowerShell step to avoid script execution errors.
If PowerShell blocks script execution, review your execution policy settings carefully.
Keep the hardware hash CSV file secure because it contains unique device identification information.
Some synchronization tasks inside Intune may take several minutes. Patience is important during the import and profile assignment stages.
Avoid resetting the device before confirming that the deployment profile has been assigned successfully.
If you manage many devices, consider automating uploads using Intune scripts or OEM registration services.
FAQs
Is Windows Autopilot available in Windows 11 and Windows 10?
Yes. Windows Autopilot works with both Windows 11 and Windows 10 devices that meet Microsoft’s supported requirements.
Do I need Microsoft Intune for Autopilot?
In most business environments, yes. Microsoft Intune is commonly used to manage Autopilot devices and deployment profiles.
What is a hardware hash in Autopilot?
A hardware hash is a unique identifier generated from the device hardware. Microsoft uses it to recognize and register devices inside Autopilot.
Can I manually register existing PCs with Autopilot?
Yes. Existing Windows PCs can be manually registered using the PowerShell hardware hash collection method explained in this guide.
Why is my Autopilot import stuck on pending?
This usually happens because Microsoft cloud synchronization is still processing the upload. Waiting a few more minutes often resolves the issue.
Is the internet required during Autopilot setup?
Yes. Internet connectivity is necessary so the device can communicate with Microsoft services and retrieve deployment configurations.
Can I register multiple devices at once?
Yes. IT administrators often collect hardware hashes from multiple devices and upload them together using a combined CSV file.
Does resetting the PC remove Autopilot registration?
No. The Autopilot registration remains associated with the device in Microsoft Intune unless it is manually removed by an administrator.
Summary
Manually registering devices with Windows Autopilot is an effective way to prepare existing Windows 11 and Windows 10 computers for automated deployment and management. The process mainly involves collecting the hardware hash using PowerShell, uploading the generated CSV file into Microsoft Intune, and assigning a deployment profile.
Although the process may seem technical at first, following each step carefully makes it manageable even for beginners. Once configured properly, Autopilot can save organizations significant time by automating Windows setup, security policies, and device enrollment tasks.
For businesses managing multiple PCs, learning how to manually register devices with Autopilot can greatly improve deployment efficiency and simplify long-term device management.