that's fine and dandy but it doesn't clear out the new Windows Eventing 6.0 logs, which are exactly the pain-in-the-a$$ logs I was referring to in the OP. For example, if you navigate to "Applications and Services Logs->Microsoft->UAC->Operational" you will
likely see a bunch of stuff (I do). Even after clearing those logs using your powershell script, they all remain. the "Get-Eventlog" command is blind to these new format logs.
Are there any other tips or ideas on how to programmatically clear these logs?? there must be a way!!