Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Tip

Updated way to Delete all Event Log data at once

Aug 11, 2014 6:27PM PDT
ORIGINAL THREAD: http://forums.cnet.com/7723-19411_102-378338/delete-all-event-logs-at-once-in-windows-7/

This Shortened Command, executed with an Administrative Command Prompt, will easily wipe the entire event log.

BEWARE: WIPING THE ENTIRE EVENT LOG WILL ERASE ANY ENTRIES THAT POINT TO A SPECIFIC SYSTEM ISSUE.

This should only be done if you need the event log wiped for some odd reason, such as "it's too full".

Command: for /f %x in ('wevtutil el') do wevtutil cl "%x"

Source: http://superuser.com/questions/655181/how-to-clear-all-windows-event-log-categories-fast

Discussion is locked

- Collapse -
I'm left wondering
Aug 11, 2014 11:23PM PDT

I'm left wondering why you would ever want to do that. There are automated processes that "rotate" the logs on a regular basis, so they should never become "too full". I can come up with exactly two reasons why you might want to do this.

1: You're trying to cover your tracks after doing something to a computer you shouldn't have
2: You're trying to clear out all the "noise" so you can more readily spot any anomalous entries when trying to pin down a rather elusive problem

The number of times that option 2 would be the case are probably very far and few between.

- Collapse -
You are correct..
Aug 12, 2014 2:44AM PDT

Reason 2 was the logic behind this method while I tracked the cause of an extremely slow boot up time.
If I booted with an external HDD connected to the front panel, it booted in 5 seconds. If booted without the external HDD, it took upwards of 2 minutes to get through the Windows splash, but afterward runs perfectly fast.
Upon checking the Event Log the first time, there was too much information to specifically pinpoint the issue. So post wiping the Logs and a reboot into safe-mode, I noticed the usb port's driver was the source. After running a few name software repairs and a fresh install, the problem persisted. It was 3am at the time and even I get tired. So I pulled out the screw driver and opened up the rig, hoping to end it before 5am.
The solution was a loose connection to the port on the motherboard. Pulled it, boots fast; reconnected, boots fast again.

My only concern is that the port on the motherboard may be failing and I may need a new motherboard..
Sounds like fun. =.=