Use PowerShell to identify recent Error and Critical events across Windows Server event logs.
01 Select a time window
06 Avoid over-filtering A missing error does not prove that the system is healthy. Combine event data with service, network and performance checks.
Define the last hour, day or other period that matches the incident investigation.
Select a time window
Query the logs
Use Get-WinEvent with a FilterHashtable to avoid reading the entire log unnecessarily.
Prioritize severity
Filter for Error and Critical levels and include ProviderName, Id and message text.
Correlate timestamps
Compare event timestamps with the start of the user-visible issue and other infrastructure changes.
Export findings
Create a CSV or HTML report containing time, log, provider, event ID and message.
Avoid over-filtering
A missing error does not prove that the system is healthy. Combine event data with service, network and performance checks.
Explore more TechRunbook guides
Continue with practical infrastructure troubleshooting, PowerShell scripts and operational runbooks.
Browse all articles →