Forum Discussion
Intune Enrollment Issues - Error `0x80180014`
Hello Community!
We've been occasionally getting this error with some of our machines when trying to manually enroll them in Intune:
Error `0x80180014` with the message "does not support this version of Windows"
From what I've seen, it typically happens to very specific devices.
We have our enrollment setup for Corporate only devices, and they have to have already been synced into Entra form our "on prem" AD. We have found that when removing that restriction, the devices can be enrolled as 'personal' devices.
We've made sure the devices are fully updated as well.
We've tried doing everything from scratch, including deleting the device from Intune, Entra, and AD before trying to re-enroll it.
Here is a dsregmcd output of one of the enrollment attempts:
H:\>dsregcmd /status
+----------------------------------------------------------------------+
| Device State |
+----------------------------------------------------------------------+
AzureAdJoined : YES
EnterpriseJoined : NO
DomainJoined : YES
DomainName : CLEARBROOK
Virtual Desktop : NOT SET
Device Name : CBROOK13289LP.clearbrook.org
+----------------------------------------------------------------------+
| Device Details |
+----------------------------------------------------------------------+
DeviceId : 1c9069dc-0079-4c49-b827-227e3a886c6b
Thumbprint : D1066B4BCBA9FBFD63F66190741B1BDD32C36C0F
DeviceCertificateValidity : [ 2026-07-24 19:46:23.000 UTC -- ]
KeyContainerId : e1d94bb2-b3f6-4e6c-93ce-319aeb6e219c
KeyProvider : Microsoft Platform Crypto Provider
TpmProtected : YES
DeviceAuthStatus : SUCCESS
+----------------------------------------------------------------------+
| Tenant Details |
+----------------------------------------------------------------------+
TenantName : CLEARBROOK
TenantId : f3c206ca-21c6-4c72-9ab6-76aa22775cd0
AuthCodeUrl : https://login.microsoftonline.com/f3c206ca-21c6-4c72-9ab6-76aa22775cd0/oauth2/authorize
AccessTokenUrl : https://login.microsoftonline.com/f3c206ca-21c6-4c72-9ab6-76aa22775cd0/oauth2/token
MdmUrl :
MdmTouUrl :
MdmComplianceUrl :
SettingsUrl :
JoinSrvVersion : 2.0
JoinSrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/device/
JoinSrvId : urn:ms-drs:enterpriseregistration.windows.net
KeySrvVersion : 1.0
KeySrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/key/
KeySrvId : urn:ms-drs:enterpriseregistration.windows.net
WebAuthNSrvVersion : 1.0
WebAuthNSrvUrl : https://enterpriseregistration.windows.net/webauthn/f3c206ca-21c6-4c72-9ab6-76aa22775cd0/
WebAuthNSrvId : urn:ms-drs:enterpriseregistration.windows.net
DeviceManagementSrvVer : 1.0
DeviceManagementSrvUrl : https://enterpriseregistration.windows.net/manage/f3c206ca-21c6-4c72-9ab6-76aa22775cd0/
DeviceManagementSrvId : urn:ms-drs:enterpriseregistration.windows.net
+----------------------------------------------------------------------+
| User State |
+----------------------------------------------------------------------+
NgcSet : NO
WorkplaceJoined : NO
WamDefaultSet : YES
WamDefaultAuthority : organizations
WamDefaultId : https://login.microsoft.com
WamDefaultGUID : {B16898C6-A148-4967-9171-64D755DA8520} (AzureAd)
+----------------------------------------------------------------------+
| SSO State |
+----------------------------------------------------------------------+
AzureAdPrt : YES
AzureAdPrtUpdateTime : 2026-07-24 20:19:05.000 UTC
AzureAdPrtExpiryTime : 2026-08-07 20:19:04.000 UTC
AzureAdPrtAuthority : https://login.microsoftonline.com/f3c206ca-21c6-4c72-9ab6-76aa22775cd0
EnterprisePrt : NO
EnterprisePrtAuthority :
OnPremTgt : NO
CloudTgt : YES
KerbTopLevelNames : .windows.net,.windows.net:1433,.windows.net:3342,.azure.net,.azure.net:1433,.azure.net:3342
+----------------------------------------------------------------------+
| Diagnostic Data |
+----------------------------------------------------------------------+
AadRecoveryEnabled : NO
Executing Account Name : CLEARBROOK\blopez1, email address removed for privacy reasons
KeySignTest : PASSED
DisplayNameUpdated : YES
OsVersionUpdated : YES
HostNameUpdated : YES
Last HostName Update : NONE
+----------------------------------------------------------------------+
| IE Proxy Config for Current User |
+----------------------------------------------------------------------+
Auto Detect Settings : YES
Auto-Configuration URL :
Proxy Server List :
Proxy Bypass List :
+----------------------------------------------------------------------+
| WinHttp Default Proxy Config |
+----------------------------------------------------------------------+
Access Type : DIRECT
+----------------------------------------------------------------------+
| Ngc Prerequisite Check |
+----------------------------------------------------------------------+
IsDeviceJoined : YES
IsUserAzureAD : YES
PolicyEnabled : NO
PostLogonEnabled : YES
DeviceEligible : YES
SessionIsNotRemote : YES
CertEnrollment : none
PreReqResult : WillNotProvision
1 Reply
The error aligns with your corporate-only enrollment restriction, not an unsupported Windows build. Manual enrollment through Settings, Company Portal, or “Add work account” is normally evaluated as personal unless Intune can identify the device as corporate. In Intune, first open Devices > Enrollment > Enrollment failures and confirm “Enrollment restriction not met.” Then either use a corporate enrollment path, such as GPO automatic MDM enrollment, co-management, or Windows Autopilot, or upload Windows corporate identifiers before enrollment. Windows identifiers must match manufacturer, model, and serial number and require a supported Windows 10 or Windows 11 build. Also verify that Windows enrollment is allowed, the user has an Intune license and is in the MDM user scope. Your dsregcmd output shows a healthy hybrid join, but the blank MdmUrl merits checking that scope. Stop deleting the Entra and AD objects; it does not change how the manual method is classified.
