Windows PPKG provisioning fails with error code `0x800700b7`: device on unsupported Windows edition or has existing MDM/provisioning package

Windows

If your Windows device fails to provision with Esper using a provisioning package (.ppkg) and shows error code 0x800700b7, this article will help you resolve it. This error typically indicates that your device is running an unsupported Windows edition or already has an existing MDM enrollment that conflicts with Esper provisioning.

Before you begin

Esper's provisioning package method only works on Windows 10 Pro, Windows 10 Enterprise, Windows 11 Pro, or Windows 11 Enterprise. Windows Home edition is not supported for this provisioning method.

How to check your Windows edition

On your device, open Settings → System → About.
Look for the Edition field and note which version you have.
If you see Windows Home, you cannot provision via provisioning package. You must upgrade to Pro or Enterprise edition using a valid license key before you can provision with Esper.

How to remove existing Work/School enrollment

Open Settings → Accounts → Access work or school.
If any work or school account is listed, select it.
Click Disconnect.
Follow any prompts to confirm removal.

How to remove existing provisioning packages

Open Settings → Accounts → Access work or school.
Look for an option to Add or remove a provisioning package.
Remove any existing provisioning packages listed.

How to check for OEM-preloaded MDM packages

If your device was pre-configured by the manufacturer or your IT department, it may have MDM enrollment that doesn't show in the standard Settings interface. To check for these packages:

Open PowerShell as Administrator on the device.
Run the following command:
```
Get-ProvisioningPackage
```
If any packages are returned, remove them using the Settings interface or PowerShell as instructed by your device manufacturer.
Retry Esper provisioning after removal.

How to prepare your device for Esper provisioning

Follow these steps in order to clean your device and make it ready for Esper provisioning:

Verify your Windows edition is Pro or Enterprise (see "How to check your Windows edition" above).
Remove any existing Work/School enrollment (see "How to remove existing Work/School enrollment" above).
Remove any existing provisioning packages (see "How to remove existing provisioning packages" above).
Check for OEM-preloaded MDM packages (see "How to check for OEM-preloaded MDM packages" above).
If your device was previously managed by another MDM solution (such as Intune or Microsoft Endpoint Manager), fully offboard it from that platform and confirm all enrollment data is removed.
Ensure you are logged in with a local administrator account on the device.

How to re-apply the provisioning package

Once your device is clean and meets all requirements above, re-apply the Esper provisioning package (.ppkg).
Wait for provisioning to complete. The device should appear in the Esper Console under your expected device group and show an Online status.

If the error persists

If error 0x800700b7 continues after following all steps above, collect diagnostic information from your device:

Confirm your device is running a supported Windows edition (Pro or Enterprise).
Confirm there is no existing Work/School enrollment or provisioning package.
Collect the Windows Activity Feed from Microsoft-Windows-Provisioning-Diagnostics-Provider.
Note your device model, exact Windows build number (you can find this by running winver on your device), and the provisioning package file you are using.
Contact Esper Support with this information.

Still need help?

If you've completed all steps above and your device is still not provisioning, contact Esper Support. include the error code, your Windows edition and build number, your device model, and any Activity Feed files you've collected.