UseEverythingInstance and Everything options [SOLVED]

[ghisler(Author)]

does Total EXACTLY know how to call this utility

Yes, calling everything is done like this:
1. Find a window where the class is named "EVERYTHING_TASKBAR_NOTIFICATION", or when UseEverythingInstance is set, look for a class named "EVERYTHING_TASKBAR_NOTIFICATION_(instance name)"
2. Send WM_USER messages to that window with specific requests, and wait for the reply.

[tuska]

How were you able to determine after the search query that the wrong Everything instance was being used?

In fact, under such conditions of the test that cmd4ever did, it raises a completely different question: does Total EXACTLY know
how to call this utility when using both programs in this spec.case with -instance param?
Under the condition that one version/exe/one (unnamed) instance works - as probably happens for many users,
like take at least me/you - yes, the Total works then. BUT these are not the test conditions that we need to check.

I asked this question because there are test scenarios where it's not easy to determine
when and if the defined Everything instance is actually used.

Example - Settings

1. 'Unnamed instance'
   1. UseEverythingInstance=
   2. Everything=C:\Everything\Everything.exe
2. Named instances
   1. UseEverythingInstance=PRIVATE
   2. Everything=C:\Everything\Everything_PRIVATE\Everything.exe -instance "PRIVATE"
3. Indexed drives in Everything
   1. 'Unnamed instance'    NTFS > C:, D:, G:
   2. 'Named instance'        NTFS > i:

Example - execution

1. Total Commander is running
2. Everything 'Unnamed instance' is running
   Task Manager -> Processes -> App: Everything 1.5.0.1409a (x64) -> Command line: "C:\Everything\Everything.exe" -startup
3. Everything instance "PRIVATE" is closed
4. Perform a search in Total Commander using Everything
   1. Search in separate process... Alt+Shift+F7 -> Find Files (separate)
   2. Search for: ToDo_temporary.txt
   3. Search in: I:\Data\zzz___ToDo___temporary
   4. 'Everything' (because the 'Unnamed instance' is running)
   5. Click on the "Start search" button
   6. Search results: [1 file and 0 directories found] -> I:\Data\zzz___ToDo___temporary\ToDo_temporary.txt
5. A result was found for drive i:, even though the 'Unnamed instance' only indexed drives C:, D:, and G:.
   This means that, in my opinion, the Everything instance "PRIVATE" was NOT used (because it was closed)
   but instead, the Total Commander search was used -> because the 'Unnamed instance' was running and because NO
   Everything parameters, such as ed: and ev:, were used in the search query in Total Commander.
   
   This is also the result I expected!

However, anyone who absolutely wants to find out how it works in practice can work out dozens of examples
and then report on them, e.g., 1x without TC parameter ed: and 1x with TC parameter ed:, etc.

Four examples were sufficient for me, and they produced the result I expected.

However, there were also other examples that I didn't like at first,
but which only occurred in cases where, for example, a TC search query was initiated,
and neither an 'Unnamed instance' nor a 'Named instance' was running.

The solution is well-known: Start at least one Everything instance.
Ideally, the instance where you expect your drives, etc., indexed in Everything to be located,
because otherwise you might not get any search results when using the TC parameters ed: or ev:.

Well, now I'm dropping out of this topic for the second time, but this time probably for good.

[cmd4ever]

Tried with CTRL-F via TC (TC launched C:\Program Files\Everything\Everything.exe -instance TC -startup)
And searched both *.* with the default "search in" c:\ path and with an empty "search in"

TC search gave me all files on C:\ ignoring the Everything -Instance TC scope. What am I doing wrong?

How were you able to determine after the search query that the wrong Everything instance was being used?
Or am I misunderstanding something here?

Hard to tell with the added complexity of ED: and EV: Both of you just told me about.

What I know for sure: TC didn't limit the results to the -Instance scope I asked and expected when I checked the Everything box.
But where the results came from? That I don't know for sure either.

Did TC even used Everything for the results? It took a certain amount of time to provide, even for the c:\windows where the c:\windows results were expected to be almost instantaneous since they are already indexed by the Everything-TC instance.

Did TC combined its traditional search with Everything's -instance results? (adding c:\*.* from the TC search and c:\windows\*.* from Everything. EDIT Now that I think of it. I remember that TC searches sometimes include duplicate results (same path/filename twice). So maybe?

