Partial Software Installation Data Loss during Discovery

[asalas]

Hi all,

I am getting inconsistent Software Installation results across multiple ITOM Discovery environments (including PDIs and Permanent Dev Instances). While Discovery completes without errors, the Software Installations tab shows incomplete data for certain Windows PCs and Servers.

Property Validation: Discover software packages is set to true.

Filter Configuration: No active software filters are configured in the Discovery Configuration Console.

Payload Discrepancy: 1. When executing the "Windows - Installed Software" probe/pattern test directly against a problematic target, the resulting payload contains the full list of expected software. 2. However, during a standard Discovery schedule, the payload processed by system ppears truncated or results in fewer records being committed to the CMDB.

Is there a hard-coded limit or an undocumented "sanity filter" within the sensor/pattern processing that discards software records based on specific criteria (e.g., missing version, publisher, or "Common" naming)? Is this behavior expected when the reconciliation engine detects high-volume software payloads? How can I force the system to commit every entry captured in the raw WMI/PowerShell output to the Software Installation table without any truncation?

For reference a pc with 300 software are just getting 22 records on tab. 

Thanks in advance!

[asalas]

Hi,

Following our investigation into the truncated results during the discovery process, we have identified that the issue is caused by damaged registry keys. This behavior is documented in NETBEANS-2523.

In my local environment, I’ve confirmed that these specific keys cause the process to hang or return incomplete data.

Is there a way to configure ServiceNow to ignore these type o registry keys or skip them upon error to ensure the discovery process completes successfully?

Best regards,