# How Package Updates Work

Pckgr simplifies the process of managing apps in Intune by pushing the initial package and capturing the App ID in the Pckgr database. \
\
When updates are available, Pckgr uses the Graph API to update specific fields, such as the version parameter in the PowerShell script.

Pckgr continuously checks for updates, then tests, packages and pushes them to your Intune for deployment, replacing the application with the new version. An important benefit of using Pckgr is that app settings are preserved and not reset after an auto-update triggered by Pckgr.

For more information on the deployment workflows, read our [Creating Deployments](/getting-started/creating-deployments.md) page.

**Deployments using PSADT**\
For Windows applications, Pckgr uses the PowerShell App Deployment Toolkit (PSADT) to wrap installation and uninstallation logic, enabling silent installs, deferral handling, and reliable removal.

Pckgr now supports **PSADT v4**, which includes modernized compatibility, improved logging, and support for branded user prompts.

→ [Learn more about PSADT](/integrations/psadt-v4.md) and how it’s used in Pckgr

<img src="/files/og1R1mCbFvy6UukjvAh9" alt="" class="gitbook-drawing">


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.intunepckgr.com/about-pckgr/intro-what-is-pckgr/how-package-updates-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.