Custom Classifier with Generic Classification Criteria and Empty Trigger Probe List and High Order Prevents Windows Discovery Pattern LaunchIssue Windows discovery did not trigger expected patterns due to a misconfigured custom classifier with generic classification criteria taking precedence over default classifiers. Symptoms1.Discovery completes without launching the expected Windows Server patterns. 2.No Windows-specific probes or sensors are triggered. 3.Reviewing the discovery status shows that classification occurred, but no follow-up actions (like probes or patterns) were initiated. 4.The classifier used has: -Generic conditions such as Name starts with "windows" or Name contains "windows". -Highest order. -An empty Trigger Probe List.ReleaseAny releaseCause1.A custom Windows classifier was created with: 2.Generic conditions like Name starts with "windows" or Name contains "windows", which matched unintended devices. 3.The highest priority (lowest order value), causing it to override the out-of-box classifiers. 4.An empty Trigger Probe List, resulting in no probes or patterns being launched after classification.Resolution1.Review your custom classifier and its classification criteria. 2.Ensure the conditions are specific enough to avoid unintended matches, and assign a lower priority (higher order value) than standard classifiers to avoid override. 3.Also, verify that the Trigger Probe List is correctly defined.