Question How long should those two processes continue?

[TheFlash1300]

Hello. How long should Service Host: Windows Event Log and Service Host: Local System last, once they start working? In my case, it's been more than 12 hours and they are still ongoing with no signs of slowing down or stopping.

I'm not asking how to reduce CPU usage, but how long the processes should continue and when they will stop.

Here is a photo of Windows Task Manager:

https://imgur.com/q6O5Pbd

View: https://i.imgur.com/q6O5Pbd.jpg


The same two processes in the same order have been ongoing for more than 12 hours. If left unchecked, unstopped, will they cause any harm to the SSD, since they cause 25MB disk usage?

 

[USAFRet]

"Service Host: Windows Event Log " would be running as long as it is 'logging' some information
"Service Host: Local System " Is running when the system is running. Like...all the time.

In the context of a 250GB -500GB drive, how much do you think "25MB" actually is?
Get your calculator out and give us a percentage.

 

[TheFlash1300]

"Service Host: Windows Event Log " would be running as long as it is 'logging' some information
"Service Host: Local System " Is running when the system is running. Like...all the time.

In the context of a 250GB -500GB drive, how much do you think "25MB" actually is?
Get your calculator out and give us a percentage.

So, the process is sending all my SSD content to Microsoft? What informations is it logging? Only 100GBs out of 250GBs are filled with information. If it's running at 25MBs at second, I'm pretty sure all those 100GBs have been already scanned. What else is it scanning?

Usually, I have kept the laptop on for days, and those processes never ran for so long. The last 12+ hours was the first time when those processes started running for so long.

Usually, when the laptop is left idle for hours and days, the CPU usage is at around 4-5% only, not as high as it is now due to those processes running.

 

[USAFRet]

No, it is NOT sending it to MS.

Logging locally at most.

 

[USAFRet]

You can stop those processes manually, if you like.

You can also crank up an install of Wireshark, and see for yourself what is and is not going 'out'.
Of course, this would require an understanding of what Wireshark is doing, and a general concept of how the whole internet works.

 

[TheFlash1300]

You can stop those processes manually, if you like.

You can also crank up an install of Wireshark, and see for yourself what is and is not going 'out'.
Of course, this would require an understanding of what Wireshark is doing, and a general concept of how the whole internet works.

Yes, I know about Wireshark. Currently, I don't plan to analyze Wireshark's information.

I'm interested to know how long those processes should continue on a SSD of 250GB with filled only 100GB, and what information they are recording locally.

Is the logged information only intended for Event Viewer? Because it doesn't look so. 25MBs per second for 12+ hours is many, many GBs. Tomorrow, it will be 24+ hours.

 

[USAFRet]

Event Viewer, Resource Monitor needs to get that data from somewhere.
That way, you can look at Events that happened in the past.

This is called a log.

 

[TheFlash1300]

Event Viewer, Resource Monitor needs to get that data from somewhere.
That way, you can look at Events that happened in the past.

This is called a log.

Yes, I know that. What I don't know is how large the report is? The processes are recording at 25mbs per second for 12+ hours. Do you know how much is that? It's probably more than the whole information on the SSD (100GB).

As far as I know, the whole content of Event Viewer is just a few megabytes, not many gigabytes.

In my opinion, as far as I can tell, those processes shouldn't last more than a few minutes...

 

[USAFRet]

Yes, I know that. What I don't know is how large the report is? The processes are recording at 25mbs per second for 12+ hours. Do you know how much is that? It's probably more than the whole information on the SSD (100GB).

As far as I know, the whole content of Event Viewer is just a few megabytes, not many gigabytes.

In my opinion, as far as I can tell, those processes shouldn't last more than a few minutes...

In your Event Viewer, what is the oldest "Event"?

In my system, in "Windows Logs" (hey, there's that Log word), it goes back over a month, to Oct 3.

Your OS is doing things behind the scenes, to keep things running well.

 

[TheFlash1300]

In your Event Viewer, what is the oldest "Event"?

In my system, in "Windows Logs" (hey, there's that Log word), it goes back over a month, to Oct 3.

Your OS is doing things behind the scenes, to keep things running well.

Everything is fine now. This morning I checked, and saw the processes are no longer recording anything.

Problem solved.

 

[Cj-tech]

Everything is fine now. This morning I checked, and saw the processes are no longer recording anything.

Problem solved.

I don’t see how a normal system process that was not negatively impacting the system was a problem… 🤔