The modern Event Viewer application that you get on all versions of Windows since Vista is so much slower the previous version that was on Server 2003 and XP. I know there is much more functionality in the newer version but most of the time I just want to quickly scan the various different event logs as quickly as possible. How can I get the the old version back?

The splitting up of the application event logs actually IMO makes it easier as now I can drill down and review ONLY what I want to review. You can setup a custom view that will show up in the tree above the standard windows logs. That might make your task more speedy once it is setup. FWIW, I don't generally find it very slow, but then again, it isn't terribly quick either. Maybe you have other issues you need to address? Are your logs huge?
–
MikeAWoodMay 17 '13 at 0:42

It's nothing to do with the size of the logs or dividing the logs into multiple different logs. It is just the snappyness of the tool when viewing each log. I appreciate the new viewer adds support for various scenarios but I still want my primary scenario to be as good as it used to be. I found a solution to have the best of both worlds .
–
Martin HollingsworthMay 17 '13 at 0:48

If the cliche of sifting forums of 1,000 useless answers for just one golden idea a day, even it takes eight hours to find it, Martin's answer is the winner of the week!!!!! That tip and article helped me too and I confirmed it works on Server 2012 too.
–
Karen3819x4May 17 '13 at 2:54

Why only worry with this is that it is missing all the application logging as well. So events that have a specific application event won't show up if the older tool is used exclusively. My concern long term would be that you would miss things that would otherwise be exposed. But very cool find and certainly a good work around if all you are going after are the regular event logs.
–
MikeAWoodMay 18 '13 at 0:32

I'm well aware of the power of PowerShell, including the CmdLets for the event log but the question was really all about restoring an existing capability. I'm all for the command line as a default but sometimes a GUI just suits the browsing scenario where you don't really know exactly what you are looking for.
–
Martin HollingsworthMay 17 '13 at 3:15

Sorry, I know it doesn't directly answer your question. I just learned about this and was excited to share. Feel free to downvote.
–
kceMay 17 '13 at 6:15

I actually up voted your answer as it does add to the discussion. Just not the right answer to the scenario I was interested in. Thanks anyway @kce
–
Martin HollingsworthMay 17 '13 at 7:07