MECM Software Inventory not reporting per user installed applications

Hello Admin Diego Melica,

This is expected as explained in the previous answer. If this is something you want to achieve, you can try creating a custom WMI class to capture this information and extending hardware inventory.

Refer to: Extend hardware inventory - Configuration Manager | Microsoft Learn

Hope this helps!If you found the information above helpful, please Click Yes. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.

MECM’s built‑in software inventory and Asset Intelligence are primarily designed to inventory:

• MSI‑based products (via Windows Installer)
• Executables and files discovered according to configured inventory rules
• Applications installed in the machine (per‑device) context

Per‑user installations such as:

• Google Chrome (User Installer)
• Visual Studio Code (User Setup)

are typically installed into the user profile and registered per‑user rather than per‑machine. These do not appear in:

• Standard Software Inventory
• Installed Software / Asset Intelligence
• Resource Explorer

because the inventory mechanisms MECM relies on do not enumerate all per‑user contexts in the way needed for a complete per‑user application inventory.

Windows Installer itself distinguishes between per‑user and per‑machine contexts, and earlier inventory mechanisms could only enumerate items in the machine context or the current user’s per‑user context, which prevents a complete inventory of all products installed by other users on the same system. MECM’s Asset Intelligence and software inventory inherit these limitations.

There is no configuration switch in the provided material that enables MECM to fully and reliably inventory all per‑user installed applications like Chrome User Installer or VS Code User Setup across all user profiles.

To inventory such software, alternative approaches are required, for example:

• Custom file inventory rules targeting known per‑user install paths (with the caveat that this is file‑level, not product‑level, and may still miss some user‑context registrations).
• Using other inventory mechanisms (such as WMI application inventory classes or Defender Vulnerability Management software inventory) that are designed to discover installed applications at the OS level, where applicable.

However, based on the context provided, MECM’s standard software inventory and Asset Intelligence cannot be expected to comprehensively report per‑user installed applications.

References:

• Using Windows Installer to Inventory Products and Patches
• Application Inventory Classes
• Software inventory