Windows discovery takes a long time to complete or fails with errors like "PowershellProcessRunner was interrupted to complete in 600 seconds" in the classification phase or when the Windows Installed Software probe runs.
This is caused by multiple round trips between the MID Server and the target host, which is susceptible to network delays and MID Server load. This issue is seen in both WinRM and WMI protocols.

Steps to Reproduce

Any individual Windows server Discovery that takes in excess of 10 minutes. If you encounter this, you should consider an upgrade to the appropriate version.


This fix includes a number of Java code changes to offload work to the remote Windows server and improve performance significantly. Because of the scope of the changes, no workaround exists for this issue. Upgrade to Madrid Patch 3 or above or to the New York release (any patch). Performance improvements can be dramatic for CPU and memory usage on the MID Server host.

Related Problem: PRB1308592

Seen In

Jakarta Patch 8b

Intended Fix Version

New York

Fixed In

Madrid Patch 3

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-07-09 17:50:12