Windows Autopilot: redeployment fails with 0x80180014 in self-deployment or pre-provisioning mode
Summary
Devices enrolled with Windows Autopilot self-deployment mode or pre-provisioning mode fail with error 0x80180014 when they are redeployed and run the Autopilot deployment again. Microsoft confirms the issue and documents two workarounds.
Symptoms
The Windows Autopilot deployment fails with error code 0x80180014 when a previously enrolled device is redeployed.
Affected
- Windows devices enrolled with Windows Autopilot self-deployment mode
- Windows devices enrolled with Windows Autopilot pre-provisioning mode
- Devices that are redeployed and rerun the Autopilot deployment
Workaround
- Delete the device record in Intune, then redeploy the device so that it reruns the Windows Autopilot deployment (see "Deregister a device").
- Alternatively, remove the device enrollment restriction for Windows (MDM) personally owned devices in Intune.
Fix
Not fixed yet. Microsoft documents only the workarounds.
Recommendation
Before reusing or redeploying a device in self-deployment or pre-provisioning mode, delete its old device record in Intune. Only remove the enrollment restriction for personally owned Windows devices if this fits your enrollment policy.
Sources
- Windows Autopilot: known issues Vendor · learn.microsoft.com
- Set enrollment restrictions in Microsoft Intune Vendor · learn.microsoft.com
Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 18:24.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.