Everything Service

Discussion related to "Everything" 1.5.
Post Reply
elisay
Posts: 1
Joined: Fri Oct 24, 2025 3:45 pm

Everything Service

Post by elisay »

I have used both Everything v1.4 and v1.5 versions on my computer, and both run in Portable mode. It seems that Everything 1.4 and 1.5 cannot enable the Everything Service at the same time. I tried "Everything.exe -svc -svc-pipe-name "EVTv15" to create a new Everything Service for Everything v1.5, or tried "Everything.exe -instance "NASServer" -service-pipe-name "\\.\PIPE\Everything Service" for Everything v1.5 to use the same Service with v1.4. But all failed.
therube
Posts: 5723
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service

Post by therube »

What is it you're trying to do?
Do you need -service-pipe-name specifically?

As it is, both 1.4 & 1.5 will run, simultaneously, each with their own Service.
By default, 1.5 uses a service name of "1.5a".
(There are settings you can make to not need to include the 1.5a, but that means that you can't then use 1.4, I believe.)

Everything.exe -instance 1.5a ...


If 1.4 is running, it talks to the 1.4 Service.
If 1.5 is running, it talks to the 1.5 Service.
Both services can be running simultaneously (if wanted).
void
Developer
Posts: 19870
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service

Post by void »

Both services can be installed at the same time.

Everything 1.5a uses the Everything 1.5a service name.
While Everything 1.4 uses the Everything service name.

However, disabling the alpha instance with NO_ALPHA_INSTANCE will cause Everything 1.5a to use the Everything service name.

Creating the NO_ALPHA_INSTANCE file is not really recommended.

I recommend disabling Tools -> Options -> Advanced -> alpha_instance instead.



The services are not compatible with each other.
Everything 1.4 requires the Everything 1.4 service and Everything 1.5 requires the Everything 1.5 service.

Changing the pipe name is not enough as this doesn't change the service name.
Post Reply