Windows Event Viewer works for a quick look at one local log. Once Windows events become part of your regular work, its limits cost time: multi-log investigations are awkward, remote systems are cumbersome to manage, and reusable analysis setups are limited. A dedicated tool should let you move from an alert or symptom to a repeatable investigation without rebuilding the same view every time.
Learn how to troubleshoot common connectivity and authentication issues when accessing remote Windows event logs. This guide covers the most frequent causes of failures, including firewall and RPC configuration, permissions, UAC restrictions, Kerberos authentication, VPN-related issues, and time synchronization problems.
A serious bug in the Windows Event Log API events to show the same task category. It affects most third-party log viewers and even PowerShell — only Windows Event Viewer displays the correct data.
We released Event Log Explorer 5.7.2, which includes robust workarounds for this Windows API bug.
When you take the first look to Event Log Explorer, you may notice Type column in the event list. In the same time, Windows Event Viewer doesn’t have this column, which may confuse you. If you worked with Windows Event Viewer in old times (with Windows XP or below), you could see the Type column. There were 5 types of events that can be logged… Read More »
Update of May 18, 2020: It looks like Windows 10 1909 doesn’t have this issue. Although era of Windows XP is over, there are still a great number of PCs running this operating system or Windows 2003 Server. According to different researches, in 2018 Windows XP market share was more than 4% of all desktop operating systems. Windows 2003 Server still has more than 10%… Read More »