How to Detect Missing Software Inventory Items via Script and Generate Compliance Reports If you’re trying to keep endpoints standardized, you’ll need to scale past manual spot checks. This is where script-driven workflows help: You can inventory what's installed, compare it to a baseline, write results locally, and create a master report. In this video, we'll go through five practical methods for detecting missing software inventory, plus how to aggregate results across devices. Before we begin, be sure to subscribe to NinjaOne’s IT video hub and our YouTube channel for more tech content like this. Detect Missing Software Inventory Items via Script Quick disclaimer: this video includes sample PowerShell scripts for demonstration purposes. Full step-by-step instructions and production-ready examples are available in the accompanying blog. As for prerequisites, confirm that the device is running Windows 10, Windows 11, or Windows Server 2016 or later, and that you have local administrator rights. PowerShell 5.1 or later is required to query installed software and generate reports. You'll also need a predefined list of required applications to compare against. For larger environments, having an RMM platform, shared storage for reports, or WMIC available for legacy systems will make automation and reporting much easier. Method 1: Collect Installed Software Inventory with PowerShell Start by pulling installed software from the registry. (both 32-bit and 64-bit uninstall keys), then format or export it. Use this script to make your findings ready for reporting This gives you a consistent data source to compare against your standards. Method 2: Compare Against a Baseline and Flag Missing Apps Next, define a baseline the apps that must be present on every device for compliance. Keep it simple by using display names that match what the uninstall keys report. Then, use this to export it as a per-device compliance artifact: Method 3: Lightweight Inventory with CMD and WMIC If PowerShell is restricted or unavailable, you can still get a rough software list using WMIC on supported legacy systems. And if you want a quick parse from PowerShell afterward, use: Method 4: Store Compliance Results in the Registry Now write your audit outcome into the registry so the endpoint always has a local compliance stamp. Then, use this to validate your values from Command Prompt This makes it easy for an RMM to read compliance without parsing CSVs on-device. Method 5: Generate Cross-Device Compliance Reports Once each endpoint exports its CSV report (or your RMM collects them), consolidate everything into a single master report. And if you want a quick client or site breakdown, group your list using. Once you integrate this workflow with scheduled tasks, GPO, or an RMM, you stop doing one-off audits and start running continuous compliance checks that scale. For more information, check out our official blog post on how to detect missing software inventory items and generate compliance reports, Linked in the description below.