Pckgr
  • About Pckgr
    • Intro: What is Pckgr?
      • How Package Updates Work
      • PckgrBot
      • Homage to Winget
    • Applications Available
      • Request Application
    • Security of Pckgr
      • Microsoft Single Sign On
    • Pckgr Pricing Model
  • Getting Started
    • Setting up your Dashboard
      • Signing Up
      • Managing Companies
      • Connecting Tenants
      • Adding Team Members
    • Creating Deployments
      • Application Library
        • Detect Applications from Intune with Pckgr
        • Application Status Tag
      • Repositories
        • Winget
        • Private Repository
          • Upgrading an Application to the Private Repository
        • MacOS
      • Deployment Settings
      • Application Management
  • Extra Features
    • Custom Applications
    • Cloning Intune Policies
  • INTEGRATIONS
    • Company Portal
    • Autopilot
  • Troubleshooting
    • Install Logs
    • Error Codes
    • Winget Issues
      • Winget Pre-Install
      • Winget CDN Issue
      • Repair Winget with PowerShell
    • Applications that Require to be Closed Before Updating
    • Frequently Asked Questions
  • SUPPORT
    • Pckgr ChatBot
    • Support Email
    • Delete your account
  • Policies
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  1. Troubleshooting

Install Logs

Pckgr logs the application installation

If you would like to see how the application installation progressed, you can access the logs within ProgramData.

This is the first step of troubleshooting and the Pckgr team will request this from the user when you are having issues with an application install. Please have this file ready to attach to your Application Bug Report Support Ticket.

For Windows:

The file path is C:\ProgramData\Pckgr for System Context apps

and C:\Users\USERNAME\AppData\Local\Pckgr for User Context apps.

The path for Mac applications is /private/var/log/Installomator.log.

PreviousAutopilotNextError Codes

Last updated 7 days ago