Did TC used the wrong instance? ie reverting to the default Everything where no index were pre-built. First thing I checked is if TC forced the creation of a default Everything.ini which would have being a smoking gun for calling the wrong instance. But there were no everything.ini on the test computer. So I can't tell for sure either.

I'll have to try toying with ED: and EV: to dig further. But how hard should it be to use a targeted Everything -Instance?

I'm that close ->"<- to adopt the "tuska" way. ie make sure TC uses the default Everything settings and instance.
(although 1.5A no longer have a default unnamed instance. If the user doesn't specify the instance, 1.5A name it for you "1.5A". That's why Christian said UseEverythingInstance= has to be set to 1.5A if Everything 1.5A was used for tests. Then we are back at dealing with -instance. It hurts behind my eyeballs).

[AntonyD]

I hope Mr.Ghisler will bring a lot more explanation to the logic of his code that is triggered by the search(internal + standalone).
Because for me, too, although the utility works by default in a single instance, a strange slowdown occurs, despite the fact that
the basic code of operation was described just above - sending a WM_message! that is, the response was expected almost instantly!
Considering that what we are looking for has been indexed, the utility does not slow down, there is enough memory.
BUT! the result was obtained as if the Total was doing the search itself - without accessing the utility.

[Horst.Epp]

2AntonyD
When you enable or disable the Everything option
and you don't see a big difference searching for some file deep inside the Windows tree
you have a complete wrong TC and/or Everything setup.
Without the Everything option you can see how TC travels the sub-dirs
in the other case it takes max 2 seconds for the full results.

[tuska]

Well, now I'm dropping out of this topic for the second time, but this time probably for good.

OK, never say never again.

2cmd4ever

What I know for sure: TC didn't limit the results to the -Instance scope I asked and expected when I checked the Everything box.
But where the results came from? That I don't know for sure either.

To figure out the reasons, you'd have to provide a very detailed description.
Similar to what I wrote in my previous post.

Did TC even used Everything for the results? It took a certain amount of time to provide,
even for the c:\windows where the c:\windows results were expected to be almost instantaneous
since they are already indexed by the Everything-TC instance.

There could be several reasons for this, such as the number of files, duplicate indexing (1x NTFS, 1x Folders), etc.
To investigate this, however, we would need to know the exact settings.
That has nothing to do with this topic, though.
You can start a separate thread in the English forum, providing all the relevant details.
Then perhaps someone can help you with this.

Did TC combined its traditional search with Everything's -instance results?

No, not in Everything 1.4.

In Everything 1.5, a file content search can be defined as either indexed (fast search results) or
unindexed (slow search results). You could view this as a “combination.”

What matters is the search query in TC (or in Everything); there is no combination of search results from TC and EV.

