Windows MDM enrollments are failing with 0x8018000a error

[AdamBaali]

Fleet version: 4.73.1

---

💥 Actual behavior

Many Windows MDM enrollments fail during migration from a previous MDM (Previous MDM was Endpoint Central) Orbit logs repeat RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a) and the MDM server URL remains blank on the host vitals card. Devices are Fleet enrolled, but not MDM enabled, so Windows profiles do not deploy. Screenshots for 8 affected devices are attached.

🧑‍💻 Steps to reproduce

1. Enroll a Windows test host into a non Fleet MDM.
2. In Fleet, enable Windows MDM and check Automatically migrate hosts connected to another MDM solution.
3. Enroll the host to Fleet. The host appears in Fleet, but host vitals show a blank MDM server URL and Windows profiles do not apply.

🕯️ More info (optional)

• Regression or new variant related to original ticket Many Windows MDM enrollments are failing with 0x8018000a error #29042
• Temporary mitigation used at customer: registry cleanup script from this comment Many Windows MDM enrollments are failing with 0x8018000a error #29042 (comment)
• Customer provided CSV shows 2666 occurrences of 0x8018000a between 2025-10-04 14:53:39 and 2025-10-08 14:16:39 on one host
• Currently observed on 8 devices and growing

Sample log rows

2025-10-08 14:16:39  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed
2025-10-08 14:16:09  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed
2025-10-08 14:15:39  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed
2025-10-08 14:15:09  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed
2025-10-08 14:14:39  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed
2025-10-08 14:14:09  host=218300640P  error=RegisterDeviceWithManagement failed: The operation completed successfully. (0x8018000a - 2149056522)  message=calling RegisterDeviceWithManagement to enroll Windows device failed

[JordanMontgomery]

I will follow up with this customer later to see if we can get any additional information.

Theory is that MDM enroll is working initially however we aren't detecting it, as was happening with previous bug

[JordanMontgomery]

Slack thread with customer: https://fleetdm.slack.com/archives/C061ZA91Y1J/p1759932720184349

I was wrong based on most recent discussions. MDM enrollment is not working or at least not permanently - the old MDM is sticking around. The registry keys associated with the old MDM have a relatively new mtime of ~Tuesday of this week on at least 2 machines which makes me think perhaps it is unenrolling fleet or blocking the enrollment? Hard to say. At any rate the error - that enrollment failed because already MDM enrolled - is the same as before because ultimately the system is MDM enrolled just not in Fleet. I am unfamiliar with the source MDM being used here but suspect there could be some conflicting setting disallowing the removal or forcing re-enrollment somehow.

[JordanMontgomery]

Customer-preston has indicated that after unenrolling their hosts in the old MDM they were able to successfully enroll in fleet. Closing this out

[fleet-release]

Windows enrolls, fails,
A cloud city's lights flicker.
Fix brings steady glow.