Windows device enrollment appears successful but Blueprint fails to apply: app install and wallpaper converge errors on Windows MDM

Windows

When a Windows device completes enrollment but its assigned Blueprint fails to apply, app installations and wallpaper settings report convergence errors in the Activity Feed—or no convergence activity appears at all.

Why this happens

After enrollment, the Esper Agent attempts to converge the device to its Blueprint by installing apps and applying settings. On Windows, this convergence can silently fail if the app package referenced in the Blueprint is missing or unpublished, the wallpaper image does not meet Windows format or size requirements, or convergence events are hidden in the Activity Feed—making errors difficult to spot without changing the view filter first.

Steps

1. Enable convergence event visibility in the Activity Feed.
   Go to Devices & Groups → [Device Name] → Activity Feed and toggle on Show Converge Events. By default this toggle is off, so convergence errors such as Failed to install application or Failed to apply desktop wallpaper are hidden even when failures have occurred.
2. Review the Activity Feed for specific error messages.
   With convergence events now visible, scroll through the feed and note every error code or message shown. Record the exact text—you will use this to target the right fix in the steps below.
3. Confirm the correct Blueprint is assigned to the device.
   Go to Devices & Groups → [Device Name] → Blueprint and verify that the intended Windows Blueprint is assigned. If the wrong Blueprint is assigned, select the correct one and save.
4. Verify the app package is uploaded and published.
   If the Activity Feed shows a Failed to install application error, go to Apps & Configuration → Apps → Private Apps and confirm the following:
   • The app package is present and its status is Published.
   • The package name and version number in the Blueprint exactly match what is uploaded here.
   An unpublished or mismatched package version will cause every convergence attempt to fail for that app.
5. Check the wallpaper image requirements.
   If the Activity Feed shows a Failed to apply desktop wallpaper error, open the Blueprint in Apps & Configuration → Blueprints → [Blueprint Name] and confirm the wallpaper image is attached and meets Windows requirements: JPEG or PNG format, recommended resolution of 1920×1080 or higher, and file size under 10 MB.
6. Re-apply the Blueprint to trigger a fresh convergence attempt.
   From Devices & Groups → [Device Name] → Blueprint, re-apply the Blueprint. Watch the Activity Feed immediately after—a new convergence attempt should appear within a few minutes.
7. Remove and re-add the device to its group if no convergence activity appears.
   If re-applying the Blueprint produces no new Activity Feed entries, go to Devices & Groups → [Device Name], remove the device from its current group, then re-add it to the same group. This forces a fresh group-level Blueprint assignment and triggers a new convergence cycle.

Verify: The issue is resolved when Devices & Groups → [Device Name] → Apps shows the application status as Installed, and the Activity Feed displays a convergence success entry with no Failed to install application or Failed to apply desktop wallpaper errors. This should reflect within 10 minutes of re-applying the Blueprint.

If this doesn't resolve it

If convergence errors persist after completing all steps above, contact Esper Support with the following information:

• Device serial number or Esper device ID
• Screenshots or an export of the full Activity Feed showing convergence errors
• Blueprint name and configuration details, including app package name, version, and wallpaper settings
• Exact error codes or messages recorded in Step 2

Still need help?

If you're still experiencing app installation or wallpaper application failures after enrollment, please submit a support ticket and include your Blueprint configuration, the specific apps or wallpaper settings that are failing, and any error messages from the device logs.