(adding c:\*.* from the TC search and c:\windows\*.* from Everything.

Example:
Search for: *.*
Search in: c:;C:\Windows

The TC search query ev:C: includes C:\Windows.
The TC search query c:\*.* includes C:\Windows.
The TC search query C:\Windows\*.* includes only C:\Windows.
The TC search query c:\*.* includes folders and files from drive C:.
The TC search query c:\*.*;C:\Windows\*.* includes folders and files from drive C: AND C:\Windows.

EDIT Now that I think of it.
I remember that TC searches sometimes include duplicate results (same path/filename twice).

This indicates that indexing has been defined twice:
Once under Indexes > NTFS AND again under Indexes > Folders.

If this is indeed duplicate indexing, remove the entry under Indexes > Folders.

Did TC used the wrong instance? ie reverting to the default Everything where no index were pre-built.
First thing I checked is if TC forced the creation of a default Everything.ini
which would have being a smoking gun for calling the wrong instance.
But there were no everything.ini on the test computer. So I can't tell for sure either.

Without a detailed example, I, at least, cannot comment on this.

I'm that close ->"<- to adopt the "tuska" way. ie make sure TC uses the default Everything settings and instance.

Good way.
Using additional Everything instances is of course possible (as I have been doing for years).

(although 1.5A no longer have a default unnamed instance.
If the user doesn't specify the instance, 1.5A name it for you "1.5A".
That's why Christian said UseEverythingInstance= has to be set to 1.5A if Everything 1.5A was used for tests.
Then we are back at dealing with -instance. It hurts behind my eyeballs).

There's a really good workaround ... (File “NO_ALPHA_INSTANCE” (without the file extension).
This option was made available by the Everything author at the time.

UseEverythingInstance= is NOT required in this case!
Everything=Path\To\Everything.exe == still highly recommended!

I've already provided some tips in various places in this post, some of them in my signature.

Everything for beginners - GoogleTranslate German -> English
- Back up Everything 1.4(!)
- Point 0. Everything 1.4: Uninstalling Everything
- Point 1. Download: Files from Google Drive
...

The initial setup takes some time for evaluating options, but I haven’t heard from anyone who regrets making the switch.
45,675 visits since February 21, 2026, which averages out to about 600 visits per day (the peak was around 1,200 visits per day).

With this migration option to 1.5a, there is likely to be only one optional, minimal step remaining with regard to
Everything 1.5 Beta: Delete the file “NO_ALPHA_INSTANCE” (without the file extension) in the Everything program directory.

It's up to you.

PS:
If your question isn't specifically about “UseEverythingInstance,...” but rather about Everything in general,
please post it as a separate thread.

PPS:
Please familiarize yourself more thoroughly with the topic before posting any further comments here.

It’s important not to make general statements, but to provide detailed examples, such as:
What steps did you take, what settings did you use, what result did you get, and what result did you expect.

[cmd4ever]

2tuska You are making some valid points and I when I read your stuff I also feel to return the favor with recommending you deepen your knowledge of what is going on here. But this isn't a p*ing contest.

So to your valid point and sticking to the topic at hand.
I ran a diff between my Everything-TC.INI (1.4.1 mind you) and the most plain vanilla Everything.ini possible (run Everything for the fist time and closed it)

Everything-TC.ini (Plain Vanilla Everything.ini value)
hide_empty_search_results=1 (0)
auto_include_fixed_volumes=0 (1)
rename_select_filepart_only=1 (0)
date_descending_first=1 (0)
size_descending_first=1 (0)
index_folder_size=1 (0)
sort=Path (run count)
sort_ascending=1 (0)
ntfs_volume_includes=0 (1)
folders="C:\\Windows" ()
folder_monitor_changes=1 ()
folder_buffer_size_list=65536 ()
folder_rescan_if_full_list=0 ()
folder_update_types=2 ()
folder_update_days=0 ()
folder_update_ats=3 ()
folder_update_intervals=6 ()
folder_update_interval_types=1 ()

In order to have my Everything-TC instance do what I want, I had to set folders="C:\\Windows" and ntfs_volume_includes=0. I provided the other differences for sake of integrity and transparency so I cannot be blame I don't know what I'm doing here.

I already told which parameters I used with Everything= UseEverythingInstance=

After your tips and reading a little further about EC: Look in content EV: Use everything...

Case 1: My instance is already running when I launch TC.
I ALT-F7 searched with EV: *.* and TC gave me the c:\windows tree. Yeah.

Case 2: My instance isn't running when I launch TC (remember, I now agree to feed all the parameters to the Everything= and Set UseEverythingInstance= to my instance, )
I ALT-F7 searched with EV: *.* and TC gave me the the full c:\*.* Booooooo.
Yet the process properties shows it was launched by TC with "C:\Program Files\Everything\Everything.exe" -instance TC -startup

Can someone tells me what is the purpose of [X]Everything checkbox in the ALT-F7 search tool? Cause I could of swear it had something to do with Everything. Just like tuska said, when entering EV: in the Search For field, it automatically check the useless [X]Everything. No offense, but if I check the said box. It would have been nice for TC to understand I'm looking for Everything results.

We are getting closer. TC use the instance properly WHEN 2 conditions are met:
1) The instance was already running prior to TC being launched
2) EV: Must be explicitly entered EVEN if the [X]Everything checkbox was checked.

The question remaining. Why TC can't use my instance when launched by TC itself.

PS:(I forgot setting CTRL-F to Execute ALT-F7, force of habit with Salamander, so earlier when I wrote CTRL-F, I meant ALT-F7)

[cmd4ever]

More info:

My instance is not running.
If I run TC without admin rights it doesn't open Everything;

