title: The description for Event ID 'X' in Source 'Microsoft-Windows-Kernel-Power' cannot be found
body: <p>I am trying to read the System Event Logs in C# .NET 3.5 with the following method <code>EventLog.GetEventLogs</code>. This seems to be working perfectly for all kinds of Event Logs that I want to take a look at. There is but one exception: <code>Microsoft-Windows-Kernel-Power</code> Event Logs which can be read but produces the following Message:</p>
  
  <blockquote>
    <p>Microsoft-Windows-Kernel-Power The description for Event ID 'X' in
    Source 'Microsoft-Windows-Kernel-Power' cannot be found. The local
    computer may not have the necessary registry information or message
    DLL files to display the message, or you may not have permission to
    access them. The following information is part of the event:'Y', 'Z'</p>
  </blockquote>
  
  <p>instead of the correct Message displayed in the Windows Event Viewer.</p>
  
  <p>Code looks like this</p>
  
  <pre><code>var myEventLogs = new List&lt;myModels.EventLogEntry&gt;();
  
  foreach (var eventLog in EventLog.GetEventLogs())
  {
      foreach (var entry in eventLog.Entries)
      {
          if (entry.Source.IndexOf("kernel-power", StringComparison.OrdinalIgnoreCase) == -1 &amp;&amp;
              entry.Message.IndexOf("kernel-power", StringComparison.OrdinalIgnoreCase) == -1)
              continue;
  
          myEventLogs.Add(new myModels.EventLogEntry(entry.Source, entry.Message))
      }
  }
  </code></pre>
  
  <p>This is happening even if I run the application as administrator. I am at a loss here. I have searched far and wide all over the internet and found a couple posts that seem to have similar issues but most are for writing Event Logs instead of having problems reading them. Is anyone familiar with that kind of problem or can point me in the right direction? All my registry keys etc seem to be set up correctly (and it is also showing the same results on a different PC).</p>
  
  <p>EDIT: Windows Version 10.0.18363 Build 18363 but it is happening on multiple PCs (I am not sure what Windows version the others are using). In fact, I have not found a single one which is working (tested 5 so far).</p>