How to track a service via eventlog name in cmd ?

Droyk said:

As i said above process monitor can only see the active services and the non active ones it cant see the already happened one
and these services what i am talking are only happen when you boot your PC So i think your solution was not that good
and if the process monitor company added something new that let you observe the offline sub-services.
Then i have to see that to be sure

No you stated that Process Explorer is not what you want. Process Monitor is the only other alternative. Since you are being really defensive on this, and do not like any of the answers. Then I guess that you should do like most of us do. That is use a search engine.

lx07 said:

Process Monitor isn't the same as Process explorer (but both come from Microsoft sysinternals).

Process explorer is a bit like task manager (you can only look at running things), Process monitor you can set to collect information at boot time (or any other period for example if something starts and stops too fast to see it in Process Explorer).

Watch out. He may tell you off like he did to me. Hate volunteering some help on these types of cases, when the owner of the topic does not want to hear the answers that we have.

I gave you two options to try and figure out your problem. You threw it back into my face, getting defensive about the two tools.

It has already been stated by someone, what the difference is.

Arguing against those of us who volunteer countless hours helping others on here. It will just cause those who refuse to work with the person trying to help you, to state exactly what I stated, which Iam not afraid to tell someone who is being argumentative.

Either you let us help you. Or you can do like the rest of us had to learn and use a search engine to find the answer.

Actually I am understanding what your problem is Droyk. The only one obsessing is you and yes you have a minor issue, which the majority of us ignore. You asked a question, we replied. What did you expect us to do, let it slip down the line then have you come back in a couple of days asking why no one has looked at your post? If you did not want the help, why did you ask for it in the first place? There is not much more that we can do to help, unless you cooperate and do some work on your end.d

This is not something to get upset about. Unless it is something causing BSOD's or program crashing, we just move along and do whatever is next.

We gave you two options. If you are saying that those are not working, you are going to have to use what is called a Search Engine and try to find another way to figure out what the incident is. There are not very many options out there for this kind of stuff.

Process Monitor will have to be ran as a background process and has to be active all of the time when you boot up. Otherwise it does nothing in helping you to find out what is going on. Using SysInternals Tools Like a Pro How to use it to record Boot events. Using Process Monitor to capture system events


All of the rest of us have been in the same situation as you. We all learned how to diagnose items, by using search engines and forums to find a solution. Majority of the time, you have to write your own solution to your problem.