If I run TC with as admin, it opens Everything but does not use my Instance (although the process was clearly launched with the - instance and -startup). Also the Everything process launched by TC is windowless. So I cannot interact with it directly (to inspect). But if I add -debug in the Everything= then I can bring up the very chatty debug console.

If I start a generic Everything instance prior to TC, TC will still launch Everything will all the parameters but ALT-F7 does not use the Instance

When I close TC, it does not close the windowless Everythying process it launched.

TC does not communicate with Everything as expected in all cases where TC launched the Everything process.
But if the Everything-TC instance was running prior to launch TC, then TC interact with it as it should. (As long as EV: is explicitly included in the search string.)

Additional Info.
When I uncheck Everything in Configuration/Operation/Calculate space occupied by sub-directories
Then If I launch TC not as admin and ALT-F7, then TC brings back the old Everything is not installed popup.
But If I launch TC as admin and ALT-F7 and then check [X]Everything, TC Starts the Everything process with the proper command lines but TC is not able to communicate with it and circle with the progress bar waiting for Everything to react.
Also if enter EV: *.* and launch the search without checking the [ ]Everything box. It brings back all c:\*.* without launching the Everything Process.

I wouldn't even know where to start to debug this.

Recap:
Depending if [ ]Everything is checked or not for Configuration/Operation/Calculate space occupied by sub-directories affect how ALT-F7 goes.
Depending if the Everything instance is running or not prior to launching TC also has an effect on how things goes.
Depending if TC run as admin or not has an effect.
Depending if ALT-F7 box is manually checked or not as an effect.

Nothing in there seams to relate to Everything operations itself. Since once configured like I want it to be. Everything behaves exactly how I expect when I interact with it.

There is ONE single path for success (apart from running Everything as a service without instances)
1) Have the wanted Everything instance running prior to Launch TC
2) Have [X]Everything checked for Configuration/Operation/Calculate space occupied by sub-directories
3) Specify EV: in the ALT-F7 search box

[petermad]

If I run TC without admin rights it doesn't open Everything;

Not confirmed Here it opens fine without TC with admin rights (I usually never start TC elevated) - Tested with both EVerything 1.4 and 1.5a

If I run TC with as admin, it opens Everything but does not use my Instance (although the process was clearly launched with the - instance and -startup). Also the Everything process launched by TC is windowless. So I cannot interact with it directly (to inspect). But if I add -debug in the Everything= then I can bring up the very chatty debug console.

Not confirmed. Here TC opens and uses the instance it is configured for, and the launced Everything instance has a window to show Tested with both EVerything 1.4 and 1.5a

If I start a generic Everything instance prior to TC, TC will still launch Everything will all the parameters but ALT-F7 does not use the Instance

Not confirmed, Here - if Everything is started prior to TC without any -instance, then TC launches the instance configured in wincmd.ini and uses it. Tested with both EVerything 1.4 and 1.5a

When I close TC, it does not close the windowless Everythying process it launched.

It has never been claimed that TC would or should do that!

[Horst.Epp]

2cmd4ever
I can fully confirm what petermad said in his last response.
Something is wrong with you're Everything configuration.
Install the service and run it not as admin as suggested.

[ghisler(Author)]

I haven't changed anything regarding Everything in TC 11.57 final, for me it works as it should.

[cmd4ever]

2petermad
Tested with Windows 11 or 10? UAC enabled or not?

I'm on 25H2 26200.8246 With UAC enabled (second level from the top). I pulled my Everything settings 1.4.1's pants down for you guys. You see EXACTLY what my INI file is. Do you see something special there? Besides the fact that it is a portable installation that doesn't run as a service. I use it point in time. Which is totally legit as far as Everything goes.

