Direct answer
A software inventory lists known applications on an endpoint with enough context to decide whether each is needed, supported and maintained. Reconcile multiple sources because no single installation record necessarily captures every application.
Collect the right fields
Record the device, collection time, application name, publisher, version, installation scope and known owner. Separate device-wide installations from software installed for a particular user. Management platforms can provide inventory across enrolled devices; a local review is useful for checking one machine but cannot represent the entire fleet.
Reference: Microsoft: Windows app inventory.
Understand the blind spots
Windows application inventory can draw from uninstall registry entries and packaged-app records. Portable tools copied into a folder may not appear in either view, and some records omit version or publisher information. Compare important entries with the application's own version information or vendor records before treating an incomplete value as a finding.
- Include 32-bit and 64-bit installation views and relevant user profiles where your tool supports them.
- Note offline devices and the last successful collection date.
- Avoid using Win32_Product as a routine inventory shortcut: Microsoft documents performance and repair side effects.
Reference: Microsoft: Working with software installations.
Turn the list into a decision
For a remote support tool found on a finance laptop, ask who approved it, whether it is still used and how it receives updates. Compare the observed version against the vendor's support and advisory information rather than declaring it vulnerable by its name alone. Prioritise unsupported or exposed applications with a responsible owner and a target date.
Update and retest safely
Pilot an update or removal, confirm licensing and dependencies, and use the organisation's approved deployment method. Recollect inventory after the change and check that the application still performs its intended function. Where removal is deferred, document a compensating control, review date and the person accepting the exception.
- Keep evidence of the installed and remediated versions.
- Protect exported inventories because they reveal device and user details.
Assessment limits
Inventory completeness depends on collection method, permissions, user profiles and device connectivity. A recorded version alone does not prove a vulnerability is exploitable, and an absent entry does not prove the software is absent.
Frequently asked questions
Can one registry key list every Windows application?
No. Per-user, packaged and portable software can be missed by a single registry view. Combine sources and record coverage limitations.
Is old software automatically vulnerable?
Not necessarily. Check the exact product and version against vendor support and advisory information, then consider configuration and exposure.
Why track the inventory collection time?
An offline device or stale report may not reflect recent updates or removals. The timestamp helps distinguish current evidence from an old snapshot.
Primary sources and further reading
These guides combine published security guidance with practical assessment planning. Adapt checks to the owner's policy, environment, and authorized scope.
This guide was prepared with AI assistance using the linked sources and illustrative examples. Check current vendor guidance and your environment before making changes.