Last updated: 2026-01-02
If you ran Add-WindowsCapability -Online -Name "SNMP.Client~~~~0.0.1.0" but Get-Service SNMP returns service not found, follow this playbook. Microsoft documents installing both SNMP and the WMI SNMP Provider and how to verify the capability state. Microsoft Learn
Goal
Restore the SNMP components so the SNMP service is present and can be configured safely.
Assumptions
-
You are running PowerShell as Administrator
-
You can reboot if required
-
You understand SNMP security implications (SNMP v1/v2c is plaintext community-based)
1) Confirm capability state (don’t guess)
Expected:
-
State : Installedfor the features you want. Microsoft uses these exact capability names. Microsoft Learn
2) Install BOTH features (official fix path)
Even if you only need SNMP, install the pair first to avoid partial states.
Then re-check:
Microsoft explicitly recommends this pattern and verification with Get-WindowsCapability. Microsoft Learn
3) Check services (SNMP + Trap)
If services appear:
-
Set SNMP to Automatic and start:
4) If still missing: repair component store (SAFE)
Run DISM + SFC, then re-run step 2.
Reboot (recommended), then repeat step 2 and step 3.
5) Check DISM logs (when install “says ok” but service is absent)
Look at:
-
C:\Windows\Logs\DISM\dism.log
You’re looking for capability install errors or staging issues.
6) Minimal security baseline (do NOT expose SNMP broadly)
Recommended:
-
Allow SNMP only from your monitoring server IP (LAN only)
-
Block SNMP from WAN
Example: allow UDP 161 inbound only from your monitoring server:
Ajustează IP-ul la serverul tău de monitorizare.
Verification
-
Capability state:
-
Service exists and is running:
-
Port listening (optional):
Rollback (clean removal)
If you decide not to use SNMP:
References (official)
-
Microsoft Learn: “Can’t install the SNMP and WMI SNMP Provider features” (capability names + verify steps) Microsoft Learn
Leave a Reply