Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

EtwRTNT Kernel Logger.etl writing, reading all the time?

- - - - -

  • Please log in to reply

#1
River Horse

River Horse

    Member

  • Member
  • PipPipPip
  • 100 posts

This process - C:\WINDOWS\system32\Logfiles\WMI\RtBackup\EtwRTNT Kernel Logger.etl - seems to read and write all the time:

5uiRo0a.png

 

In about 7 minutes over 3 GB. Is it like it should be? Can / should one stop that process? Because it impacts the performance?


  • 0

Advertisements


#2
winstinks

winstinks

    New Member

  • Member
  • Pip
  • 1 posts

Sorry to say I've had this issue for weeks and still no joy. Over the years I've largely migrated to Linux because of nonsense such as this and rarely use Windows for much other than for Windows-centric photo programs such as Lightroom, etc. As near as I can tell this kernel logging seems to be something new since I "upgraded" to the Creator's Update last year. In any case I've Googled myself into oblivion and by all accounts this idiotic file is essential to this OS running at all. I find it patently ridiculous that an OS, sitting essentially idle, needs to constantly read/write to a log file and worse yet not provide an obvious and easy way for the user to disable it.

 

Good luck finding out any useful info on this utter foolishness.

 

 

  • 0

#3
River Horse

River Horse

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 100 posts

Thank you very much, yes, good luck is very welcome not only for that foolishing process but also for using the foolish respectively senseless Windows.


  • 0

#4
Guy...

Guy...

    New Member

  • Member
  • Pip
  • 1 posts

Just had the same exact problem - and it seems to be caused by NirSoft's FileActivityWatch itself (the monitoring tool from the screenshot).

When I close it and open Resource Monitor I don't see any writing to EtwRTNT Kernel Logger.etl, and when I denied writing access to the file and opened FileActivityWatch the program stayed empty (didn't display any information about files).

I guess it uses this file as part of its log.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP