Pckgr Blog

  • Custom Applications 2.0 is live!

    Custom Applications started life as a simple popup on the dashboard. You uploaded an installer, it ran through testing, and that was about it. It did the job, but it was thin. There was no real way to manage an app once it was in, and a single page refresh at the wrong moment could…

    Thomas Mahony

  • Jabra Direct moving from x86 to x64

    Jabra has transitioned to a 64-bit version of Jabra Direct from the previous 32-bit build. During testing, the x64 installer successfully updated the x86 version without leaving duplicates. It’s crucial to check both registry hives for detection, ensuring a smooth update across devices transitioning to the new architecture.

    Thomas Mahony

  • Slack Retired the Machine-Wide MSI: Migrating to the New MSIX with Intune

    Slack has replaced its machine-wide MSI package with an MSIX package for Windows deployment as of September 15, 2025. This change complicates migration since admins must uninstall the MSI before installing MSIX. Pckgr now offers a solution, automating the uninstall process and simplifying deployment, allowing seamless transition for IT teams managing multiple devices.

    Thomas Mahony

  • Application Templates: Onboard a New Tenant Without Adding Apps One at a Time

    Pckgr has introduced a new feature called Application Templates to streamline client onboarding. This allows users to bundle frequently used applications and their settings into a reusable template. Instead of repetitive configurations for each new tenant, users can quickly deploy pre-set apps, ensuring consistency and efficiency across multiple tenancies.

    Thomas Mahony

  • Edge and WebView2 x86 or x64? Why Registry Detection Falls Short in Intune

    When deploying Microsoft Edge and WebView2 via Intune, traditional detection rules can fail due to inconsistent registry values that don’t indicate application architecture. A proposed solution involves using the PE header trick, which confirms the binary’s architecture, ensuring that updates target the correct version and architecture, preventing app malfunctions.

    Thomas Mahony

  • Tracking and Patching CVEs in Pckgr Portal

    Pckgr Portal enhances endpoint management by streamlining the patching process for vulnerable applications. Users can easily identify and remediate vulnerabilities with just a click. The platform tracks installed apps and matches them with CVE data, enabling efficient updates or uninstalls of risky software. It currently supports Windows desktop applications.

    Thomas Mahony

  • Introducing Wingetly – Search Every Winget App in One Place

    In todays blog we have something a little different to share. We have just launched Wingetly, a free community resource that lets you search and bundle apps from the Microsoft Windows Package Manager (Winget) catalog right inside a web browser. If you have ever tried to find a specific app in the Winget repository, or…

    Thomas Mahony

  • How We Kept Breaking Cursor With Our Own Patching Tool And then Fixed it

    The author discusses a recurring issue with updating the Cursor app, an Electron-based code editor, through Microsoft Intune. The problem arose from running the app while updating, causing file errors. The solution was to use Pckgr’s “Allow Defer Close Apps” feature, preventing broken installations and enhancing update reliability.

    Thomas Mahony

  • Introducing the Pckgr Portal: Lightweight, Affordable Device Management

    The Pckgr Portal has launched as a lightweight, affordable device management platform for managing Windows fleets. It simplifies app management with over 700 pre-built applications and offers features like Smart Patch for streamlined updates and a self-service app store. The portal enhances fleet visibility while maintaining privacy in remote access, catering to smaller teams and…

    Thomas Mahony

  • Wireshark Explained – Why Your MSI Deployment Fails with a 1603 Error

    Deploying Wireshark via Microsoft Intune can lead to installation failures due to the presence of two distinct Windows installers—EXE and MSI—that cannot coexist. Users often install the EXE manually, causing the MSI deployment to fail with a 1603 error. Identifying the installed variant helps resolve these conflicts and streamline future deployments.

    Thomas Mahony