Windows Server 2022 — Windows Event Forwarding subscriptions stop delivering events — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Windows Event Forwarding subscriptions stop delivering events on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the monitoring subsystem is in use, typically following configuration drift or recent updates.

wecutil gs SubscriptionName
Get-WinEvent -LogName 'Microsoft-Windows-EventCollector/Operational' -MaxEvents 30

Root Cause Analysis

The defect stems from misaligned event forwarding settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Get-Service Wecsvc | Select Status,StartType
winrm enumerate winrm/config/listener

Step-by-Step Diagnosis

Walk the monitoring stack from configuration to runtime, collecting logs and counters that point at the failing component.

wecutil gr SubscriptionName
Get-WinEvent -LogName 'Microsoft-Windows-Forwarding/Operational' -MaxEvents 30

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the event forwarding component re-initialises cleanly.

wecutil ds SubscriptionName
wecutil cs C:SubscriptionsSecurityEvents.xml
Restart-Service Wecsvc
winrm qc -q

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

New-Item -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindowsEventLogEventForwardingSubscriptionManager' -Force
Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindowsEventLogEventForwardingSubscriptionManager' -Name '1' -Value 'Server=http://collector.contoso.com:5985/wsman/SubscriptionManager/WEC,Refresh=60'

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

wecutil rs SubscriptionName
Get-WinEvent -LogName 'ForwardedEvents' -MaxEvents 10

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

wecutil ds SubscriptionName
Restart-Service Wecsvc

Prevention & Hardening

Bake the validated event forwarding configuration into baseline GPOs or DSC and add a monitoring check for early detection.

wecutil ss SubscriptionName /e:true /cm:Push
New-NetFirewallRule -DisplayName 'WinRM-HTTP' -Direction Inbound -LocalPort 5985 -Protocol TCP -Action Allow

Related Errors & Cross-Refs

Related: other monitoring failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.