Troubleshooting Steps

Read our best practice processes for troubleshooting your deployment issues

This section of the documentation is designed to assist users in identifying and resolving common issues that may arise when deploying applications through Pckgr. While Pckgr is built to streamline and automate software deployment into Microsoft Intune, variables such as device configurations, installer types, scope mismatches, or network issues can occasionally lead to unexpected results.

Here, you'll find practical guidance and diagnostic steps for addressing these problems efficiently—whether it's an application failing to deploy, not being detected after installation, or any other aspect of your deployment workflows. Before reaching out to the support team, we recommend reviewing these guides to perform initial checks that often resolve issues independently.

Have you checked the Install Logs?

Pckgr creates install logs on the devices for all applications to provide further insight into your installation procedures - we recommend checking these for troubleshooting any errors. Read more here.

Is your application deployed from Pckgr's Winget Repository?

If you joined Pckgr prior to May 2025, you may have been deploying applications from Pckgr's Winget Repository, which you can now upgrade to the Private Repository version, following the instructions in our Upgrade Applications page. For more information on our transition away from our Winget Repository and allowing all users access to our Private Repository, please read the information on our Private Repository page.

The first step is to check which repository you have deployed this application from; this can be determined in your Application Library under the title 'Source' for that application. If it states 'Winget', please upgrade this application to the Private Repository version before any next steps.

After this upgrade has successfully deployed, please assess if your installation error still occurs.

If you joined Pckgr after May 2025, the Winget Repository information will not be applicable to your Pckgr experience and you can move to the next steps.

ERROR: 0x87D1041C Application Installed but Not Detected

Occasionally, users may encounter a scenario where an application is reported as successfully installed in Intune, but Pckgr (or Intune) does not detect the application. Below are steps to identify and resolve the most common causes of this issue.

Read troubleshooting steps

Step 1: First, please check if your application is deployed from the Winget Repository and follow the 'upgrade' instructions mentioned above. This will likely resolve your issue.

Step 2: Check for Installer Type Mismatch (EXE vs MSI)

A common cause of detection failures is an installer format mismatch between what's already on the device and what's being deployed. For example:

• If the deployed version uses an EXE installer but the device already has the MSI version (or vice versa), the detection script may fail.

• MSI installations typically leave registry traces or product codes that EXE versions do not, and detection logic is often tailored to one or the other.

Solution:

• Identify which version is currently installed on the device.

• Compare this with the installation method being used by the Pckgr deployment.

• Redeploy using the matching version type, or uninstall the existing conflicting version first.

Step 3: Check for Scope Mismatch (User vs System)

Another frequent cause is a scope mismatch:

• If the application was previously installed in User Scope (under the user profile) but is being redeployed in System Scope (for all users), the detection logic may miss it—or vice versa.

Solution:

• Determine how the existing installation was scoped (look at the install path—e.g., under C:\Users\<User>\AppData for user installs, or C:\Program Files for system installs).

• Re-align your deployment scope in Pckgr to match the existing installation, or uninstall the original to avoid conflict.

Step 4: Review Installation Logs

Pckgr logs the installation process to help identify what occurred during the deployment:

• For System Context installs: C:\ProgramData\Pckgr

• For User Context installs: C:\Users\<Username>\AppData\Local\Pckgr

These logs can provide clues such as:

• Whether the installation silently failed.

• If a different version was installed.

Review these logs to verify the installation and understand any anomalies. If you're unsure what the logs indicate, you can include them in a support request for further help.

Step 5: When to Raise a Support Ticket

If you have verified:

• The installer type and scope are correct,

• The logs do not show any clear failure or misconfiguration,

• And the detection still fails,

Then it's time to raise a support ticket with our team. Please include the following:

• A copy of the relevant installation log.

• Any error codes or statements showing in Intune for this application.

You can raise a support ticket by following the steps outlined in the Pckgr ChatBot page.

macOS App Updates Not Working

If your macOS applications are no longer updating through Pckgr — even though they were previously deployed successfully — this is likely due to a recent permission enforcement by Microsoft Intune.

Pckgr deploys macOS apps using Installomator-based scripts, which are managed through the Devices > macOS > Scripts section in Intune. These deployments rely on Microsoft Graph API access.

Microsoft now requires an additional permission to perform script-based operations. If this permission has not been granted, macOS app updates through Pckgr will stop without error.

Read troubleshooting steps

New Required Permission

To continue managing and updating macOS applications via scripts, your Microsoft tenant must approve the following Graph API permission:

DeviceManagementScripts.ReadWrite.All

This permission allows approved applications to create, assign, and modify PowerShell and shell scripts within Intune.

Official Microsoft documentation: DeviceManagementScripts.ReadWrite.All – Microsoft Graph Permissions Reference

---

What’s Affected

• Affected: macOS apps deployed through the Scripts section in Microsoft Intune

• Not affected: Apps deployed through the Apps section of Intune (e.g. Windows apps)

You may notice:

• Updates are no longer being delivered to macOS devices

• Intune shows apps as deployed but with outdated versions

• No error appears in Pckgr or Intune — deployments silently stop updating

---

How to Fix It

To restore macOS update functionality, you’ll need to reconnect your Intune tenant and accept the updated permission scope. This can be done through the Policy Manager tab in your Pckgr dashboard.

Steps:

1. Log in to your Pckgr Dashboard: https://intunepckgr.com/dashboard

2. Open the Policy Manager tab

3. Click Reconnect to Intune

4. When prompted by Microsoft, review and accept the updated permissions, including DeviceManagementScripts.ReadWrite.All

After completing this process, Pckgr will resume managing and updating macOS apps automatically. There is no need to redeploy any existing apps.

---

Additional Notes

• Microsoft has not issued a formal public announcement for this change, but it is now actively enforced across many tenants

• This requirement affects all third-party tools that manage Intune scripts via the Microsoft Graph API

• This is the only permission change required to restore functionality

---

Still Having Issues?

If your macOS updates are still not working after reconnecting:

• Ensure the Microsoft account used during reconnection has Global Administrator privileges

• Confirm that the tenant shows a Connected status in the Policy Manager tab

If problems persist, please contact Pckgr support at [email protected] or use the in-app chat in the dashboard.