Forum Discussion

josvds's avatar
josvds
Brass Contributor
Jul 18, 2023

Unknown Win32 Error code: 0x86000011

We are having a problem with one device inside a tenant of our customer. This device is fully updated to the latest version W11 22H2. We are trying to push changed to the firewall policy, but this device doesn't recieve them.

 

Inside the log Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin we see several errors:

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (DeviceStatus), Command Type: (Clear: first phase of Delete), CSP URI: (./Vendor/MSFT/DeviceStatus/Antispyware/Status), Result: (Unknown Win32 Error code: 0x86000011).

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (DeviceStatus), Command Type: (Clear: first phase of Delete), CSP URI: (./Vendor/MSFT/DeviceStatus/Antivirus/Status), Result: (Unknown Win32 Error code: 0x86000011).

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (DeviceStatus), Command Type: (Clear: first phase of Delete), CSP URI: (./Vendor/MSFT/DeviceStatus/TPM/SpecificationVersion), Result: (Unknown Win32 Error code: 0x86000011).

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (DeviceStatus), Command Type: (Clear: first phase of Delete), CSP URI: (./Vendor/MSFT/DeviceStatus/Firewall/Status), Result: (Unknown Win32 Error code: 0x86000011).

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (TenantLockdown), Command Type: (Clear: first phase of Delete), CSP URI: (./Vendor/MSFT/TenantLockdown/RequireNetworkInOOBE), Result: (Unknown Win32 Error code: 0x86000011).

- MDM ConfigurationManager: Command failure status. Configuraton Source ID: (B44EB90D-E2ED-4673-B098-C5D3F1943D80), Enrollment Type: (MDMDeviceWithAAD), CSP Name: (DMClient), Command Type: (Clear: first phase of Delete), CSP URI: (./Device/Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/SkipUserStatusPage), Result: (Unknown Win32 Error code: 0x86000011).

 

We cannot find what the cause of these errors are.

  • We figured out that the user we used (administrator of the tenant) didn't had a Intune license. When switching to another user which has a Business Premiun licenses made the issues go away.
    The error description didn't really help me figure this out, but found this on a page of Rudy Ooms.

    But now, after a couple of reboots, we are running into a 0x80072f76 error. Inside the event log its shown as MDM Session: OMA-DM server message parsing failed. Result: (Unknown Win32 Error code: 0x80072f76)..
  • josvds's avatar
    josvds
    Brass Contributor
    We figured out that the user we used (administrator of the tenant) didn't had a Intune license. When switching to another user which has a Business Premiun licenses made the issues go away.
    The error description didn't really help me figure this out, but found this on a page of Rudy Ooms.

    But now, after a couple of reboots, we are running into a 0x80072f76 error. Inside the event log its shown as MDM Session: OMA-DM server message parsing failed. Result: (Unknown Win32 Error code: 0x80072f76)..
    • josvds's avatar
      josvds
      Brass Contributor
      The other errors we got was because apparently Microsoft has a request limit which was reached when trying to synchronise. So in the background we had HTTP Error 509. The next day this was resolved.

Resources