Issue Summary
A Windows provisioning package allows bulk enrollment of Windows 10 or later devices into Microsoft Intune. However, you might encounter the following error when attempting to enroll a Windows 11 device using a provisioning package:
Provisioning failure: Installation of a provisioning package failed. Please work with the package author to diagnose the problem.
Reported error code: 0x800700b7
The error code 0x800700b7 Typically indicates that a provisioning package has already been applied to the device. As a result, the system is unable to create a new provisioning instance. This issue commonly occurs if the same provisioning package was previously executed on the device.
TL;DR:
Error 0x800700b7 during Windows 11 Intune enrollment via provisioning package means the package already exists on the device. Go to Settings → Accounts → Access work or school → Add or Remove a provisioning package, remove the existing one, and then re‑run the .ppkg.

What Causes Error 0x800700b7?
The error typically occurs when:
- A duplicate provisioning package has been applied to the device.
- Remnants of a previously applied package remain in the system registry.
- The provisioning package itself is corrupted or incomplete.
In short, Windows detects a conflict when trying to apply the same package more than once, or when leftover configuration data interferes with enrollment
How to Fix Enrollment Error 0x800700b7
To fix the 0x800700b7 error, you need to remove the provisioning package by following the steps below. Once the existing package is removed, you can run the package again.
- Open Settings
Go to Settings → Accounts → Access work or school. - Check for Provisioning Packages
Click on Add or Remove a Provisioning package at the bottom of the screen.

- Remove Duplicate Package
On the Add or Remove a provisioning package screen, select the provisioning package that you want to remove and click on Remove.

Retry Enrollment
Re-run the provisioning package or initiate Intune enrollment again. It should work as expected now.
Still encountering the error? Feel free to leave a comment below or reach out with your log snippet for further assistance.
Advanced Troubleshooting
If the issue persists, try these additional steps:
- Check Event Viewer Logs
Navigate to Event Viewer → Applications and Services Logs → Microsoft → Windows → DeviceManagement-Enterprise-Diagnostics-Provider. Look for detailed error messages. - Review Registry Keys
InspectHKLM\Software\Microsoft\Provisioningfor leftover entries from old packages. Remove only if you’re confident—always back up the registry first. - Validate Package Integrity
Ensure the provisioning package (.ppkgfile) is not corrupted. Recreate or re-export it if necessary.
Related Posts
- Win32 App Deployment failed with error code 0x80070643
- Win32 App Deployment Failed with Error 0x87D1041C
- Win32 App Deployment failed with error 0x87D300C9
- Win32 App failed with error code 0x80070653
- That account info didn’t work – error when disconnecting Windows 10 / 11 Work or School account
- Intune – Windows 10 MDM- Basic troubleshooting
- Deploying Microsoft 365 Apps Stuck in Downloading in Company Portal
- Windows 10 / 11 Operating System Build Versions
- MDM Enroll: Device Credential, Failed (Unknown Win32 Error code : 0xcaa9001f
- Microsoft Endpoint Manager: Error Code Reference
- Intune Bulk Enrollment with Provisional Package failed Error 0xCAA2000C
- How to Fix Intune Win32 App Deployment Error 0x87D30006
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.