Windows PPKG provisioning fails with error 0x800700b7 — remove conflicting MDM enrollment

Windows

When applying an Esper provisioning package (.ppkg) to a Windows device, the provisioning process fails and the device displays error code 0x800700b7.

Why this happens

This error occurs when one of two conditions blocks the provisioning package from applying: the device is running Windows Home edition, which Esper does not support for PPKG provisioning, or the device already has an active MDM enrollment or provisioning package that conflicts with the new one. Windows does not allow two MDM enrollments to coexist.

Step 1: Confirm your Windows edition is supported

Open Settings → System → About on the device.
Find the Edition field.
- Supported: Windows 10 Pro, Windows 10 Enterprise, Windows 11 Pro, Windows 11 Enterprise
- Not supported: Windows Home
If the device shows Windows Home, upgrade to Pro or Enterprise using a valid license key before continuing. PPKG provisioning cannot succeed on Home edition regardless of any other changes.

Step 2: Remove any existing Work or School account

Open Settings → Accounts → Access work or school.
If any account is listed, select it.
Select Disconnect and confirm when prompted. This removes the active MDM channel that is blocking Esper enrollment.
Restart the device after disconnecting.

Step 3: Remove existing provisioning packages

Open Settings → Accounts → Access work or school.
Select Add or remove a provisioning package.
Remove every package listed. Leftover packages from a previous MDM deployment will continue to conflict even after a work account is disconnected.

Step 4: Check for OEM-preloaded MDM packages

Some manufacturer-configured or IT-imaged devices carry MDM packages that do not appear in the standard Settings interface. Check for these using PowerShell.

Open PowerShell as Administrator on the device.
Run the following command:
```
Get-ProvisioningPackage
```
If any packages are returned, remove them through Settings → Accounts → Access work or school → Add or remove a provisioning package, or follow your device manufacturer's guidance for PowerShell-based removal.
Restart the device after removal.

Step 5: Offboard from any previous MDM platform

If the device was previously managed by a third-party MDM solution such as Microsoft Intune or another endpoint manager, fully retire or unenroll the device from that platform's admin console before proceeding.
Confirm with that platform's console that no enrollment record remains for the device.
Restart the device once offboarding is confirmed.

Step 6: Re-apply the Esper provisioning package

Confirm you are signed in to the device with a local administrator account. Domain or standard user accounts may lack the permissions required to apply a provisioning package.
Apply the Esper .ppkg file downloaded from the Esper Console.
Allow provisioning to complete fully before interacting with the device.

Verify: After provisioning completes, open the Esper Console and navigate to Devices & Groups. The device should appear in your expected group with a status of Online within 5 minutes. If the device does not appear, check that the device has an active internet connection and that no firewall rules are blocking communication with Esper endpoints.

If this doesn't resolve it

If error 0x800700b7 persists after completing all steps above, collect the following before contacting Esper Support:

A screenshot of Settings → System → About showing the Windows edition and build number
Output of Get-ProvisioningPackage from PowerShell
The exact .ppkg file used and the date it was downloaded from the Esper Console
Any additional error text or secondary codes shown on the device during provisioning failure

Contact Esper Support with the above information so the issue can be investigated further.

Still need help?

If you're still encountering error 0x800700b7 after removing conflicting MDM enrollments, please submit a support ticket and include your PPKG file details, the conflicting MDM enrollment information, and the complete error logs from the provisioning attempt.