Can you compare your Everything-Instance.ini with a Plain Vanilla portable Everything.ini file and show it to us?
(drop the Everything portable files in a folder, Run Everything.exe once. Do nothing and close it. That will give you an virgin Everything.ini file baseline, as you can see, my test instance has very few tweaks. It's basically one folder tree c:\windows and no NTFS volume)

Now if TC has special requirements to work with Everything instances. This is something else.

[tuska]

I also feel to return the favor with recommending you deepen your knowledge of what is going on here.

Good point
I hope I can still manage it (I am just a hobby user).

I can answer some of your questions or comments below.

Case 1: My instance is already running when I launch TC.

Search for: ev: ... in Total Commander

Search results:
Confirmed: OK: TC displays search results only for the C:\Windows folder indexed in Everything 1.4.
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺

Case 2: My instance isn't running when I launch TC
(remember, I now agree to feed all the parameters to the Everything= and Set UseEverythingInstance= to my instance, )
I ALT-F7 searched with EV: *.* and TC gave me the the full c:\*.* Booooooo.
Yet the process properties shows it was launched by TC with "C:\Program Files\Everything\Everything.exe" -instance TC -startup

Settings: Everything instance running/not running

Code: Select all

ONLY Everything instance "TC" available! (One Everything instance!)
Neither Everything 1.4 nor TC 11.57 was launched as an administrator.

Everything Service: "Everything (TC)" running -> Named instance ==  my MAIN instance(!) - Task Manager > Processes: 1.4 MB

C:\Everything\Everything_1.4\TC\Everything-TC.ini
Options > Everything (TC) - 1.4.1.1032 -> Indexes > Folders: C:\Windows

Button in TC with command: C:\Everything\Everything_1.4\TC\everything.exe -instance "TC" -startup

wincmd.ini - [Configuration]
Everything=C:\Everything\Everything_1.4\TC\everything.exe -instance TC
UseEverythingInstance=TC

- EV instance "TC" closed -> wincmd.ini [Configuration] UseEverything=0
- TC closed
- TC startet
- ALT-F7
- Search for: ev: ... in TC (Find Files (separate)) --> if “ev:” is used, the “Search in:” field is ignored(!)).
  ☐ 'Everything' Not checked, because EV 1.4 was not started -> wincmd.ini [Configuration] UseEverything=0
- Press the button "Start search"
  This message may appear briefly: "'Everything’: Main program is busy, please wait!"
- 'Everything' was launched in the background, so this option was checked immediately AND
  in wincmd.ini - [Configuration], the value was changed to: UseEverything=1
  Checking or unchecking the ‘Everything’ option allows a user to choose whether or not to use the ‘Everything’ tool
  during a TC search query. This should be self-explanatory to users.
- Search results:
  Since the TC parameter `ev:` was used (to integrate Everything into the TC search query)
  the search results only displayed files and folders from the C:\Windows folder indexed by Everything.
I'm happy with the test results!

We are getting closer. TC use the instance properly WHEN 2 conditions are met:
1) The instance was already running prior to TC being launched
2) EV: Must be explicitly entered EVEN if the [X]Everything checkbox was checked.

Re 1) This statement is contradicted by the previous test result,
since the Everything instance was closed and was only launched automatically in the background by the TC search query.

re 2) No.
If the TC parameter `ev:` is used in a TC search query, the search in TC is performed on the drives indexed by Everything.

If the “Everything” option is checked in Total Commander -> ‘Everything’
and the Total Commander parameters “ed:” or “ev:” are NOT used in the search query,
then the search query is performed using Total Commander's internal search.

- If 'Everything' is checked - without prefix ed: - then the search criteria of TC (with the support of 'Everything') apply,
i.e. you still get the search result much faster than if 'Everything' is not checked.

The question remaining. Why TC can't use my instance when launched by TC itself.

I'm trying to figure that out - but I still need to run a few more tests...

[AntonyD]

I haven't changed anything regarding Everything in TC 11.57 final, for me it works as it should.

You did not answer our questions and the description of the complex and unclear situations that we described in our posts.

An explanation in pseudocode is needed about HOW the work in the dialog for searching for the Total itself and
the connected utility is implemented.
Taking into account and WITHOUT taking into account the presence of the suffixes ev:/ed: in the search string.

You can see that people are already starting a full debugging of the behavior of your program's code in an attempt
to find and build a complete chain of logic of behavior. They are trying different interaction options — and settings.
You could save everyone time by giving a complete overview of your code in a pseudo-block algorithm from the start.

And most importantly, the utility should be considered in an exclusively portable version for this bug.
No installation and no services in the autorun!
That is, only the case when Everything is launched exclusively either by Total Commander or by the user!
And preferably in admin mode.

[petermad]

The tests I refer to here viewtopic.php?p=483715#p483715 was made with Everything NOT installed as service (as I usually do), and with Everything running as administrator (1.4) and running indexing process as administrator (1,5a)

Windows 10 and 7, UAC is standard setting.