WEVTUTIL: The specified channel could not be found. Check channel configuration.

This one took a while longer than it should have done. Let’s play “Spot the Difference”

The first command fails, whereas the second command works. Why? Believe it or not, there is a difference in the double-inverted commas. I copied and pasted the command from some webpage.

C:\Windows\system32>wevtutil.exe set-log "Microsoft-Windows-Dsc/Analytic" /q:true /e:true
Failed to read configuration for log "Microsoft-Windows-Dsc/Analytic". The specified channel could not be found. Check channel configuration.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

This site uses Akismet to reduce spam. Learn how your comment data is processed.