When no windows credential is working, Device History state for Windows Classify is left in Active. As a result when 3 or more ports are open on a target, not all the classify probes are launched.DescriptionWhen no windows credential is working, Device History state for Windows Classify is left in Active. As a result when 3 or more ports are open on a target, not all the classify probes are launched.Steps to Reproduce > Run discovery to a target that has port 135, port 22 and port 161 open> Only Windows - Classify and Unix - Classify probes are launched. SNMP - Classify is not launched> Check Device History, Windows - Classify is still showing active after discovery status is marked completedWorkaround> Open Script Include: DiscoverySensor Update the "shouldUpdateDeviceIssueState" function to the following shouldUpdateDeviceIssueState: function(errors) { if (errors.length === 0) return false; if (errors.length !== 1) return true; if (!errors[0].msg) return false; /* * When we are dealing with a classify probe we always want to update issue state so we * don't leave a device in classifying state. */ if (JSUtil.notNil(g_probe.getParameter("use_class"))) return true; /* * Iterating over the errors to see whether we want to skip the update of device history. * some() will return 'true' in case the condition is met on ANY of our values and in our case, if we find a match * we want to return 'false' [hence the !] and if none of our errors was found in the message * we want to return 'true' [= update device history record] */ return !DiscoverySensor.PayloadErrors.some(function(error) { return errors[0].msg.indexOf(error) > -1; }); }, Related Problem: PRB1544017