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.
ERROR: 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: 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 2: 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 3: 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 4: 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 page.
