The Package Library is why most admins fall for PDQ Deploy in the first hour: hundreds of common applications, already packaged, already silent, maintained by PDQ. But a library package still deserves a technician's first run — the right pick, a test target, and a verified result.
Building your own installer package for Chrome or Adobe Reader would be wasted work — PDQ's team already did it, tests each release, and updates the package when the vendor ships a new version. This guide covers the library run done properly: what you are actually downloading, what to check before the first push, and where the library's limits honestly sit.
When you download a library package, PDQ fetches the vendor's current installer, stores it in the repository on your console, and wraps it in a package with the correct silent switches, sensible success codes and conditions (such as only installing on 64-bit Windows) already set. You are not downloading a PDQ-made clone of the software — it is the vendor's real installer, pre-configured. That is why library installs behave so predictably compared to hand-rolled ones.
Paid editions let you edit a library package and add steps around the install: a pre-step that closes the running application or removes a broken older version, a post-step PowerShell command that sets a registry value or copies a company config file. This is how a generic package becomes your standard build. The honest limit: in free mode a package is limited to one Install step, so pre and post steps are a reason offices upgrade — test them during the 14-day trial, which unlocks the full product.
Deploy the library package with Deploy Once to two or three machines first — ideally including your own PC and one ordinary user's. Confirm three things: the deployment reports success, the application opens on the target, and the new version shows in Add/Remove Programs. Only then widen the target list. That ten-minute discipline is the difference between a library package you trust for the next five years and one bad fleet-wide surprise.
Library packages can be set to Auto Download: when PDQ publishes a new version, the console fetches it automatically. Pair that with a schedule — or with Auto Deployment in Enterprise — and staples like browsers patch themselves. Be selective: auto-download everything, but auto-deploy only the boring, safe applications. Line-of-business software with plugins and integrations deserves a human in the loop, which the rollout-discipline guide in this series covers.
Watch the video's library deployment end to end, then recreate it on your own test PCs — the first successful push takes minutes.
▶️ Watch Full VideoYes. PDQ downloads the vendor's own installer and wraps it with silent switches and install conditions. You get the genuine application, installed the unattended way, which is also why the installed product behaves exactly like a manual install afterwards.
Because PDQ maintains it. When the vendor ships a new version, PDQ tests and updates the package — new switches, new conditions, new quirks handled. Your hand-made package freezes on the day you built it and silently ages.
Yes, the library is available in free mode, but free packages are limited to a single Install step, and Deploy Once is the only deployment method. Schedules, multi-step packages and older library versions need a paid edition — the trial shows the difference clearly.