Deleting Everything with service running.

[harryray2]

Originally, when I wanted to delete Everything.exe to replace it with a newer version I had to stop the Everything service to be able to delete the file. This no longer seems to be the case.

This hasn't caused problems, but I'm wondering why?

[raccoon]

We have a new feature to automatically stop the Everything service when the Everything client is exited. Is that the behavior you're describing?

[harryray2]

Service is still running when I exit Everything...

[harryray2]

I found the stop stop service in the ini file, but I haven't enabled it.

[void]

The ini setting is stop_service_on_exit

What version are you using?
There was a bug in 1330 and earlier that would sometimes stop the Everything Service when exiting Everything. (ignoring this setting)

You can stop/start the Everything Service now with a standard user account.

[harryray2]

The stop service isn't a problem. I don't want it enabled, I'm happy with the way it is, but what I was curious about was that I'm now able to delete Everything.exe without stopping the service, whereas before I couldn't.

[void]

That shouldn't be possible.
You can't delete the Everything.exe while it is running the Everything Service.

Maybe you have another Everything.exe running the Everything Service?
Please check the service path:

• From the Start menu, search for: Services
• Click Services
• Right click Everything and click Properties.
• Check the Path to executable
  Is this different to the path to Everything.exe that was deleted?

[harryray2]

Apologies, I'm not sure if I made it clear..I can delete Everything.exe after I have exited the instance. Previously, I couldn't delete it with the service running.

I'm using one service for all instances.

[void]

You can deleted your Everything.exe as long as that specific Everything.exe is not hosting the Everything Service.

[harryray2]

I'm running three instances, and they can all be deleted while the service is running. The service appears to be running OK.
I'm wondering if this is connected with the problem I have of the service taking a long time to kick in when I updated to 1331?

[void]

What is your Everything service path:

• From the Start menu, search for: Services
• Click Services
• Right click Everything and click Properties.
• What is your "Path to executable"?

What is the path to your Everything.exe for each instance? (it's fine to use the same Everything.exe here)

[harryray2]

The path is to D:\harry\Everything64.exe" -svc -instance "harry".

Which is, as expected.

[void]

Are your three instances also calling this exact same Everything64.exe?
Please check the same drive letter and path.

Are you running a BAT file to install/copy Everything?
Maybe this BAT file is stopping and restarting the Everything Service?
-The only thing that has changed is starting/stopping the service no longer requires admin privileges.

If you delete D:\harry\Everything64.exe, does the service keep running?