Everything Service Disconnected

[therube]

Everything Service Disconnected
I got that, out of the blue, & with no understandable reason?



IT'S THE DIRECTORY NAME !!!!!!!
if DIRNAME is... is what... is what, is what is what ... ???????



C:\DEV\Locate\DUP.from.KKK\KKK-ro\, containing:
Everything.exe
GO.bat ---> cmd /c start .\everything.exe -instance DUP.from.K -read-only -debug
result: 2-FAIL

DEL *.ini (so no .ini)
REN C:\DEV\Locate\DUP.from.KKK\KKK-ro\ -> C:\DEV\Locate\DUP.from.KKK\KKK-rox\
GO.bat ---> cmd /c start .\everything.exe -instance DUP.from.K -read-only -debug
result: 6-WORKS



ALL I DID was to change the DIRNAME where Everything was "installed" (Everything.ZIP, so
all i did was to change the dirname where Everything was "placed in").


Changing the directory name would result in Everything either being able to
or not being able to connect to the Service.


Nothing else made a difference - not .ini, not .db (all ESDb2's), not run*, not search*,
not session*, not omit*...

All default settings (i.e., no pre-existing .ini) [& so too, IPC is at its' default].

Is Service holding something open from the GUI, such that a dirname change, with the
same Instance name, causes Disconnected state?


Win7 x64
Everything 1.5.0.1404a (x86)


(that's the short story.
the long story is MUCH longer .)



so i copied an existing Instance, complete,
(& i used Everything to rename all the associated file names, their instance names,
to a new, "unique" instance name, so as to not conflict with existing...)

after that, problems ensued, specifically:

> ntfs monitor read error 5 retrying in 30 seconds...
> Service: 2 (disconnected / installed and not running)


& with that, nothing was making sense
all my existing instances were working correctly
i could close & reopen existing, & they continued to work

but this "new" instance was failing, & all other subsequent new instances too were failing
& that was making no sense, disconnected


(on the fails) Indexes | NTFS
"fixed" volumes, all show as "Access denied: Install the Everything service..."
"removable" volumes (USB), do not show that (error) message


Service:
Started: a month ago (06:34:48 PM 12/22/2025) [per System Informer]

Event Viewer: 12/22/2025 The Everything (1.5a) service entered the running state.
A service was installed in the system.

Service Name: Everything (1.5a)
Service File Name: "C:\DEV\Locate\15.1404\Everything.exe" -svc
Service Type: user mode service
Service Start Type: auto start
Service Account: LocalSystem


nothing is making sense
i create all kinds of new instances, in a single directory as it was, & most i open
either -read-only or -no-auto-include, no existing nothing, except Everything.exe
& they are all failing (2-disconnected)
(instance names; abc, doobe, MULE.MULE, xxx, zzz, closeYELLOW...)


< computer goes to sleep >
< i go to sleep >
< next day >


Quit (MULE) - an existing, working instance
COPY (MULE) -> (MULE - Copy)
OPEN (MULE - Copy) ---> 6 (connected) - works - WHY ?
[i did NOT change the Instance name, only copied the directory itself, & opened with
the same -instance name (MULE)]
Quit (MULE - Copy)


then i fire up one of the above no making sense instances, (zzz), as it happened to
be, & ... guess what

6 (connected)

& yet yesterday, the very same .exe, very same .ini, very same command line - failed
& i'm like, WHY? one day it fails & the next it works?


i'll note that even though (at this point) i'm still 6 (connected),
clicking on a Index | NTFS volume (letter), on that /initial/ click, of a particular volume letter,
Debug Console still shows something like:
> open volume \\?\Volume{...bd601c5ecf5d}
> CreateFileW(): GetLastError(): 5: Failed to open volume \\?\Volume{...}
> opened ffffffff 0.010594
^--- this on a Fixed drive, & while 5: Failed, it's immaterial, as it will work
maybe that is expected?

> open volume \\?\Volume{...}
> opened 00000370 0.004266
^--- this on a removable drive (USB), it simply "opens", no Failed message like with a Fixed volume
maybe that is expected?


so what changed? nothing that i'm aware of.
so why did doing nothing different from one day to another, have different outcomes?

as Instance (zzz) was now working
i go back to (DUP.from.KKK), figuring that too will now be working?
NOPE?

& again i'm totally confused, nothing making sense. some (new) Instances are working, some not.


& i think well maybe it is this or that or the other, so i start whittling down, & still nothing
is making sense. & at some point, there is nothing left to whittle down to - except for the
directory, the directory name.



(i'll spare you the long story as it is MUCH longer .)



(i messed around with IPC= 1,2,3 in .ini, & not that i know what they do nor even if 1,2,3 are
correct, but that too was to no avail.)


Win7 x64, Everything .1404 (x86)
.


.

Everything - changing instalDir name can cause ntfs monitor read error 5, disconnected.png (88.3 KiB) Viewed 6021 times

[harryray2]

Not sure if this helps, but when I was running Windows 7, I was having problems with the Everything service after upgrading to a certain version (I can't remember which version of Everything), but after upgrading to Windows 11, the problem disappeared.

[void]

Could be a service crash?
Please check eventvwr for any errors with:
The Everything Service service terminated unexpectedly.

Please enable mini crash dumps for Everything:

• In the Registry Editor, navigate to:

  Code: Select all

  HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

• Create a new key called:
  Everything.exe
• Navigate to:

  Code: Select all

  HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Everything.exe

• Create a new dword value called:
  DumpType
• Set the value data to:
  2
  
  (2 = mini crash dump)
• Create a new dword value called:
  DumpCount
• Set the value data to:
  3
• Create a new expandable string value called:
  DumpFolder
• Set the value data to:
  C:\DEV\Locate
  
  --wait for Everything to be disconnected from the Service again.
• Please upload the dmp files from C:\DEV\Locate in a bug report.

Renaming the folder shouldn't matter.
Launching a fresh instance of Everything will restart the Everything Service.
Where's your Everything.exe for the Everything Service located?
-Right click the Everything.exe running as SYSTEM in the task manager and click Open Location.
-Please make sure you are running the latest version for the Everything Service.

[therube]

check eventvwr

Pretty sure my search was "Everything" & (noted above), 12/22/2025 The Everything (1.5a) service entered the running state.

Launching a fresh instance of Everything will restart the Everything Service.

Well, Service has been up & running since December. (Computer has been up & running since at least December).
Existing Instances, at least 2, probably 3, maybe 4, have also been up since December.

So in that respect, launching a new Instance should simply piggy-back on the already running Service, no?

Where's your Everything.exe for the Everything Service located?

(Noted above), Service File Name: "C:\DEV\Locate\15.1404\Everything.exe" -svc,
so in C:\DEV\Locate\15.1404.

What I do, on new Everything version...
Blanket copy 15.1404 (directory) -> "15.1404 - Copy"
Rename "15.1404 - Copy" (directory) to 15.1405
Everything -uninstall-service -instance 15 (& yes I know -instance is superfluous)
- the uninstall itself, I might initiate from within either the .1404 or .1405 directory.

Then, i copy the new Everything.exe (.1405) ( overtop of the existing .1404) in the .1405 directory.
From within .1405 directory, i reinstall the service,
Everything -install-service -instance 15
then, from within .1405, I run Everything,
cmd /c start .\everything.exe -instance 15

Instance 15 (& yes, 15, not 1.5) is my primary Instance, typically always open.

Other instances I typically use, are in their own directories, & done much the same way, except no changes to the Service end - as it already is, by virtue of above. They are named differently, of course, & run simultaneously, opened similarly with the appropriate Instance name. They'll have their own copy of Everything.exe with their "instance" directory, & it is that (separate) copy of Everything.exe that opens the particular instance.

Aside from my main Instance, & my other regularly used Instance, every once in a while, for whatever reason, I fire up a new instance.

Typically, create a directory, copy a copy of Everything.exe into it,
cmd /c start Everything.exe -instance yetanotherinstance
& Everything fires up & ... works.

Sometimes, depending what I'm wanting, I'll simply copy an existing Instance (wholesale), change the Instance naming of the files (such that I end up running a new Instance - otherwise it would simply open the original) & again, it just ... works.

For whatever reason, the other day, it did not work?
No matter what I did, existing .db or not, existing .ini or not, existing .db but new .ini, existing .ini but new .db, nothing I did got things working - always "disconnected", until I renamed the directory itself, & then it (just as always) ... worked.

make sure you are running the latest version for the Everything Service.

AFAIK, I am. Whenever I "install" a new version of Everything, I do as noted above.
Uninstall using the existing version, then install anew using the new version.

Otherwise, I'm not sure how to determine the Service "version" per se.
System Informer does show a "Version number", & that number has not always (necessarily) coincided with the version of the GUI that I am running.

Even now (on a different computer), it shows .1399, yet my GUI is .1400.
(Yes, I am knowingly on an older version - till I get to a point where I'm able to throw in 1404.)
I don't know why that is or if it the "Version number" that System Informer is showing is meaningful?
But an -uninstall-service / -install-service, may or may not change the outcome (what is displayed by System Informer).
This mismatch has only happened, sometimes (& I don't know why it occurs).
.

Everything - Service version vs GUI version.png (40.76 KiB) Viewed 5952 times

.

I'll note, in case it matters:
Service, Image type, i386 (64-bit)
GUI, Image type, i386 (32-bit)

Everything Service's 'Number' may not reflect Everything version

[void]

The service shouldn't just exit on its own.

Please check for any scripts that might be stopping the Everything Service.
eg:
NET STOP "Everything (1.5a)"

Please check for any instances that might have stop_service_on_exit enabled.
This is a machine ini setting and can be set in the Everything.ini in the same location as your Everything.exe

I wonder if its a crash with no report, possible caused by access to a USB device.
Where you adding or removing any USB devices at the time? or writing to a USB device?

So in that respect, launching a new Instance should simply piggy-back on the already running Service, no?

Yes.

I don't know why that is or if it the "Version number" that System Informer is showing is meaningful?

Version 1392 or later will be fine.
Version 1392 and later can connect to the Everything Service running any newer version of Everything.
Older versions will be unable to connect (certificate error)



If you are able to reproduce the issue:
From the Tools menu, under the Debug submenu, click Start Debug Logging...
From the Help menu, click Troubleshooting information.
Close the Troubleshooting information page.
From the Tools menu, under the Debug submenu, click Stop Debug Logging...
---This will open your Everything Debug Log.txt in Notepad.
Please upload this file in a bug report
This log will capture any errors when connecting to the Everything Service.
Showing the troubleshooting information page will trigger a service connection.



edit:
It could be another Everything Service with the same pipe name.
Please check if you have multiple services running.
name pipes are weird, two or more servers can be created, the first server will take the first client, and the second server will take the second client.
Check if the connection is failing ever other time in Help -> Troubleshooting information.

[NotNull]

Without reading all posts:

This seems to me like a rather convoluted way to do this. I remember from previous posts that you had more issues with it.

I think de-coupling your Everyting service from the instances would make it less error prone:

- Create a folder somewhere on your system, for example Everything15_Service
- Copy everything(64).exe to that folder
- Run elevated:

Everything.exe -install_service

Now your service is installed. All 1.5 instances [1] will make use of that service.
(it will be shown in the Options > General as "square-ticked".
You can leave the service running when upgrading your Everything instances.

The service code does not change often, but once in a while you can run:

Code: Select all

sc stop "Everything (1.5a)"
timeout /t 5
copy "c:\path to\newest\everything.exe"  c:\Everything15_Service\
sc start "Everything (1.5a)"

(untested)


FWIW: This is what I use to create new, *temporary* instances.
For example to create a new instance "Test service", run

newinstance "Test service"

and a new Everything instance will be started.
Put newinstance.cmd somewhere in your %PATH%.

(bfore running, change the two SETTINGS to match your own setup).


[1] All NAMED instances; the unnamed 1.5 instance still requires its own service.

NewInstance.cmd

Code: Select all

@echo off & setlocal

::	SETTINGS
	set INSTANCES_FOLDER=T:\
	set EVERYTHING_EXE="C:\Program Files\Everything 1.5a\Everything64.exe"
	



::	Get instance name
	If [%*]==[] (
		Set /P "INSTANCE=Instance naam = "
	) Else (
		Set "INSTANCE=%*"
	)


	set "THIS_INSTANCE=%INSTANCES_FOLDER%\Instance_%INSTANCE%"

:: Go to folder and exit if instance exists
	If exist "%THIS_INSTANCE%\" (
		endlocal & 	cd /d "%THIS_INSTANCE%\" & dir
		goto :EOF
	)


::	FOLDER
	md "%THIS_INSTANCE%"


::	EXE
	copy %EVERYTHING_EXE%  "%THIS_INSTANCE%\"


::	INI
(
	echo [Everything]
	echo run_in_background=0
	echo show_tray_icon=0
) > "%THIS_INSTANCE%\Everything-%INSTANCE%.ini"


::	"SHORTCUT"
	for %%x in (%EVERYTHING_EXE%) do set EXE=%%~nxx

	echo Start "" "%THIS_INSTANCE%\%EXE%" -instance "%INSTANCE%" %%* > "%THIS_INSTANCE%\GO.cmd"


:: RUN
	Start "" "%THIS_INSTANCE%\%EXE%" -instance "%INSTANCE%"
	

[therube]

enable mini crash dumps for Everything

I wasn't getting any crash, or at least any crash .dmp files.
Did I do this correctly?
(Everything itself is not crashing, only some Instances are not connecting to the Service.)

Everything - dump NOT.png
- Service connection is in failed state
(all other simultaneous running instances are fine, are connected)
.

Everything - dump NOT.png (97.91 KiB) Viewed 5757 times

[therube]

Everything - prompt to install Service.png
- prompt to install service
(yet service is installed, is running)
.

Everything - prompt to install Service.png (38.46 KiB) Viewed 5753 times

.
Everything - did nothing more then changed the Directory name and now the Service is there.png
- quit above, rename directory from /rox/ to /ro/, open Everything - WORKS
.

Everything - did nothing more then changed the Directory name and now the Service is there.png (30.14 KiB) Viewed 5753 times

.
Everything - changed the Directory name back and now Service FAILS.png
- quit above, rename directory from /ro/ to /rox/, open Everything - FAILS (again)
.

Everything - changed the Directory name back and now Service FAILS.png (35.54 KiB) Viewed 5753 times

.


*i then -uninstall-service
(i missed taking that screenshot)

Everything - Service uninstalled and a current Instance says rightly no Service.png
- pre-existing, running Instance correctly says the Service is not installed
.

Everything - Service uninstalled and a current Instance says rightly no Service.png (19.22 KiB) Viewed 5753 times

.


Everything - Service re-installed - shows 1404 - 1404a - prior it had been 1404 - 1403a.png
- i've reinstalled the Service
in the shot, note, directory 1404, & the tooltip says
c:/dev/locate/15.1404/Everything.exe
Everything 15.1404a
voidtools

*before i re-installed the Service, the tooltip read:
c:/dev/locate/15.1404/Everything.exe
Everything 15.1403a
voidtools

- before it read 1403a, now 1404a (& i missed that screenshot)
(don't know why it read that way before, or why it reads differently now, nor if it is even
meaningful?)
.

Everything - Service re-installed - shows 1404 - 1404a - prior it had been 1404 - 1403a.png (23.22 KiB) Viewed 5753 times

.
Everything - changed the Directory name back again and again Service FAILS.png
- once again changed the Directory name, & once again Service - FAIL
.

Everything - changed the Directory name back again and again Service FAILS.png (50.82 KiB) Viewed 5753 times

.
Everything - changed the Directory name back again yet another time and NOW the Service WORKS again.png
- & doing nothing more except changing the Directory name back - WORKS
.

Everything - changed the Directory name back again yet another time and NOW the Service WORKS again.png (43.85 KiB) Viewed 5753 times

[therube]

The service shouldn't just exit on its own.

The Service is not exiting, it is simply unavailable, in some circumstances, to certain Instances.

Please check for any scripts that might be stopping the Everything Service.
NET STOP "Everything (1.5a)"

The only time or way the Service would start or stop, would be by me -uninstall-service / -install-service (from a command-line). Otherwise, it is up & running.

Please check for any instances that might have stop_service_on_exit enabled.

Unless that is a defaulted setting, which it is not, then no.
In my /KKK-ro/, /KKK-rox/ examples above, they were initially started with no existing .ini's.
So whatever .ini is used would entirely be at defaults.

Existing Instances, are rarely closed (typically only on an Everything.exe update).
(One particular Instance, -read-only, I'll Quite & re-open... every few days or so. But doing so in no way affects any other Instances.)

And I have never messed with, nor would I (purposely) enable that setting.
(Without looking, cause I can't presently, I'll say that settings is not affecting anything on my end, in any of my Instances.)

I wonder if its a crash with no report, possible caused by access to a USB device.
Where you adding or removing any USB devices at the time? or writing to a USB device?

My original desire, for what was (one of) "KKK" Instances, yes, I probably did add USB device that was not Included in database.

(I copied existing "Instance", wholesale, to "Instance - Copy", renamed Instance name so as to not conflict, so it was unique, then, yes, I probably did, at that point, add a USB device that was not Include in the original "Instance" instance.)

But, in my KKK-ro / KKK-rox, I was opening those either -read-only or -no-auto-include, & in those instances, nothing was being added to the .db, yet, & depending on the directory name - the only change made, I would either be connected to, or disconnected from, the Service.

(Dealing with this), Connected or Disconnected is all I've been (pretty much) paying attention to.
So I'll open an Instance, & immediately go to, Help | Troubleshooting (Alt+H, T) & that tells me (immediately) if I'm connected or not to the Service.

Version 1392 or later will be fine.

Then I'm good.

Please check if you have multiple services running.

No I do not.
In one of the shots above, Everything - Service re-installed - shows 1404 - 1404a - prior it had been 1404 - 1403a.png,
there is a 2.56 MB Everything.exe - which is the Service,
& also a 5.47 MB Everything.exe - which is a GUI Instance (that simply isn't using any RAM).
(& then, 3 other Instances, using even more RAM.)

Check if the connection is failing ever other time in Help -> Troubleshooting information.

Do you mean,
Help | Troubleshooting, & I should see a Disconnected,
followed by,
Help | Troubleshooting, & I should see a Connected,
or something along those lines?
(That is a possibility?)

I think de-coupling your Everyting service from the instances

That is what I do, basically.
Service is only ever -install-service / -uninstall-service from within the current Everything versions "instalDir" (though that directory name changes with any Everything update, so 1404 ... 1405 ...) but it will be done from there.

All other Instances are (typically) run from within their own "Instance Directories", with unique Instance names, & are never used for -install-service / -uninstall service.

When Everything updates, I -uninstall-service, then copy current Everything.exe into/over top of existing Everything.exe in all of my "Instance Directories".

So the Service is removed, all Everything.exe are updated in all "Instance Directories", then the Service is Started, & then I go about opening the GUI of each Instance.

This is what I use to create new, *temporary* instances.

Essentially what I do, though I go about it a bit differently, more manually, but it works.
Typically create a directory, anywhere, any name.
Copy Everything.exe into it,
Create a .bat file (typically "go.bat") typically like,
cmd /c start Everything.exe -instance <InstanceName>
& hit, GO!

If I copy an existing Instance, I rename the copied directory, rename the "instance names" of the files within (again, I use Everything itself to do that), & change the go.bat <InstanceName> to the revised Instance name. GO!

So if existing Instance name was "MULE", & I wanted it named ELUM, I simply
Everything.exe -rename *-MULE*
which loads only files that are <InstanceName> related (where the Instance is MULE)
then simply,
Old Format: -MULE
New Format: -EULM
OK. Done.

[therube]

If you are able to reproduce the issue

Sure can.

[therube]

Debug logs sent.


-


Copy Everything.exe into C:\DEV\Locate\DUP.from.KKK\KKK-rox\ (& otherwise, empty)
Everything.exe -read-only
Save Debug information
Quit

Copy Everything.exe into C:\DEV\Locate\DUP.from.KKK\KKK-rox\ (& otherwise, empty)
Everything.exe -read-only
Save Debug information - Verbose
Quit


Rename directory from \...-rox\ to \...-ro\


Copy Everything.exe into C:\DEV\Locate\DUP.from.KKK\KKK-ro\ (& otherwise, empty)
Everything.exe -read-only
Save Debug information
Quit

Copy Everything.exe into C:\DEV\Locate\DUP.from.KKK\KKK-ro\ (& otherwise, empty)
Everything.exe -read-only
Save Debug information - Verbose
Quit


Only difference is the directory name change

Result, /rox/ - FAIL
Result, /ro/ - WORKS


(& i take it that Debug + Verbose provides no additional meaningful information)

(& through all tests, Service is/was installed, is/was running,
in 4 other existing Instances, being run simultaneously,
& there exists only this 1 Everything Service)

-

Showing the troubleshooting information page will trigger a service connection.

(Not that I know, but) not sure if it did?

But clicking on a Index | NTFS Volume (letter) probably did?
So I'll upload to you those associated reports...
.

The attachment Everything - Debug Log - Good vs FAIL to connect to Service.png is no longer available

.

The attachment Everything - Debug Log - Good vs FAIL to connect to Service + NTFS.png is no longer available

.

The attachment Everything Debug Log-1.5a-FAIL-no-existing.ini.txt is no longer available

The attachment Everything Debug Log-1.5a-GOOD-no-existing.ini.txt is no longer available

Everything - Debug Log - Good vs FAIL to connect to Service.png (40.23 KiB) Viewed 5646 times

Everything - Debug Log - Good vs FAIL to connect to Service + NTFS.png (69.69 KiB) Viewed 5646 times

[void]

Thank you for the logs.

The service is running, but I think the service is booting the client on connection.

I am not sure why at this stage..



Service debug logs might also help:

• In the instance that fails to connect to the service:
• In Everything, Press and hold down SHIFT, from the Tools menu, under the Debug submenu, click Start Service Debug Logging.
• Release the SHIFT key.
• From the Help menu, click Troubleshooting information.
• Press and hold down SHIFT, from the Tools menu, under the Debug submenu, click Stop Service Debug Logging.
  ---This will open your C:\Windows\Temp\Everything Service debug Log.txt in Notepad.
• Release the SHIFT key.
• Could you please upload this file in a bug report.

These logs will show if the service is booting the client.



Please try the following:

• From the Start menu, search for:
  regedit
• Right click Registry Editor and click Run as administrator.
• In the Registry Editor, navigate to:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies
• Create the following key:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools
• Create the following key:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools\Everything
• In this new key, on the right, create a new DWORD value.
• Set the value name to:
  service_allow_untrusted_connections
• Set the value data to:
  1

Restart the Everything Service.
Does the issue persist?

[therube]

Service debug logs might also help:

Actually, they won't.
Because if you can't attach to the Service (in the instance where the -Instance gives a Service is Disconnected), you can't debug it.

Though in a case where you can connect to the service, then you can do that.
(So I've thrown that up.)

Code: Select all

2026-02-11 20:39:53.351: Everything 1.5.0.1404a (x86)
2026-02-11 20:39:53.351: OS: Windows NT 6.1 7601 (x64)
2026-02-11 20:39:53.351: Admin: 1
2026-02-11 20:39:53.351: Service: 1 (connected / installed and running)
2026-02-11 20:39:53.351: Command line: -svc
2026-02-11 20:39:53.351: Binary: C:\DEV\Locate\15.1404\Everything.exe
2026-02-11 20:39:53.352: Profile: C:\DEV\Locate\15.1404\Everything-1.5a.ini
2026-02-11 20:39:53.352: Database: C:\DEV\Locate\15.1404\Everything-1.5a.db
2026-02-11 20:39:53.352: Instance: 1.5a
2026-02-11 20:39:53.352: 
2026-02-11 20:39:53.352: Config:
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 44
2026-02-11 20:39:53.352: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-11 20:39:53.352: 
2026-02-11 20:39:53.352: Policy:
2026-02-11 20:39:53.352: 
2026-02-11 20:39:53.352: Plugins:
2026-02-11 20:39:53.352: 
2026-02-11 20:39:53.352: client 16 00000404 0 1 0 ffffffff
2026-02-11 20:39:53.352: ntfs monitor count: 10
2026-02-11 20:39:53.352: ntfs monitor 0: \\?\Volume{...............................92a24} 2 1 0 0 000003dc 000003d4
2026-02-11 20:39:53.352: ntfs monitor 1: \\?\Volume{...............................4f116} 3 1 0 1000 0000022c 000003e4
2026-02-11 20:39:53.352: ntfs monitor 2: \\?\Volume{...............................e6963} 1 2 0 30000 ffffffff ffffffff
2026-02-11 20:39:53.352: ntfs monitor 3: \\?\Volume{...............................e8464} 1 2 0 30000 ffffffff ffffffff
2026-02-11 20:39:53.352: ntfs monitor 4: \\?\Volume{...............................46a3a} 2 1 0 0 000003e8 000003c8
2026-02-11 20:39:53.352: ntfs monitor 5: \\?\Volume{...............................4da94} 2 1 0 0 000003ec 000003a4
2026-02-11 20:39:53.352: ntfs monitor 6: \\?\Volume{...............................ecf5d} 2 1 0 0 000001e4 000003c4
2026-02-11 20:39:53.352: ntfs monitor 7: \\?\Volume{...............................15d94} 2 1 0 0 00000398 000003b8
2026-02-11 20:39:53.352: ntfs monitor 8: \\?\Volume{...............................da1c3} 2 1 0 0 000003f0 0000038c
2026-02-11 20:39:53.352: ntfs monitor 9: \\?\Volume{...............................4d92e} 2 1 0 0 000003d8 000003a8
2026-02-11 20:39:53.352: refs monitor count: 0
2026-02-11 20:39:53.352: client 46 0000013c 0 1 0 ffffffff
2026-02-11 20:39:53.352: ntfs monitor count: 0
2026-02-11 20:39:53.352: refs monitor count: 0
2026-02-11 20:39:53.352: write pipe 0 8
2026-02-11 20:39:53.352: read pipe 34 52
2026-02-11 20:39:53.352: 16: got command 22 44
2026-02-11 20:39:53.352: client 46 wait 2 0
2026-02-11 20:39:53.352: write pipe 0 288
2026-02-11 20:39:53.352: client 46 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: GetOverlappedResult failed 109
2026-02-11 20:39:53.352: update read failed
2026-02-11 20:39:53.352: server awake
2026-02-11 20:39:53.352: event 1 01a90170
2026-02-11 20:39:53.352: disconnect client 46
2026-02-11 20:39:53.352: client 16 wait 9 1
2026-02-11 20:39:53.352: client disconnected
2026-02-11 20:39:53.352: listen_handle 00000444
2026-02-11 20:39:53.352: pipe listen GetOverlappedResult 996
2026-02-11 20:39:53.352: server wait 2 0
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 44
2026-02-11 20:39:53.352: read pipe 34 52
2026-02-11 20:39:53.352: 16: got command 22 44
2026-02-11 20:39:53.352: write pipe 0 16
2026-02-11 20:39:53.352: client 16 wait 9 1
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 12
2026-02-11 20:39:53.352: read pipe 35 20
2026-02-11 20:39:53.352: 16: got command 23 12
2026-02-11 20:39:53.352: write pipe 0 131
2026-02-11 20:39:53.352: client 16 wait 9 1
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 12
2026-02-11 20:39:53.352: read pipe 35 20
2026-02-11 20:39:53.352: 16: got command 23 12
2026-02-11 20:39:53.352: write pipe 0 65
2026-02-11 20:39:53.352: client 16 wait 9 1
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 44
2026-02-11 20:39:53.352: read pipe 34 52
2026-02-11 20:39:53.352: 16: got command 22 44
2026-02-11 20:39:53.352: write pipe 0 16
2026-02-11 20:39:53.352: client 16 wait 9 1
2026-02-11 20:39:53.352: client 16 awake
2026-02-11 20:39:53.352: pipe read event
2026-02-11 20:39:53.352: data read size 44
2026-02-11 20:39:53.352: read pipe 33 52
2026-02-11 20:39:53.352: 16: got command 21 44
2026-02-11 20:39:53.352: RESUME NTFS 1 3
2026-02-11 20:39:53.352: write pipe 0 8
2026-02-11 20:39:53.353: client 16 wait 9 1
2026-02-11 20:39:54.353: client 16 awake
2026-02-11 20:39:54.353: client 16 wait 9 1
2026-02-11 20:39:55.298: server awake
2026-02-11 20:39:55.298: listen_handle 00000444
2026-02-11 20:39:55.298: client 47 connecting...
2026-02-11 20:39:55.353: client 16 awake
2026-02-11 20:39:55.353: update monitor 1 read: hcjoverlapped 000003e4
2026-02-11 20:39:55.353: READING NTFS 1 9
2026-02-11 20:39:55.353: client 16 wait 10 1
2026-02-11 20:39:55.365: c 01a90170, read buf 01aa0170, write buf 01a90170
2026-02-11 20:39:55.365: client 47 connected
2026-02-11 20:39:55.365: listen_handle ffffffff
2026-02-11 20:39:55.365: client 47 awake
2026-02-11 20:39:55.365: listening...
2026-02-11 20:39:55.365: data read size 0
2026-02-11 20:39:55.365: read pipe 0 8
2026-02-11 20:39:55.365: 47: got command 00 0
2026-02-11 20:39:55.365: write pipe 0 12
2026-02-11 20:39:55.365: connect error 997
2026-02-11 20:39:55.365: server wait 2 0
2026-02-11 20:39:55.365: ReadFile failed 109
2026-02-11 20:39:55.365: update read failed
2026-02-11 20:39:55.365: server awake
2026-02-11 20:39:55.365: event 1 01a90170
2026-02-11 20:39:55.365: disconnect client 47
2026-02-11 20:39:55.365: client disconnected
2026-02-11 20:39:55.365: listen_handle 00000438
2026-02-11 20:39:55.365: pipe listen GetOverlappedResult 996
2026-02-11 20:39:55.365: server wait 2 0
2026-02-11 20:39:56.354: client 16 awake
2026-02-11 20:39:56.354: open volume \\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963}
2026-02-11 20:39:56.354: GetVolumeInformationW \\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963} 3
2026-02-11 20:39:56.354: opened ffffffff 0.000054
2026-02-11 20:39:56.354: open volume 2 ffffffff
2026-02-11 20:39:56.354: update monitor 2 read: hcjoverlapped ffffffff
2026-02-11 20:39:56.354: check journal ids volume ffffffff
2026-02-11 20:39:56.354: DeviceIoControl failed 3 (\\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963}) retrying in 30 seconds...
2026-02-11 20:39:56.354: open volume \\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464}
2026-02-11 20:39:56.354: GetVolumeInformationW \\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464} 3
2026-02-11 20:39:56.354: opened ffffffff 0.000031
2026-02-11 20:39:56.354: open volume 3 ffffffff
2026-02-11 20:39:56.354: update monitor 3 read: hcjoverlapped ffffffff
2026-02-11 20:39:56.354: check journal ids volume ffffffff
2026-02-11 20:39:56.354: DeviceIoControl failed 3 (\\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464}) retrying in 30 seconds...
2026-02-11 20:39:56.354: client 16 wait 10 1
2026-02-11 20:39:57.354: client 16 awake
2026-02-11 20:39:57.354: client 16 wait 10 1
2026-02-11 20:39:58.354: client 16 awake
2026-02-11 20:39:58.354: client 16 wait 10 1
2026-02-11 20:39:59.354: client 16 awake
2026-02-11 20:39:59.354: client 16 wait 10 1
2026-02-11 20:39:59.689: server awake
2026-02-11 20:39:59.689: listen_handle 00000438
2026-02-11 20:39:59.689: client 48 connecting...
2026-02-11 20:39:59.752: c 01a90170, read buf 01aa0170, write buf 01a90170
2026-02-11 20:39:59.752: client 48 connected
2026-02-11 20:39:59.752: listen_handle ffffffff
2026-02-11 20:39:59.752: listening...
2026-02-11 20:39:59.752: connect error 997
2026-02-11 20:39:59.752: server wait 2 0
2026-02-11 20:39:59.752: client 48 awake
2026-02-11 20:39:59.752: data read size 0
2026-02-11 20:39:59.752: read pipe 0 8
2026-02-11 20:39:59.753: 48: got command 00 0
2026-02-11 20:39:59.753: write pipe 0 12
2026-02-11 20:39:59.753: data read size 0
2026-02-11 20:39:59.753: read pipe 101 8
2026-02-11 20:39:59.753: 48: got command 65 0
2026-02-11 20:39:59.753: write pipe 0 12
2026-02-11 20:39:59.753: data read size 0
2026-02-11 20:39:59.753: read pipe 98 8
2026-02-11 20:39:59.753: 48: got command 62 0
2026-02-11 20:39:59.753: write pipe 0 12
2026-02-11 20:39:59.753: ReadFile failed 109
2026-02-11 20:39:59.753: update read failed
2026-02-11 20:39:59.753: server awake
2026-02-11 20:39:59.753: event 1 01a90170
2026-02-11 20:39:59.753: disconnect client 48
2026-02-11 20:39:59.753: client disconnected
2026-02-11 20:39:59.753: listen_handle 00000428
2026-02-11 20:39:59.753: pipe listen GetOverlappedResult 996
2026-02-11 20:39:59.753: server wait 2 0
2026-02-11 20:40:00.354: client 16 awake
2026-02-11 20:40:00.354: client 16 wait 10 1
2026-02-11 20:40:01.354: client 16 awake
2026-02-11 20:40:01.354: client 16 wait 10 1
2026-02-11 20:40:01.814: server awake
2026-02-11 20:40:01.814: listen_handle 00000428
2026-02-11 20:40:01.814: client 49 connecting...
2026-02-11 20:40:01.878: c 01a90170, read buf 01aa0170, write buf 01a90170
2026-02-11 20:40:01.878: client 49 connected
2026-02-11 20:40:01.878: listen_handle ffffffff
2026-02-11 20:40:01.879: client 49 awake
2026-02-11 20:40:01.879: listening...
2026-02-11 20:40:01.879: connect error 997
2026-02-11 20:40:01.879: server wait 2 0
2026-02-11 20:40:01.879: data read size 0
2026-02-11 20:40:01.879: read pipe 0 8
2026-02-11 20:40:01.879: 49: got command 00 0
2026-02-11 20:40:01.879: write pipe 0 12
2026-02-11 20:40:01.879: data read size 0
2026-02-11 20:40:01.879: read pipe 97 8
2026-02-11 20:40:01.879: 49: got command 61 0

---This will open your C:\Windows\Temp\Everything Service debug Log.txt in Notepad.

I'll just note that in my case, %TMP% is not as noted above (as I have ages ago redirected it).
Nonetheless, above does exist, & the report is sent there.
Though as C:\Windows\Temp\ (actually, E:, in my case) is a (Windows) "protected" folder, the
Log does not actually open at all (though does get written). (So I elevate, go there... & get
it.)

(Debug Logs go into %TMP%. Service Debug Logs go into E:\Windows\Temp - in my case.)
Please try the following:

Code: Select all

    regedit
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies
    Create key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools
    Create key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools\Everything
    create a new DWORD value:
    Set the value name to:  service_allow_untrusted_connections
    Set the value data to:  1
    
Restart the Everything Service.

c:/1404/Everything -uninstall-service -instance 15 -> Everything -install-service -instance 15

Does the issue persist?

Success
(Prior, with this directory name, /...-rox/ it would fail to connect.
Now, both -rox & -ro connect.)

Code: Select all

Everything 1.5.0.1404a (x86)
OS:	Windows NT 6.1 7601 (x64)
Admin:	0
Service:	6 (connected / partially installed)
Command line:	-read-only
Binary:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything.exe
Profile:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-1.5a.ini
Database:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-1.5a.db
Instance:	1.5a

Config:
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

If I remove that Registry key, then I FAIL, again.
(I did not remove / reinstall the Service.)
(And remove / reinstall the Service, made no difference, still FAIL without that untrusted Registry entry.)

Now, of course, even though "success", that does not answer the question as to why that is "suddenly"
(if in fact it is actually "suddenly") needed - in some cases?

As in (at a time when) executing Everything from within
C:\DEV\Locate\DUP.from.KKK\KKK-rox\, FAILS (disconnected)
Executing Everything from within
C:\DEV\Locate\DUP.from.KKK\KKK-rox\x\, WORKS (connected)

Both open, running, started seconds apart & 1 works & 1 does not.

Oh.
And in such a case..., with:
Everything1404.exe
Everything1403.exe

Everything1403.exe -read-only, WORKS
Alt+F X
followed by
Everythging1404.exe -read-only, FAILS
Alt+F X

So simply by switching which .exe version I run (Service is left unchanged, .1404), I can generate
a working Instance or a failed (connection) Instance.

So some change between 1404 & 1403, it would seem.


.
Everything Debug Log-1.5a-rox-WORKS with service_allow_untrusted_connections.txt
.

Code: Select all

2026-02-11 21:02:29.537: Everything 1.5.0.1404a (x86)
2026-02-11 21:02:29.538: OS: Windows NT 6.1 7601 (x64)
2026-02-11 21:02:29.538: Admin: 0
2026-02-11 21:02:29.538: Service: 6 (connected / partially installed)
2026-02-11 21:02:29.538: Command line: -read-only
2026-02-11 21:02:29.538: Binary: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything.exe
2026-02-11 21:02:29.538: Profile: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-1.5a.ini
2026-02-11 21:02:29.538: Database: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-1.5a.db
2026-02-11 21:02:29.538: Instance: 1.5a
2026-02-11 21:02:29.538: 
2026-02-11 21:02:29.538: Config:
2026-02-11 21:02:29.538: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-11 21:02:29.538: 
2026-02-11 21:02:29.538: Policy:
2026-02-11 21:02:29.538: 
2026-02-11 21:02:29.538: Plugins:
2026-02-11 21:02:29.538: 
2026-02-11 21:02:29.538: Debug logging started.
2026-02-11 21:02:31.799: COMMAND 40089
2026-02-11 21:02:31.807: WM_ACTIVATE 00000000 08f30654
2026-02-11 21:02:31.807:  lastfocus 041f0bce
2026-02-11 21:02:31.807:  current focus 041f0bce
2026-02-11 21:02:31.807:  current foreground 057511e6
2026-02-11 21:02:31.807:  minimized 00000000
2026-02-11 21:02:33.126: WM_ACTIVATE 00000001 08f30654
2026-02-11 21:02:33.126:  lastfocus 041f0bce
2026-02-11 21:02:33.126:  current focus 056f0582
2026-02-11 21:02:33.126:  current foreground 057511e6
2026-02-11 21:02:33.126:  minimized 00000000
2026-02-11 21:02:33.126: FOCUS 0 
2026-02-11 21:02:33.126: FOCUS restore 041f0bce
2026-02-11 21:02:33.127: FOCUS restore 041f0bce
2026-02-11 21:02:35.634: SYSCOMMAND 0000f095 010c036f
2026-02-11 21:02:38.013: COMMAND 40210

.

Everything Service Debug Log-1.5a-rox WORKS with service_allow_untrusted_connections.txt
.

Code: Select all

2026-02-11 21:05:59.378: Everything 1.5.0.1404a (x86)
2026-02-11 21:05:59.378: OS: Windows NT 6.1 7601 (x64)
2026-02-11 21:05:59.378: Admin: 1
2026-02-11 21:05:59.378: Service: 1 (connected / installed and running)
2026-02-11 21:05:59.378: client 2 awake
2026-02-11 21:05:59.378: pipe read event
2026-02-11 21:05:59.378: data read size 44
2026-02-11 21:05:59.379: read pipe 34 52
2026-02-11 21:05:59.379: 2: got command 22 44
2026-02-11 21:05:59.379: write pipe 0 288
2026-02-11 21:05:59.379: Command line: -svc
2026-02-11 21:05:59.379: client 2 wait 9 1
2026-02-11 21:05:59.379: client 2 awake
2026-02-11 21:05:59.379: Binary: C:\DEV\Locate\15.1404\Everything.exe
2026-02-11 21:05:59.379: pipe read event
2026-02-11 21:05:59.379: data read size 44
2026-02-11 21:05:59.379: Profile: C:\DEV\Locate\15.1404\Everything-1.5a.ini
2026-02-11 21:05:59.379: read pipe 34 52
2026-02-11 21:05:59.379: 2: got command 22 44
2026-02-11 21:05:59.379: Database: C:\DEV\Locate\15.1404\Everything-1.5a.db
2026-02-11 21:05:59.379: Instance: 1.5a
2026-02-11 21:05:59.379: write pipe 0 16
2026-02-11 21:05:59.379: 
2026-02-11 21:05:59.379: Config:
2026-02-11 21:05:59.379: client 2 wait 9 1
2026-02-11 21:05:59.379: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-11 21:05:59.379: client 2 awake
2026-02-11 21:05:59.379: pipe read event
2026-02-11 21:05:59.379: data read size 12
2026-02-11 21:05:59.379: 
2026-02-11 21:05:59.379: Policy:
2026-02-11 21:05:59.379: read pipe 35 20
2026-02-11 21:05:59.379: 2: got command 23 12
2026-02-11 21:05:59.379: 
2026-02-11 21:05:59.379: Plugins:
2026-02-11 21:05:59.379: 
2026-02-11 21:05:59.379: client 2 000001f0 0 1 0 ffffffff
2026-02-11 21:05:59.379: ntfs monitor count: 10
...
2026-02-11 21:05:59.379: refs monitor count: 0
2026-02-11 21:05:59.379: client 8 0000012c 0 1 0 ffffffff
2026-02-11 21:05:59.379: ntfs monitor count: 0
2026-02-11 21:05:59.379: refs monitor count: 0
2026-02-11 21:05:59.380: write pipe 0 8
2026-02-11 21:05:59.380: write pipe 0 131
2026-02-11 21:05:59.380: client 8 wait 2 0
2026-02-11 21:05:59.380: client 8 awake
2026-02-11 21:05:59.380: pipe read event
2026-02-11 21:05:59.380: GetOverlappedResult failed 109
2026-02-11 21:05:59.380: update read failed
2026-02-11 21:05:59.380: server awake
2026-02-11 21:05:59.380: event 1 00921208
2026-02-11 21:05:59.380: disconnect client 8
2026-02-11 21:05:59.380: client 2 wait 9 1
2026-02-11 21:05:59.380: client disconnected
2026-02-11 21:05:59.380: listen_handle 000001e4
2026-02-11 21:05:59.380: pipe listen GetOverlappedResult 996
2026-02-11 21:05:59.380: server wait 2 0
2026-02-11 21:05:59.380: client 2 awake
2026-02-11 21:05:59.380: pipe read event
2026-02-11 21:05:59.380: data read size 12
2026-02-11 21:05:59.380: read pipe 35 20
2026-02-11 21:05:59.380: 2: got command 23 12
2026-02-11 21:05:59.380: write pipe 0 65
2026-02-11 21:05:59.380: client 2 wait 9 1
2026-02-11 21:05:59.380: client 2 awake
2026-02-11 21:05:59.380: pipe read event
2026-02-11 21:05:59.380: data read size 44
2026-02-11 21:05:59.380: read pipe 34 52
2026-02-11 21:05:59.380: 2: got command 22 44
2026-02-11 21:05:59.380: write pipe 0 16
2026-02-11 21:05:59.380: client 2 wait 9 1
2026-02-11 21:05:59.380: client 2 awake
2026-02-11 21:05:59.380: pipe read event
2026-02-11 21:05:59.380: data read size 44
2026-02-11 21:05:59.380: read pipe 33 52
2026-02-11 21:05:59.380: 2: got command 21 44
2026-02-11 21:05:59.380: RESUME NTFS 1 3
2026-02-11 21:05:59.380: write pipe 0 8
2026-02-11 21:05:59.380: client 2 wait 9 1
2026-02-11 21:06:00.380: client 2 awake
2026-02-11 21:06:00.380: client 2 wait 9 1
2026-02-11 21:06:01.380: client 2 awake
2026-02-11 21:06:01.380: update monitor 1 read: hcjoverlapped 0000020c
2026-02-11 21:06:01.380: READING NTFS 1 9
2026-02-11 21:06:01.380: client 2 wait 10 1
2026-02-11 21:06:01.932: client 2 awake
2026-02-11 21:06:01.932: AVAILABLE NTFS 1
2026-02-11 21:06:01.932: data available on ntfs monitor 1
2026-02-11 21:06:01.932: write pipe 3 12
2026-02-11 21:06:01.932: client 2 wait 9 1
2026-02-11 21:06:01.932: client 2 awake
2026-02-11 21:06:01.932: pipe read event
2026-02-11 21:06:01.932: data read size 44
2026-02-11 21:06:01.932: read pipe 34 52
2026-02-11 21:06:01.932: 2: got command 22 44
2026-02-11 21:06:01.932: write pipe 0 352
2026-02-11 21:06:01.932: client 2 wait 9 1
2026-02-11 21:06:01.932: client 2 awake
2026-02-11 21:06:01.933: pipe read event
2026-02-11 21:06:01.933: data read size 44
2026-02-11 21:06:01.933: read pipe 34 52
2026-02-11 21:06:01.933: 2: got command 22 44
2026-02-11 21:06:01.933: write pipe 0 16
2026-02-11 21:06:01.933: client 2 wait 9 1
2026-02-11 21:06:01.933: client 2 awake
2026-02-11 21:06:01.933: pipe read event
2026-02-11 21:06:01.933: data read size 12
2026-02-11 21:06:01.933: read pipe 35 20
2026-02-11 21:06:01.933: 2: got command 23 12
2026-02-11 21:06:01.933: write pipe 0 109
2026-02-11 21:06:01.933: client 2 wait 9 1
2026-02-11 21:06:01.933: client 2 awake
2026-02-11 21:06:01.933: pipe read event
2026-02-11 21:06:01.933: data read size 12
2026-02-11 21:06:01.933: read pipe 35 20
2026-02-11 21:06:01.933: 2: got command 23 12
2026-02-11 21:06:01.933: write pipe 0 73
2026-02-11 21:06:01.933: data read size 44
2026-02-11 21:06:01.933: read pipe 34 52
2026-02-11 21:06:01.933: 2: got command 22 44
2026-02-11 21:06:01.933: write pipe 0 16
2026-02-11 21:06:01.933: data read size 44
2026-02-11 21:06:01.933: read pipe 33 52
2026-02-11 21:06:01.934: 2: got command 21 44
2026-02-11 21:06:01.934: RESUME NTFS 1 3
2026-02-11 21:06:01.934: write pipe 0 8
2026-02-11 21:06:01.934: client 2 wait 9 1
2026-02-11 21:06:02.934: client 2 awake
2026-02-11 21:06:02.934: client 2 wait 9 1
2026-02-11 21:06:03.039: server awake
2026-02-11 21:06:03.039: listen_handle 000001e4
2026-02-11 21:06:03.039: client 9 connecting...
2026-02-11 21:06:03.039: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:06:03.039: client 9 connected
2026-02-11 21:06:03.039: listen_handle ffffffff
2026-02-11 21:06:03.039: listening...
2026-02-11 21:06:03.039: connect error 997
2026-02-11 21:06:03.039: server wait 2 0
2026-02-11 21:06:03.039: client 9 awake
2026-02-11 21:06:03.039: data read size 0
2026-02-11 21:06:03.039: read pipe 0 8
2026-02-11 21:06:03.039: 9: got command 00 0
2026-02-11 21:06:03.039: write pipe 0 12
2026-02-11 21:06:03.039: ReadFile failed 109
2026-02-11 21:06:03.039: update read failed
2026-02-11 21:06:03.039: server awake
2026-02-11 21:06:03.039: event 1 00921208
2026-02-11 21:06:03.039: disconnect client 9
2026-02-11 21:06:03.039: client disconnected
2026-02-11 21:06:03.039: listen_handle 00000258
2026-02-11 21:06:03.039: pipe listen GetOverlappedResult 996
2026-02-11 21:06:03.039: server wait 2 0
2026-02-11 21:06:03.934: client 2 awake
2026-02-11 21:06:03.934: update monitor 1 read: hcjoverlapped 0000020c
2026-02-11 21:06:03.934: READING NTFS 1 9
2026-02-11 21:06:03.934: client 2 wait 10 1
2026-02-11 21:06:04.934: client 2 awake
2026-02-11 21:06:04.934: client 2 wait 10 1
2026-02-11 21:06:05.934: client 2 awake
2026-02-11 21:06:05.934: client 2 wait 10 1
2026-02-11 21:06:06.934: client 2 awake
2026-02-11 21:06:06.934: client 2 wait 10 1
2026-02-11 21:06:07.934: client 2 awake
2026-02-11 21:06:07.934: client 2 wait 10 1
2026-02-11 21:06:08.392: server awake
2026-02-11 21:06:08.392: listen_handle 00000258
2026-02-11 21:06:08.392: client 10 connecting...
2026-02-11 21:06:08.392: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:06:08.392: client 10 connected
2026-02-11 21:06:08.392: client 10 awake
2026-02-11 21:06:08.392: data read size 0
2026-02-11 21:06:08.392: listen_handle ffffffff
2026-02-11 21:06:08.392: read pipe 0 8
2026-02-11 21:06:08.392: 10: got command 00 0
2026-02-11 21:06:08.392: write pipe 0 12
2026-02-11 21:06:08.392: listening...
2026-02-11 21:06:08.392: connect error 997
2026-02-11 21:06:08.392: server wait 2 0
2026-02-11 21:06:08.392: data read size 0
2026-02-11 21:06:08.392: read pipe 101 8
2026-02-11 21:06:08.392: 10: got command 65 0
2026-02-11 21:06:08.392: write pipe 0 12
2026-02-11 21:06:08.392: data read size 0
2026-02-11 21:06:08.392: read pipe 98 8
2026-02-11 21:06:08.392: 10: got command 62 0
2026-02-11 21:06:08.392: write pipe 0 12
2026-02-11 21:06:08.392: ReadFile failed 109
2026-02-11 21:06:08.392: update read failed
2026-02-11 21:06:08.392: server awake
2026-02-11 21:06:08.393: event 1 00921208
2026-02-11 21:06:08.393: disconnect client 10
2026-02-11 21:06:08.393: client disconnected
2026-02-11 21:06:08.393: listen_handle 0000012c
2026-02-11 21:06:08.393: pipe listen GetOverlappedResult 996
2026-02-11 21:06:08.393: server wait 2 0
2026-02-11 21:06:08.935: client 2 awake
2026-02-11 21:06:08.935: client 2 wait 10 1
2026-02-11 21:06:09.935: client 2 awake
2026-02-11 21:06:09.935: client 2 wait 10 1
2026-02-11 21:06:10.596: server awake
2026-02-11 21:06:10.596: listen_handle 0000012c
2026-02-11 21:06:10.596: client 11 connecting...
2026-02-11 21:06:10.596: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:06:10.596: client 11 connected
2026-02-11 21:06:10.596: listen_handle ffffffff
2026-02-11 21:06:10.596: client 11 awake
2026-02-11 21:06:10.596: listening...
2026-02-11 21:06:10.596: connect error 997
2026-02-11 21:06:10.596: server wait 2 0
2026-02-11 21:06:10.596: data read size 0
2026-02-11 21:06:10.596: read pipe 0 8
2026-02-11 21:06:10.596: 11: got command 00 0
2026-02-11 21:06:10.596: write pipe 0 12
2026-02-11 21:06:10.596: data read size 0
2026-02-11 21:06:10.596: read pipe 97 8
2026-02-11 21:06:10.596: 11: got command 61 0

.

Everything Debug Log-1.5a-ro-also-WORKS with service_allow_untrusted_connections.txt
.

Code: Select all

2026-02-11 21:09:01.112: Everything 1.5.0.1404a (x86)
2026-02-11 21:09:01.112: OS: Windows NT 6.1 7601 (x64)
2026-02-11 21:09:01.112: Admin: 0
2026-02-11 21:09:01.112: Service: 6 (connected / partially installed)
2026-02-11 21:09:01.112: Command line: -read-only
2026-02-11 21:09:01.112: Binary: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything.exe
2026-02-11 21:09:01.113: Profile: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-1.5a.ini
2026-02-11 21:09:01.113: Database: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-1.5a.db
2026-02-11 21:09:01.113: Instance: 1.5a
2026-02-11 21:09:01.113: 
2026-02-11 21:09:01.113: Config:
2026-02-11 21:09:01.113: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-11 21:09:01.113: 
2026-02-11 21:09:01.113: Policy:
2026-02-11 21:09:01.113: 
2026-02-11 21:09:01.113: Plugins:
2026-02-11 21:09:01.113: 
2026-02-11 21:09:01.113: Debug logging started.
2026-02-11 21:09:02.661: SYSCOMMAND 0000f095 010a039b
2026-02-11 21:09:04.805: COMMAND 40089
2026-02-11 21:09:04.812: WM_ACTIVATE 00000000 04581082
2026-02-11 21:09:04.812:  lastfocus 0ba408c8
2026-02-11 21:09:04.812:  current focus 0ba408c8
2026-02-11 21:09:04.812:  current foreground 096e0d2c
2026-02-11 21:09:04.812:  minimized 00000000
2026-02-11 21:09:06.508: WM_ACTIVATE 00000001 04581082
2026-02-11 21:09:06.508:  lastfocus 0ba408c8
2026-02-11 21:09:06.508:  current focus 11880d08
2026-02-11 21:09:06.508:  current foreground 096e0d2c
2026-02-11 21:09:06.508:  minimized 00000000
2026-02-11 21:09:06.508: FOCUS 0 
2026-02-11 21:09:06.508: FOCUS restore 0ba408c8
2026-02-11 21:09:06.510: FOCUS restore 0ba408c8
2026-02-11 21:09:07.552: SYSCOMMAND 0000f095 010f0376
2026-02-11 21:09:11.048: COMMAND 40210

.

Everything Service Debug Log-1.5a-ro-still-WORKS with service_allow_untrusted_connections.txt
.

Code: Select all

2026-02-11 21:10:33.144: client 2 awake
2026-02-11 21:10:33.145: AVAILABLE NTFS 1
2026-02-11 21:10:33.145: data available on ntfs monitor 1
2026-02-11 21:10:33.145: write pipe 3 12
2026-02-11 21:10:33.145: Everything 1.5.0.1404a (x86)
2026-02-11 21:10:33.145: OS: Windows NT 6.1 7601 (x64)
2026-02-11 21:10:33.145: Admin: 1
2026-02-11 21:10:33.145: Service: 1 (connected / installed and running)
2026-02-11 21:10:33.145: Command line: -svc
2026-02-11 21:10:33.145: Binary: C:\DEV\Locate\15.1404\Everything.exe
2026-02-11 21:10:33.145: Profile: C:\DEV\Locate\15.1404\Everything-1.5a.ini
2026-02-11 21:10:33.145: Database: C:\DEV\Locate\15.1404\Everything-1.5a.db
2026-02-11 21:10:33.145: Instance: 1.5a
2026-02-11 21:10:33.145: 
2026-02-11 21:10:33.145: Config:
2026-02-11 21:10:33.145: client 2 wait 9 1
2026-02-11 21:10:33.145: client 2 awake
2026-02-11 21:10:33.145: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-11 21:10:33.145: 
2026-02-11 21:10:33.145: Policy:
2026-02-11 21:10:33.145: pipe read event
2026-02-11 21:10:33.145: data read size 44
2026-02-11 21:10:33.145: 
2026-02-11 21:10:33.145: Plugins:
2026-02-11 21:10:33.145: 
2026-02-11 21:10:33.145: client 2 000001f0 0 1 0 ffffffff
2026-02-11 21:10:33.145: ntfs monitor count: 10
...
2026-02-11 21:10:33.146: refs monitor count: 0
2026-02-11 21:10:33.146: client 17 0000012c 0 1 0 ffffffff
2026-02-11 21:10:33.146: ntfs monitor count: 0
2026-02-11 21:10:33.146: refs monitor count: 0
2026-02-11 21:10:33.146: write pipe 0 8
2026-02-11 21:10:33.146: read pipe 34 52
2026-02-11 21:10:33.146: 2: got command 22 44
2026-02-11 21:10:33.146: client 17 wait 2 0
2026-02-11 21:10:33.146: write pipe 0 288
2026-02-11 21:10:33.146: client 17 awake
2026-02-11 21:10:33.146: client 2 wait 9 1
2026-02-11 21:10:33.146: client 2 awake
2026-02-11 21:10:33.146: pipe read event
2026-02-11 21:10:33.146: data read size 44
2026-02-11 21:10:33.146: read pipe 34 52
2026-02-11 21:10:33.146: 2: got command 22 44
2026-02-11 21:10:33.146: write pipe 0 16
2026-02-11 21:10:33.146: pipe read event
2026-02-11 21:10:33.146: GetOverlappedResult failed 109
2026-02-11 21:10:33.146: update read failed
2026-02-11 21:10:33.146: server awake
2026-02-11 21:10:33.146: event 1 00921208
2026-02-11 21:10:33.146: disconnect client 17
2026-02-11 21:10:33.146: client 2 wait 9 1
2026-02-11 21:10:33.146: client disconnected
2026-02-11 21:10:33.146: listen_handle 000001e4
2026-02-11 21:10:33.146: pipe listen GetOverlappedResult 996
2026-02-11 21:10:33.146: server wait 2 0
2026-02-11 21:10:33.146: client 2 awake
2026-02-11 21:10:33.146: pipe read event
2026-02-11 21:10:33.146: data read size 12
2026-02-11 21:10:33.146: read pipe 35 20
2026-02-11 21:10:33.146: 2: got command 23 12
2026-02-11 21:10:33.146: write pipe 0 131
2026-02-11 21:10:33.146: client 2 wait 9 1
2026-02-11 21:10:33.146: client 2 awake
2026-02-11 21:10:33.146: pipe read event
2026-02-11 21:10:33.146: data read size 12
2026-02-11 21:10:33.146: read pipe 35 20
2026-02-11 21:10:33.146: 2: got command 23 12
2026-02-11 21:10:33.146: write pipe 0 65
2026-02-11 21:10:33.146: client 2 wait 9 1
2026-02-11 21:10:33.146: client 2 awake
2026-02-11 21:10:33.146: pipe read event
2026-02-11 21:10:33.146: data read size 44
2026-02-11 21:10:33.147: read pipe 34 52
2026-02-11 21:10:33.147: 2: got command 22 44
2026-02-11 21:10:33.147: write pipe 0 16
2026-02-11 21:10:33.147: client 2 wait 9 1
2026-02-11 21:10:33.147: client 2 awake
2026-02-11 21:10:33.147: pipe read event
2026-02-11 21:10:33.147: data read size 44
2026-02-11 21:10:33.147: read pipe 33 52
2026-02-11 21:10:33.147: 2: got command 21 44
2026-02-11 21:10:33.147: RESUME NTFS 1 3
2026-02-11 21:10:33.147: write pipe 0 8
2026-02-11 21:10:33.147: client 2 wait 9 1
2026-02-11 21:10:34.147: client 2 awake
2026-02-11 21:10:34.147: client 2 wait 9 1
2026-02-11 21:10:35.147: client 2 awake
2026-02-11 21:10:35.147: update monitor 1 read: hcjoverlapped 0000020c
2026-02-11 21:10:35.147: READING NTFS 1 9
2026-02-11 21:10:35.147: client 2 wait 10 1
2026-02-11 21:10:35.733: server awake
2026-02-11 21:10:35.733: listen_handle 000001e4
2026-02-11 21:10:35.733: client 18 connecting...
2026-02-11 21:10:35.734: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:10:35.734: client 18 connected
2026-02-11 21:10:35.734: listen_handle ffffffff
2026-02-11 21:10:35.734: client 18 awake
2026-02-11 21:10:35.734: listening...
2026-02-11 21:10:35.734: connect error 997
2026-02-11 21:10:35.734: server wait 2 0
2026-02-11 21:10:35.734: data read size 0
2026-02-11 21:10:35.734: read pipe 0 8
2026-02-11 21:10:35.734: 18: got command 00 0
2026-02-11 21:10:35.734: write pipe 0 12
2026-02-11 21:10:35.734: ReadFile failed 109
2026-02-11 21:10:35.734: update read failed
2026-02-11 21:10:35.734: server awake
2026-02-11 21:10:35.734: event 1 00921208
2026-02-11 21:10:35.734: disconnect client 18
2026-02-11 21:10:35.734: client disconnected
2026-02-11 21:10:35.734: listen_handle 00000258
2026-02-11 21:10:35.734: pipe listen GetOverlappedResult 996
2026-02-11 21:10:35.734: server wait 2 0
2026-02-11 21:10:36.147: client 2 awake
2026-02-11 21:10:36.147: client 2 wait 10 1
2026-02-11 21:10:37.147: client 2 awake
2026-02-11 21:10:37.147: client 2 wait 10 1
2026-02-11 21:10:38.147: client 2 awake
2026-02-11 21:10:38.147: client 2 wait 10 1
2026-02-11 21:10:39.147: client 2 awake
2026-02-11 21:10:39.147: client 2 wait 10 1
2026-02-11 21:10:39.486: server awake
2026-02-11 21:10:39.486: listen_handle 00000258
2026-02-11 21:10:39.486: client 19 connecting...
2026-02-11 21:10:39.486: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:10:39.486: client 19 connected
2026-02-11 21:10:39.486: client 19 awake
2026-02-11 21:10:39.487: data read size 0
2026-02-11 21:10:39.487: read pipe 0 8
2026-02-11 21:10:39.487: 19: got command 00 0
2026-02-11 21:10:39.487: write pipe 0 12
2026-02-11 21:10:39.487: listen_handle ffffffff
2026-02-11 21:10:39.487: listening...
2026-02-11 21:10:39.487: connect error 997
2026-02-11 21:10:39.487: server wait 2 0
2026-02-11 21:10:39.487: data read size 0
2026-02-11 21:10:39.487: read pipe 101 8
2026-02-11 21:10:39.487: 19: got command 65 0
2026-02-11 21:10:39.487: write pipe 0 12
2026-02-11 21:10:39.487: data read size 0
2026-02-11 21:10:39.487: read pipe 98 8
2026-02-11 21:10:39.487: 19: got command 62 0
2026-02-11 21:10:39.487: write pipe 0 12
2026-02-11 21:10:39.487: ReadFile failed 109
2026-02-11 21:10:39.487: update read failed
2026-02-11 21:10:39.487: server awake
2026-02-11 21:10:39.487: event 1 00921208
2026-02-11 21:10:39.487: disconnect client 19
2026-02-11 21:10:39.487: client disconnected
2026-02-11 21:10:39.487: listen_handle 0000012c
2026-02-11 21:10:39.487: pipe listen GetOverlappedResult 996
2026-02-11 21:10:39.487: server wait 2 0
2026-02-11 21:10:40.147: client 2 awake
2026-02-11 21:10:40.147: client 2 wait 10 1
2026-02-11 21:10:41.147: client 2 awake
2026-02-11 21:10:41.147: client 2 wait 10 1
2026-02-11 21:10:42.147: client 2 awake
2026-02-11 21:10:42.147: client 2 wait 10 1
2026-02-11 21:10:42.885: server awake
2026-02-11 21:10:42.885: listen_handle 0000012c
2026-02-11 21:10:42.885: client 20 connecting...
2026-02-11 21:10:42.885: c 00921208, read buf 00931208, write buf 00921208
2026-02-11 21:10:42.885: client 20 connected
2026-02-11 21:10:42.885: listen_handle ffffffff
2026-02-11 21:10:42.886: client 20 awake
2026-02-11 21:10:42.886: data read size 0
2026-02-11 21:10:42.886: read pipe 0 8
2026-02-11 21:10:42.886: 20: got command 00 0
2026-02-11 21:10:42.886: write pipe 0 12
2026-02-11 21:10:42.886: listening...
2026-02-11 21:10:42.886: connect error 997
2026-02-11 21:10:42.886: server wait 2 0
2026-02-11 21:10:42.886: data read size 0
2026-02-11 21:10:42.886: read pipe 97 8
2026-02-11 21:10:42.886: 20: got command 61 0

[tuska]

Code: Select all

Admin:   1
Service: 1 (connected / installed and running)

Just out of interest:
Until now, I was of the opinion that such a combination usually causes problems.
However, such a combination occurs frequently in the previous post.

I would appreciate an explanation please.

[void]

Thanks for the latest logs therube,

Admin: 1
Service: 1 (connected / installed and running)

Just out of interest:
Until now, I was of the opinion that such a combination usually causes problems.

These are Everything Service Debug Logs.
This is normal for the Everything Service.
The Everything Service runs as admin and would always have a connection to itself.



Some things to clarify:

When the connection fails, the following is in the client logs:

GetOverlappedResult failed 109

This means the pipe was connected, but later broken (server side closed the pipe)
So a connection to the service is being made, but the service is then closing the connection.

Because if you can't attach to the Service (in the instance where the -Instance gives a Service is Disconnected), you can't debug it.

I completely missed this!
Good thinking for picking this up and using a connected client to start the service debug logging.



If enabling service_allow_untrusted_connections fixes the issue, to me this means the service is seeing the connection as untrusted for the failed connections.
If a connection is untrusted, the service will log:

connection not allowed.

I'm not seeing any

connection not allowed.

messages in the service debug logs.
To me this indicates another service is running.

In Process Explorer, do a search for:

Everything Service

There should be one pipe handle:
Everything.exe 6724 File \Device\NamedPipe\Everything Service (1.5a)




Please check the Everything.exe in C:\DEV\Locate\DUP.from.KKK\KKK-rox has a valid certificate and the digital certificate is OK under Everything.exe -> right click -> Properties -> Digital Signature -> Details -> Digital Signature Information.



The Everything Service will skip the trust check if the client and the service exe are the same.



When the client connects to the service, it does a version check.
There's no messages indicating this fails.
-The service version has not changed for a very long time.



There was no changes to the service (client and server) between 1403 and 1404.

I'll just note that in my case, %TMP% is not as noted above (as I have ages ago redirected it).
Nonetheless, above does exist, & the report is sent there.
Though as C:\Windows\Temp\ (actually, E:, in my case) is a (Windows) "protected" folder, the
Log does not actually open at all (though does get written). (So I elevate, go there... & get
it.)

The service writes to C:\Windows\Temp (not %TEMP%)

[tuska]

Admin: 1
Service: 1 (connected / installed and running)

Just out of interest:
Until now, I was of the opinion that such a combination usually causes problems.

These are Everything Service Debug Logs.
This is normal for the Everything Service.
The Everything Service runs as admin and would always have a connection to itself.

Thanks for the prompt reply!

I'm trying to understand the options, and this is what it looks like when someone changes the setting.
Please see the information in: "Troubleshooting Information".

FROM: Everything Service
TO:      Run as administrator
 

2026-02-13_Everything Service disconnected_Everything as Administrator.png (37.73 KiB) Viewed 5328 times

 
That concludes this matter for me.
--------------------------------------------

On this occasion, I have another question:
I noticed that, for example, when using an instance in Everything 1.5a, a checkbox no longer displays the status
“” Square-checked but “ ⚊ ” Line-checked.

Does the status “” Square-checked even exist in Everything 1.5?

[void]

[▪] square check and [-] dash checked are the same thing.

It's the symbol for the indeterminate value. (it's neither set or unset)

[tuska]

[▪] square check and [-] dash checked are the same thing.

It's the symbol for the indeterminate value. (it's neither set or unset)

Thanks for the information!

[therube]

This means the pipe was connected, but later broken (server side closed the pipe)
So a connection to the service is being made, but the service is then closing the connection.

Again begs the question, Why?

If enabling service_allow_untrusted_connections fixes the issue, to me this means the service is seeing the connection as untrusted for the failed connections.

Ditto, why?

To me this indicates another service is running.

I'll look again, but AFAIK, that is not the case.

Please check the Everything.exe in C:\DEV\Locate\DUP.from.KKK\KKK-rox has a valid certificate and the digital certificate

It should. I simply copy a copy of (the current) "Everything.exe" into a new directory.
I'll check. (And again, I run x86, Everything, .exe, .ZIP, should that matter.

(Looking at what I have here, sure, & not that I know particularly what I'm looking at, but yes, it has the expected Digital Certificate... [expires to soon, too, 05-20-2026].
[In that respect, Code signing: consolidation, monopolies, and price hikes.])

There was no changes to the service (client and server) between 1403 and 1404.

OK.
But, changing the .exe version of (the GUI) Everything(.exe) that I ran did make a difference.
Everything1403.exe connected where Everything1404.exe did not.
Everything the same, only I ran one or the other.
c:\...rox\Everything1403.exe -instance blablabla
c:\...rox\Everything1404.exe -instance blablabla

And again, all this is at the very same time that I do have other Instances, open, running, working, all using the very same Service, & I can even create a subdirectory to \rox\, \rox\x\ & copy Everything.exe into there (c:\...rox\x\) & that opens & connects.

So \rox\ works if I set, service_allow_untrusted_connections, or without that, if i use the GUI .exe of 1403.
\rox\x\ happens to simply work, without service_allow_untrusted_connections, & with GUI .exe of 1404 (or 1403).



(Different system...)

c:/dev/locate/Everything.exe
- version 1400, 1 Service, 1400
Quit Everything
c:/dev/locate/Everything -uninstall-service -instance 15
- no Everything
- copy Everything-1.5.0.1404a.x86.zip -> Everything.exe --> c:/dev/locate/, Overwrite ? -> YES.
c:/dev/locate/Everything -install-service -instance 15
- Service created
cmd /c start "" everything -instance OFFICEMULE
cmd /c start .\everything.exe -instance HOME -read-only -no-auto-include

That's about what I do.

And whatever happens after that, including opening arbitrary Instances, anywhere, anytime, anyhow - that have always "just worked" - until... I cause these recent failures - sometimes.
.
1. Service (1400) & two Instances running (of which 1 is actually running 1404 GUI .exe)
2. here, I'm simply showing one of the GUI's
<I Quit GUI, uninstall service, reinstall service>
3. Service (1404) has updated
4. re-opened two Instances, showing one of the GUI's (& not both are running 1404 GUI .exe)
.

Everything - installation.png (104.51 KiB) Viewed 4983 times

[therube]

In Process Explorer, do a search for: Everything Service

There should be one pipe handle:
Everything.exe 6724 File \Device\NamedPipe\Everything Service (1.5a)

With 6274 being the PID of "services.exe", right?
And #### will be "a number", but not necessarily 6274 (as it would vary depending on the PID that services.exe happened to have obtained).

Everything Service

Everything Service, or simply, Everything ?
(Filtering on), Everything Service, does not return anything.
(Filtering on), Everything, returns both the Service (-svc), & all GUI Instances.

pipe handle

Oh, oh, oh. So you want the Handle, not the Service per se.
And in that case, 'everything service' would be a correct search.
(And I've got to assume ? that there is only 1. [I'll let you know.])

The Everything Service will skip the trust check if the client and the service exe are the same.

Explain?

[therube]

pipe handle

Example.
.

Everything Service - Handle.png (48.68 KiB) Viewed 4978 times

[NotNull]

The Everything Service will skip the trust check if the client and the service exe are the same.

Explain?

When the exe of the service and the exe of the client point to the same file (like c:\folder\everything.exe), there is no need to check the certificate.


Maybe this helps in debugging th issue:
- download pipelist from SysInternals
- In the command Prompt (cmd.exe) run:

Code: Select all

pipelist64.exe | findstr /i Everything

(or pipelist.exe on a 32-bit OS)
What is the output?

[therube]

I'll suppose that the PipeList_101.zip I have on hand, 07/19/2006, suffices .

Code: Select all

C:\DEV\Sysinternals>pipelist | grep -i everything
Everything Service (1.5a)                         2               -1
Everything IPC (OFFICEMULE)                       1               -1
Everything IPC (HOME)                             1               -1

In this case, both (OFFICEMULE) & (HOME) are in their own separate directories, having their own separate Everything.exe's (1404's).

The Service itself was uninstalled/installed from within:
c:/dev/Locate/

(I didn't actually run, yet, the "main" Instance that is also within that directory.)
(Updated to v1.02, PipeList.)

When the exe of the service and the exe of the client point to the same file (like c:\folder\everything.exe), there is no need to check the certificate.

Above, Service installed, started (the GUI .exe, Everything.exe) found within c:/dev/Locate/.

(On my other end would be the "same", except I keep Everything ("main", if you will) versions in their own directories,
so currently, c:/dev/Locate/1404/. Everything is "installed" there, Service is initiated from there. My main instance (15) is started from there. Then any other Instances I run, will be, the GUI will be started from within their own separate directories, started from a 1404 Everything.exe that resides in said directory.)

[therube]

Now, having done what I've described above - today, & today I'm on a different computer, with ES, I getting... NOT?
Not nul either, as I do get a message .

Code: Select all

C:\BIN>es pipelist
Error 8: Everything IPC not found. Please make sure Everything is running.

es.bat:

Code: Select all

@es.ex2 -instance 15  -footer  %*

Code: Select all

C:\BIN>es.ex2 -version
1.1.0.36

I surmise it has to do with above?
I surmise that once I open my "main" Instance (15), ES will "just work"?



YES.

c:/dev/locate/> start "" .\everything.exe -instance 15

Code: Select all

C:\BIN>es pipelist
C:\DEV\Sysinternals\pipelist.exe
C:\LIB\Sysinternals\OLD\PipeList_101.zip
C:\out\PipeList_102 (Sysinternals).zip
C:\DEV\Sysinternals\pipelist64.exe

(Gotta run. I'll see if I can get in, tomorrow...)

OK, ignore, I'm pretty sure.
I run instances (i.e., not "1.5a"), & my batch file was running my "main" instance (15), which ordinarily is always open, only just so happens that I did not open it, now, so that is why my ES was failing.

OK, ignore.

[therube]

Code: Select all

C:\DEV\Sysinternals>pipelist | grep -i everything

Pipe Name                                    Instances       Max Instances
---------                                    ---------       -------------
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1
Everything Service (1.5a)                         2               -1

Now, why (pipelist) Instances (for Everything Service) shows 2
(or what Instances / Max Instances even means, I don't know) ?


<see pics>


getting somewhere, i think...

Code: Select all

1. existing:
C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1
Everything Service (1.5a)                         2               -1

2: C:\DEV\Locate\15.1404>everything -uninstall-service
(i did not include '-instance 15' on the command-line - as i have done, as a matter of course, from the days when it actually meant something [& for no other reason then that])
- Service is gone (as expected)
C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1

3. C:\DEV\Locate\15.1404>everything -install-service
(again, i did not include '-instance 15' on the command-line - as i have done, as a matter of course...)
- Service is back & running (as expected)
- THIS TIME, (pipelist) Instance only shows 1 (where a moment ago, it was 2)
C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1
Everything Service (1.5a)                         1               -1

4. C:\DEV\Locate\15.1404>everything -uninstall-service
(uninstall again, Service is gone, as expected)
C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1

5. C:\DEV\Locate\15.1404>everything -install-service -instance 15
(this time, DO include the -instance <name>, which /should/, should AFAIK, be superflorous, for a long
time now, BUT, this time (pipelist) Instances only shows '1' for the Everything Service)
C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15)                               1               -1
Everything IPC (KKK)                              1               -1
Everything IPC (CEO)                              1               -1
Everything IPC (MULE.1402)                        1               -1
Everything Service (1.5a)                         1               -1

C:\DEV\Sysinternals>

So maybe, from ages ago... what, I have had two (pipelist) "Instances", & one "Everything -svc"?
AND, at the moment, from my last step above, I do NOT have any Handle 'everything service'
& yet, my various Everything Instances are all working, the Service is installed, I do have
Everything.exe \NamedPipe\Everything IPC (InstanceName),
but I do NOT have Everything Service (1.5a) named pipe - or something like that...

So... at this point /rox/ should still be broken? OK... was not expected that. /rox/ IS working
with Everything1404.exe. [I thought it was going to be broken, still.]
(Oops, forgot to include the -no-auto-load or -read-only switch!) (And Everything1403.exe is also
working with /rox/.)

OK, so now all I need is a Everything Service "pipe", IPC, no?
So if i uninstall / install, without the "superfluous" '-instance 15', i should be good, no?

For good measure:
C:\DEV\Locate\15.1404>everything -uninstall-service -instance 15
C:\DEV\Locate\15.1404>everything -uninstall-service -instance 15
C:\DEV\Locate\15.1404>everything -uninstall-service
C:\DEV\Locate\15.1404>everything -uninstall-service

On the first uninstall, I receive notice that the Service was removed.
Subsequent uninstalls did not notify (as there was nothing to notify of, as it was already gone).

C:\DEV\Locate\15.1404>everything -install-service

With above, should get me back going, (pipelist) Instance should show (1), Find Handle for
'Everything Service' should also now be found?

Err... wrong?
So what went wrong?

Service is there, running.
I do NOT have Everything Service found as a Handle (in System Informer or Process Explorer).
But I do show 'Everything Service (1.5a) in pipelist, 1 Instance.
My existing Everything Instance show connected to the Service (either 1 or 6, connected).
My /rox/ Instance... IS still working, with both Everything1404.exe & Everything1403.exe.

So the only questions now are...
1. my use of '-instance 15', was that in fact causing issues by its use, or has something
from my (ancient & continued current) usage of it simply "stuck" from time immemeorial?
2. why am i now not seeing 'Everything Service' being found by Process Explorer, Find Handles?

Uptime: 37 days 2 hours 1 minute 28 seconds, which would have had to have been a power
failure... But even so, that would have left the existing Service intact. And the Service
would only have been uninstall / install, on an Everything update (aside from messing around,
currently), & that was Dec. 22, was it. And (of course) at that time, I would have used
-instance 15 during the uninstall / install...

I'll assume, at this point the issue is resolved, that I shouldn't run into further issues,
even if not clear on all the facts that lead up to it, nor the lack of finding, currently,
'Everything Service' in Process Explorer.

(I'll mess around I see if I can't duplicate the pipelist Instance count to two .)

Even in a version (1213) where (Everything) -instance does affect the Service "name",
if I, everything -install-service -instance 15,
I end up with a Everything Service (15), rather then Everything Service (1.5a)

If I then take (1404) & -uninstall-service -instance 15, the -instance 15 is for not,
& then Everything Service (15) is left.
(1404) will only uninstall an Everything Service (1.5a)
(1404) will only install an Everything Service (1.5a)

In order to actually uninstall an Everything Service (15), I need to actually use
an Everything version (like 1213), where the -instance <name> actually had some meaning.

Now, while (1404) cannot remove an (user) named Everything Service (like, 15), it can
add an addition Everything Service (1.5a), so those two could potentially exist at the
same time - but that would be fairly obvious. you would see two in "task manager".

C:\DEV\Sysinternals>pipelist | grep -i everything
Everything IPC (15) 1 -1
Everything IPC (KKK) 1 -1
Everything IPC (CEO) 1 -1
Everything IPC (MULE.1402) 1 -1
Everything Service (15) 1 -1
Everything Service (1.5a) 1 -1

Everything (1213) can uninstall a (1404) Service - so long as you give it the correct
Service <name>, so Everything.exe -uninstall-service -instance 1.5a

So, so far I can get more then one Instance <name> running, ending up with two separate
Service <names>, I can uninstall either or both, but I've not duplicated where pipelist
showed that Everything Service (1.5a) had a (pipelist) Instance count of 2. Nor have I
gotten a Process Explorer Handle search to turn up anything again for
"Everything Service"?

I've never (that I remember) done anything to not have to use what is it, the instance
name (?) with Everything 1.5. I've always used -instance <name> in my batch files.

Current Everyting 1.5 instance is (1.5a). I've never used (particularly) "1.5a" for
any of my Instance naming. My main, regular, every day Instance name has always been
"15" - "15" vs. "1.5a". Even thought my "main" Instance is /named/ "15",
it is the (1.5a) /Service/ that it is running, that -instance 15 communicates with.

All other Instances that I run are likewise. They have their unique -instance <name>,
& use the (1.5a) Service. (If I were to not specifically give an -instance <name>,
then at that point it would simply default to an Instance name of (1.5a). All of this
has remained "constant", over time. Never any problems - until fairly recently, when,
out of the blue, firing up some arbitrary -instance <name> simply failed to connect
- sometimes.

And at the same time, simply by changing the directory name that "Everything.exe"
was within, did allow that very same -instance <name> to connect, to work?
/rox/ fails, where /ro/ works?

And likewise, something generated a (pipelist) Everything Service (15) "Instance"
count (whatever that means) of 2 (rather then what seemingly should have been 1)

(Likewise, in the System Informer screenshots, /when/ the Handle search for
'Everything Service' turned up results, it too hinted at a "2" - 2 /References/,
& 1 Handle, again, whatever that means?)

Might "Image type"; i386 (64-bit) Service, vs. i386 (32-bit) GUI, have any
bearing? (I'm using x86.)

Remember the "2"... Why was it 2? How did it get to be 2? Why did it change
from 2 to 1? As there were (seemingly) 2 "References" / "Instances" to this
singular Handle to the Everything Service (1.5a) (is the the gist ?) what caused
that, & why when (& I assume I did ?) -uninstall-service / -install-service,
did that "2" persist - until just now?


(And even on the computer I am on now, the post above this one, it too shows "2" in pipelist?

And now, 1 day later, it is... "3" ?)

Code: Select all

C:\DEV\Sysinternals>pipelist | grep -i everything
Everything Service (1.5a)                         3               -1
Everything IPC (OFFICEMULE)                       1               -1
Everything IPC (15)                               1               -1

[therube]

Note 2 "References" (whatever that means?), 1 Handle - and, 'everything service' is found (& that changes):
.

Everything Service - NamedPipe.png (85.72 KiB) Viewed 4884 times

.
All my 1404's are identical, having digital certificates & whatnot.
.

Everything - SHA1 values, so digital certificates are valid.png (33.53 KiB) Viewed 4884 times

.
Somehow my (pipelist) "Instance" number, which originally was "2", changed to "1".
And at the same time, a (Process Explorer) Handle search no longer finds 'everything service' - only 'everything' is found (& works).
.

Everything Service - no ES Handle found, but Everything Handle is, and too, Everything works.png (30.54 KiB) Viewed 4884 times

[therube]

(Back on other computer...)

And that reminded me...

Code: Select all

C:\DEV\Sysinternals>handle | grep -i everything
Everything.exe pid: 20056 \<unable to open process>
Everything.exe pid: 28756 RUBEN\RUBEN7
Everything.exe pid: 53012 RUBEN\RUBEN7

20056 is the actual Service, & 28756 & 53012 are two open (GUI) Instances talking to the Service.
Searching for 'everything service' finds (now), 2, the same 28756 & 53012.
Where, last night, 'everything service' was not finding anything, when I had 4 Instances open?


So I open another Instance (dumy) -no-auto-include, & handle sees it.

Code: Select all

C:\DEV\Sysinternals>handle | grep -i everything
Everything.exe pid: 20056 \<unable to open process>
Everything.exe pid: 28756 RUBEN\RUBEN7
Everything.exe pid: 53012 RUBEN\RUBEN7
Everything.exe pid: 39560 RUBEN\RUBEN7

Yet searching for 'everything service' still only shows 2 (the two above).
AND, Help | Troubleshooting of (dumy), shows 1 (connected) ?
I was sure expecting to see a 6 (connected).
All I have every seen in the past (& so expecting the same, here) is
1 (connected) on my "main" Instance &
6 (connected) on all subsequently opened Instances.

And yet here, I have two 1 (connected), plus one 6 (connected).

Add a volume to (dumy), & with that, a search for 'everything service' now finds
3 items, the third being (dumy). (Yet 'References' - whatever that means, is still
2. So whatever I might have thought it meant moments ago, no longer holds.)
.

Everything Service - each Instance gets its own Handle, yet at home, NO Handles now turn up.png (18.66 KiB) Viewed 4875 times

[void]

Thanks for the reports therube,

This means the pipe was connected, but later broken (server side closed the pipe)
So a connection to the service is being made, but the service is then closing the connection.

Again begs the question, Why?

If enabling service_allow_untrusted_connections fixes the issue, to me this means the service is seeing the connection as untrusted for the failed connections.

Ditto, why?

I don't have a good answer yet.
The next update will add more debug output to try to find the issue.

With 6274 being the PID of "services.exe", right?

Yes, the PID is just an example, it will be random.

One thing I didn't mention is you will need to run Process Explorer as Admin.
Running as a standard user would explain why Process Explorer shows no pipe handles (when no client GUIs are running)
I recommend closing all instances of Everything as Process Explorer will show the service and client GUIs.
We are only interested in the services.

Everything Service, or simply, Everything ?

Search for Everything Service, that should match the pipe name.
The stock pipe name for Everything 1.5 alpha is:

\Device\NamedPipe\Everything Service (1.5a)

This is hard coded and cannot be changed with

-instance

Oh, oh, oh. So you want the Handle, not the Service per se.
And in that case, 'everything service' would be a correct search.
(And I've got to assume ? that there is only 1. [I'll let you know.])

I'm after the total number of handles from the service process.
Please try exiting all client GUIs before running Process Explorer.
Otherwise, Process Explorer will also list the client GUI pipe connections.

Now, why (pipelist) Instances (for Everything Service) shows 2
(or what Instances / Max Instances even means, I don't know) ?

It's normal for there to be 2 or more pipe instances.
If a client GUI connects, that will count as one.
Then there's always an extra instance listening for a new connection.
If you close all the client GUIs, there should only be 1 for service.

Max Instances of -1 just means the maximum number of instances is unlimited.

So maybe, from ages ago... what, I have had two (pipelist) "Instances", & one "Everything -svc"?

That's what I was thinking, but I'm not so sure it's happening..
Launching

Everything.exe -svc

will fire up another service, you can run multiple instances of the service and they will share the pipe connections and cause the issue you describe.

So... at this point /rox/ should still be broken? OK... was not expected that. /rox/ IS working
with Everything1404.exe. [I thought it was going to be broken, still.]
(Oops, forgot to include the -no-auto-load or -read-only switch!) (And Everything1403.exe is also
working with /rox/.)

Please try disabling service_allow_untrusted_connections and see if the connection is still broken.

OK, so now all I need is a Everything Service "pipe", IPC, no?

Just the Everything Service pipe, ignore the IPC pipes.

So if i uninstall / install, without the "superfluous" '-instance 15', i should be good, no?

You don't need an instance name when uninstalling/installing the Everything Service.
The instance name is ignored.
Early versions of the alpha did use the instance name, so maybe there is a lingering service with an unique instance.
What's listed under Start -> Run -> Services.msc (are there multiple Everything Services listed?)

And at the same time, simply by changing the directory name that "Everything.exe"
was within, did allow that very same -instance <name> to connect, to work?
/rox/ fails, where /ro/ works?

I don't have a good explanation for this at the moment.
Logs from the next alpha update should help.

Might "Image type"; i386 (64-bit) Service, vs. i386 (32-bit) GUI, have any
bearing? (I'm using x86.)

No.
The image type doesn't matter.

So I open another Instance (dumy) -no-auto-include, & handle sees it.
Yet searching for 'everything service' still only shows 2 (the two above).
AND, Help | Troubleshooting of (dumy), shows 1 (connected) ?

Strange it shows 1 (connected)
Status are as follows:

Code: Select all

0 = Service not installed and no connection could be made.
1 = Service fully installed with the current GUI Everything.exe and service is running.
2 = Service partially installed with any Everything.exe and service is not running.
4 = Service not installed and connected via the 'run indexing process as admin'.
6 = Service partially installed with any Everything.exe and service is running.

I would expect 6 too, unless you set the dumy to be the service?

[therube]

you will need to run Process Explorer as Admin

I have not been doing that - so far.

Running as a standard user would explain why Process Explorer shows no pipe handles (when no client GUIs are running)

Usually. But this can also happen when the GUIs are running but not actually "connecting", "updating", if you will.

I recommend closing all instances of Everything as Process Explorer will show the service and client GUIs.

Yes, I saw that.

I'm after the total number of handles from the service process.

AFAIK, for the Service itself, it will be only 1. (And again, I've not yet run "as Admin".)

Otherwise, Process Explorer will also list the client GUI pipe connections.

Saw that too, but they're easily distinguishable.

It's normal for there to be 2 or more pipe instances.
If a client GUI connects, that will count as one.
Then there's always an extra instance listening for a new connection.
If you close all the client GUIs, there should only be 1 for service.

Yep, just what I came to realize.

Please try disabling service_allow_untrusted_connections and see if the connection is still broken.

Once I saw that setting that "fixed" things, I then unset it (renamed the key, so it has been "off" since then).

I would expect 6 too, unless you set the dumy to be the service?

Nope.
(Depending on which computer, the Service would have been installed from either /dev/Locate/ or /dev/Locate/1404/.
dumy is simply a plain-jane Instance that was run.)


And it gets better... (below).

[therube]

Everything - search 'Everything Service' - lack, thereof

OK, got that straightened.
As I'm messing... I never did actually close any open instances, so even though I was ("connected"),
I was not actually updating - "connecting", if you will.

But once I, Index | Pause, Index | Update, at that point I started (actually) updating, (actually) "connecting",
& with that, search for 'Everything Service' did then turn up the expected "Handle" (NamedPipe).

Likewise, pipelist also incremented the (existing) (pipelist) Instance count from (what was) 1 to 2.
(And as I Index | Pause, Index | Update, in my other Instances, then too does (pipelist) Instance count increment.)


So, (pipelist) Instance count increments for each (Everything) Instance (that is not -read-only),
& so should also decrement for each (Everything) Instance that is closed,
with a count of 1 meaning that either all (Everything) Instances are closed,
or that no (Everything) Instances are actually "connected", "connecting"
(& even if Help | Troubleshooting indicates that they are - they're just in a lala land, until "poked").

So then there goes that (my) theory about "2" (having some significance in my Instances that were truly NOT connecting).

And a "search for 'Everything Service' that has only ever turned up 1 (or none) result, so that is totally fine.

(System Informer) "References" being "2", still not understanding just what that means,
but that it is "2" seems like that too is immaterial.

(System Informer) Find Handle 'everything service' returns only
1 item (or 0, ever), & that being the (Everything) Instance from which the Service had been installed from.

(Process Explorer) Find Handle 'everything service' returns the
Instances that are actually connected (so usually 1 or more, & potentially 0 - if things are in lala land).
(I've not yet run these, "as Admin".)

Handle, returns both the Instances (actually connecting or not) & also the Service itself.

Code: Select all

C:\DEV\Sysinternals>handle -p everything | grep -v E:

Nthandle v5.0 - Handle viewer
Copyright (C) 1997-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

-----------------------------------------------------
Everything.exe pid: 3960 RUBEN7\RUBEN
   1C: File          C:\DEV\Locate\15.1404
-----------------------------------------------------
Everything.exe pid: 7268 RUBEN7\RUBEN
   1C: File          C:\DEV\Locate\K-DRIVE
-----------------------------------------------------
Everything.exe pid: 5360 RUBEN7\RUBEN
   1C: File          C:\DEV\Locate\CE+O
-----------------------------------------------------
Everything.exe pid: 14256 RUBEN7\RUBEN
   1C: File          C:\DEV\Locate\MULE.1402
-----------------------------------------------------
Everything.exe pid: 13228 \<unable to open process>
-----------------------------------------------------
Everything.exe pid: 9316 RUBEN7\RUBEN
   1C: File          C:\DEV\Locate\DUP.from.KKK\zzz

pipelist returns similar, different format, each Instance, plus the Service, plus a count of Instances that are actually
connected to the Service, with 1 being the Service itself.

Code: Select all

:\DEV\Sysinternals>pipelist | grep -i everything
verything IPC (15)                               1               -1
verything IPC (KKK)                              1               -1
verything IPC (CEO)                              1               -1
verything IPC (MULE.1402)                        1               -1
verything Service (1.5a)                         4               -1
verything IPC (abc)                              1               -1

And with all of that, there is still the question as to why Everything1404.exe actually failed to connect to the Service when run from the directory /rox/ (& why, what changed, that it does, now)?
(And that question is now kind of moot - see below.)


So for...

In Process Explorer, do a search for: Everything Service

There should be one pipe handle:
Everything.exe 6724 File \Device\NamedPipe\Everything Service (1.5a)

That's not really right. There should be one pipe handle for every (actually) connected (Everything) Instance.
(And lets change that again - for each Instance that has an actually connected NTFS [& maybe some other type(s) of] Index.)
.

Everything Service - Process Explorer 'ES' search.png (30.58 KiB) Viewed 4763 times

.



AND AND AND, & after all of that, thinking that things were working, after verifying yet one more time that /rox/ was (& IS) working, I rename /rox/ to /ro/, AND AND AND, guess what ???

EVERYTHING1404.exe -read-only - FAIL, 2 (disconnected)
EVERYTHING1403.exe -read-only - FAIL, 2 (disconnected)

Before it was /rox/ that was failing & /ro/ that was working,
& at the same time 1404+/rox/ was failing & 1403+/rox/ was working,
& now /ro/ is failing with both 1404 & 1403
& /rox/ is working with both?

Things flipped (& more).
(And I thought I was getting somewhere, heh.)
And all I did was to change the directory name.


So I kind of got a handle on Handle, & I piped pipelist, & I explored Process Explorer,
& I was informed by System Informer, & after all of that, I'm where I started .

How's that for a monkey in the wrench!
.

What was not working before, now is, what was working before, now is not.
.

Everything Service - rox vs ro, plus, 1404 vs 1403, working vs not - switched places, and ro not working at all.png (87.18 KiB) Viewed 4762 times

[therube]

Now, just what is that showing?
20056 is the Service, & there are 3 (when running, "as Admin").

The other two PIDs are two running GUI Instances.

Oh. So when you Quit a GUI, it drops, & also one of the 20056's drops.
So if you Quit all GUI, then only the 1 Service 20056 PID should remain. [Yes.]
And that is what you're looking for, so (on this computer) I should be good, only a single 20056 with all GUI's closed.
.

Everything Service - as Admin.png (18.38 KiB) Viewed 4754 times

(I'll see what my home computer turns up tonight...)

[therube]

Running Process Explorer "as Admin", so nothing really new, just more a "complete" picture.
And there is only 1 Service, so no "stragglers".


13228 is the Service

System Informer shows the GUI's that are attached to the Service, but not the Service itself.
(System Informer is not running "as Admin".)

Process Explorer shows the GUI's that are attached to the Service, & the Service itself, plus,
that Service connection for each of the GUI Instances.

Neither shows the -read-only Instance (13356), & being -read-only, no actual connection to the Service.

3960 is my "main" Instance (15), where the Service was "installed" from
7268 & 5360 are two other Instances I have running

(I've not shut down any GUI's, but surmise if I did so, System Informer would not find anything in a Handle search,
& Process Explorer, running as Admin, would return only 1 result, the Service itself.)

Process Explorer was run "as Admin", & is returning the same results as when run at a User level
- except that it now shows the Service itself.
(And I'll suppose that if I were to run System Informer "as Admin", it too would then pick up on the Service itself too.
Process Hacker, run "as Admin" does, so yes, System Informer would do so too.)

.

Everything Service - Process Explorer & Process Hacker, as Admin, System Informer as User.png (56.97 KiB) Viewed 4698 times

[void]

The pipe handle information all looks as expected.

Everything 1.5.0.1405a adds more debug information.

Could you please capture a log from both the client and Everything Service for an instance that fails to connect.

[therube]

Quit all instances
Copy (directory) /1404/ -> /1405/

/1404/
everything -uninstall-service -instance 15
(service 1.5a is removed)
(note i did this from /1404/, not /1405/
service had been running from 1404
there are times when i might have -uninstall-service
from either /1404/ or /1405/ - in case that might matter)

/1405/
attrib -a
copy Everything1405.exe over top of (existing 1404) Everything.exe
everything -install-service -instance 15

(service 1.5a is created)

go.bat: cmd /c start .\everything.exe -instance 15

Instance 15
History | Restore

Copy Everything1405.exe overtop of all other Everything.exe's (in each Instance folder)
Instance 15 is only open Instance, i've not yet opened any other Instances


---


Open /ro/
go.bat: cmd /c start .\everything1405.exe -instance DUP.from.K -read-only -debug
/ro/ opened successfully 6,connected
Quit

ren /ro/ -> /rox/
go.bat
/rox/ FAILED, 2,disconnected


Debug Console.TXT:

Code: Select all

WriteFile GetOverlappedResult failed 109
_service_client_ioctrl failed to write
failed to check service version 6
Everything 1.5.0.1405a (x86)
OS: Windows NT 6.1 7601 (x64)
Admin: 0
Service: 2 (disconnected / installed and not running)
Command line: -instance DUP.from.K -read-only -debug
Binary: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything1405.exe
Profile: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.ini
Database: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.db
Instance: DUP.from.K

Config:
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size",
"width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

load localization
load image lists
sys img list 00453708 0048d7b8 1 0
load fonts
default font MS Shell Dlg 2 -11
load everything icon
install hooks
create mutex
OpenMutex 2
load property system
property system loaded 0.006692 seconds
load bookmarks
load 0 bookmarks 0.000098 seconds
load 0 bookmarks 0.000050 seconds
load filters
load 0 filters 0.000108 seconds
load 0 filters 0.000048 seconds
load macros
load search history
load 0 search history items 0.000060 seconds
load 0 search history items 0.000062 seconds
load property values
property override loaded 0.000015 seconds
MoveFile:
C:\DEV\Locate\DUP.from.KKK\KKK-rox\Session-DUP.from.K.json
to:
C:\DEV\Locate\DUP.from.KKK\KKK-rox\Session-DUP.from.K.backup.json
MoveFileEx 2
create system tray icon
start ipc pipe server
new thread (0)
Desktop SHChangeNotifyRegister: 002c0744 36867 1 0
load db
new thread (1)
create ui
set rebuild reason: Unable to open database file.
loaded 0 folders, 0 files, in 0.002124 seconds
theme not cached
WM_ACTIVATE 00000001 00000000
 lastfocus 00000000
 current focus 00000000
 current foreground 02b01178
 minimized 00000000
FOCUS 0
FOCUS restore 00000000
FOCUS restore 002f05f4
enter setfocus
leave setfocus
add nav
new results 0
load plugins
FindFirstFileEx 3 C:\DEV\Locate\DUP.from.KKK\KKK-rox\Plugins\*
start plugins
enter main loop
load db failed.
DB_WAIT: _db_load_failed_proc waiting for _db_load_local_thread_proc...
DB_WAIT: _db_load_failed_proc waited 0.000354 seconds
clear queries
clear is available
clear db
shell_change_notify stop get fd thread
shell_change_notify remove events
shell_change_notify free events
shell_change_notify remove got fd events
shell_change_notify free got fd events
shell_change_notify after update events
shell_change_notify free monitors
load backup db
set rebuild reason: Unable to open database file.
loaded 0 folders, 0 files, in 0.000481 seconds
load backup db failed.
DB_WAIT: _db_load_backup_failed_proc waiting for _db_load_local_thread_proc...
DB_WAIT: _db_load_backup_failed_proc waited 0.000309 seconds
clear queries
clear is available
clear db
shell_change_notify stop get fd thread
shell_change_notify remove events
shell_change_notify free events
shell_change_notify remove got fd events
shell_change_notify free got fd events
shell_change_notify after update events
shell_change_notify free monitors
Load complete.
is rebuild required
index loaded.
ready
search '' filter '' sort 5 ascending 0
FOLDER TERM START 001cf010 M 001cf010 N 001cf0b0
FILE TERM START 001cf010 M 001cf010 N 001cf0b0
found 0 files with 0 threads in 0.000001 seconds
found 0 folders with 0 threads in 0.000001 seconds
SET SORT 0
set sort 5 ascending 0 is valid 1 case 0
fill with name arrays
sort complete 01607ae2, valid 1
finished sort, time taken 0.000911 seconds
updated selection in 0.000002 seconds
ready
DB_WAIT: _db_ready_proc waiting for _db_search_thread_proc...
DB_WAIT: _db_ready_proc waited 0.000311 seconds
new results 0
COMMAND 40089
WriteFile GetOverlappedResult failed 109
_service_client_ioctrl failed to write
failed to check service version 6
WM_ACTIVATE 00000000 003a03e0
 lastfocus 002f05f4
 current focus 002f05f4
 current foreground 02b01178
 minimized 00000000

Again, cannot Debug Service of /rox/ cause /rox/ is disconnected.
(/rox/ is left open)


Debug Service from /15/ Instance.TXT
(attached)


Quit /rox/
ren /rox/ -> /ro/
go.bat

Debug Console /ro/.TXT

Code: Select all

Everything 1.5.0.1405a (x86)
OS: Windows NT 6.1 7601 (x64)
Admin: 0
Service: 6 (connected / partially installed)
Command line: -instance DUP.from.K -read-only -debug
Binary: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything1405.exe
Profile: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.ini
Database: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.db
Instance: DUP.from.K

Config:
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size",
"width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

load localization
load image lists
sys img list 008b37a8 008ed808 1 0
load fonts
default font MS Shell Dlg 2 -11
load everything icon
install hooks
create mutex
OpenMutex 2
load property system
property system loaded 0.006121 seconds
load bookmarks
load 0 bookmarks 0.000148 seconds
load 0 bookmarks 0.000050 seconds
load filters
load 0 filters 0.000067 seconds
load 0 filters 0.000070 seconds
load macros
load search history
load 0 search history items 0.000057 seconds
load 0 search history items 0.000055 seconds
load property values
property override loaded 0.000011 seconds
MoveFile:
C:\DEV\Locate\DUP.from.KKK\KKK-ro\Session-DUP.from.K.json
to:
C:\DEV\Locate\DUP.from.KKK\KKK-ro\Session-DUP.from.K.backup.json
MoveFileEx 2
create system tray icon
start ipc pipe server
new thread (0)
Desktop SHChangeNotifyRegister: 00430744 36867 1 0
load db
new thread (1)
create ui
set rebuild reason: Unable to open database file.
loaded 0 folders, 0 files, in 0.002661 seconds
theme not cached
WM_ACTIVATE 00000001 00000000
 lastfocus 00000000
 current focus 00000000
 current foreground 08e60b30
 minimized 00000000
FOCUS 0
FOCUS restore 00000000
FOCUS restore 0526050a
enter setfocus
leave setfocus
add nav
new results 0
load plugins
FindFirstFileEx 3 C:\DEV\Locate\DUP.from.KKK\KKK-ro\Plugins\*
start plugins
enter main loop
load db failed.
DB_WAIT: _db_load_failed_proc waiting for _db_load_local_thread_proc...
DB_WAIT: _db_load_failed_proc waited 0.000302 seconds
clear queries
clear is available
clear db
shell_change_notify stop get fd thread
shell_change_notify remove events
shell_change_notify free events
shell_change_notify remove got fd events
shell_change_notify free got fd events
shell_change_notify after update events
shell_change_notify free monitors
load backup db
set rebuild reason: Unable to open database file.
loaded 0 folders, 0 files, in 0.000463 seconds
load backup db failed.
DB_WAIT: _db_load_backup_failed_proc waiting for _db_load_local_thread_proc...
DB_WAIT: _db_load_backup_failed_proc waited 0.000278 seconds
clear queries
clear is available
clear db
shell_change_notify stop get fd thread
shell_change_notify remove events
shell_change_notify free events
shell_change_notify remove got fd events
shell_change_notify free got fd events
shell_change_notify after update events
shell_change_notify free monitors
Load complete.
is rebuild required
index loaded.
ready
search '' filter '' sort 5 ascending 0
FOLDER TERM START 0042f0c8 M 0042f0c8 N 0042f168
FILE TERM START 0042f0c8 M 0042f0c8 N 0042f168
found 0 files with 0 threads in 0.000001 seconds
found 0 folders with 0 threads in 0.000001 seconds
SET SORT 0
set sort 5 ascending 0 is valid 1 case 0
fill with name arrays
sort complete 012d7ae2, valid 1
finished sort, time taken 0.000786 seconds
updated selection in 0.000003 seconds
ready
DB_WAIT: _db_ready_proc waiting for _db_search_thread_proc...
DB_WAIT: _db_ready_proc waited 0.000282 seconds
new results 0
COMMAND 40089
WM_ACTIVATE 00000000 04ff0e80
 lastfocus 0526050a
 current focus 0526050a
 current foreground 08e60b30
 minimized 00000000
WM_ACTIVATE 00000001 04ff0e80
 lastfocus 0526050a
 current focus 00401248
 current foreground 08e60b30
 minimized 00000000
FOCUS 0
FOCUS restore 0526050a
FOCUS restore 0526050a
WM_ACTIVATE 00000000 00000000
 lastfocus 0526050a
 current focus 0526050a
 current foreground 004106ac
 minimized 00000000

this time, /ro/, we are 6,connected, so can get Debug Service log from /ro/
(15 is still open)


(i'll note...
Service Debug, when it is not debugging, the Stop is not in a grayed out state,
like it is when Debug Logging is Stopped.)



Ah...

i changed my batch file - in /rox/ (which WORKS)

cmd /c start C:\DEV\Locate\15.1405\Everything.exe -instance DUP.from.K -read-only

& with that, /rox/, instead of 6,connected
now shows 1,connected

& lets see what happens when i ren /rox/ -> /ro/...

& now /ro/ - also WORKS, 1,connected

& if i go back to my older batch file, starting the Instance from the Everything1405.exe
that is contained in /ro/...

& now /ro/ - STILL WORKS, but now as 6,connected

& with that, i might have broken my brokenness ? as in i might not be able to repeat
the 2,disconnected state?

what pointed me to try above was
client 10: exe C:\DEV\Locate\15.1405\Everything.exe in the /15/ log &
client 25: exe C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything1405.exe in the /ro/ log


(similarly, in a post above, when there was an unexpected 1,connected instead
of 6,connected, wonder if instead of copying Everything.exe into that directory,
if i had not posted the path to the .exe where the Service had been installed from?)


ren /ro/ -> /rrr/
go.bat (running Everything1405.exe) - AHA! 2,disconnected
cmd /c start .\everything1405.exe -instance DUP.from.K -read-only

Code: Select all

ren /rrr/ -> /ro/ - 6,connected
ren /ro/ -> /rox/ - 2,disconnected :-), so i broke myself back to breaking
ren /rox/ -> /ro/ - 6,connected
ren /ro/ -> /rrr/ - 2,disconnected :-), so now i've flipped, & tossing & turning

change go.bat again...
go.bat: cmd /c start C:\DEV\Locate\15.1405\Everything.exe -instance DUP.from.K -read-only

Code: Select all

(existing)  /rrr/ - 1,connected
ren /rrr/ -> /ro/ - 1,connected
ren /ro/ -> /rox/ - 1,connected

now we've gotten somewhere
now why/how i ended up /ro/ & /rox/ & /rrr/, well, that's anyone's guess
at the start maybe if i had used more descriptive names (but then, it wouldn't be as much fun, heh)


in general, i (almost) always...
"install" into a /version.number/ directory, so /1404/ /1405/ /1406/...

in general, (almost) always...
any Instances are within their own directory, have their own copy of Everything within that directory
& are started with a go.bat: .\Everything.exe -instance <name>

with that...
i've always had 1,connected with my /version.number/ directory Instance (& that is always Instance 15)
& any other Instance's come up as 6,connected

before "now", i'd never run into a 2,disconnected. (maybe by chance, maybe not?)

anyhow...

it looks like running from the Everything.exe in the "install" directory (the /version.number/ directory),
pointed to from within any (different) Instance directory,
will give a 1,connected (so multiple simultaneous 1,connected's)


AH, but that is wrong isn't it.
Doing that does:

Code: Select all

Binary:	C:\DEV\Locate\15.1405\Everything.exe
Profile:	C:\DEV\Locate\15.1405\Everything-DUP.from.K.ini
Database:	C:\DEV\Locate\15.1405\Everything-DUP.from.K.db
Instance:	DUP.from.K

Binary: is correct, that is what i am running
BUT...
Profile: & Database: are wrong.
They are (& in fact are) setting the Profile to /1405/, & writing the .db to /1405/,
rather then in the directory where the Instance: (DUP.from.K) is located
(which currently is /rox/): C:\DEV\Locate\DUP.from.KKK\KKK-rox\

(now i suppose there are command line switches to get around that, but that is not the point.
you should be able to simply throw an Everything.exe into any arbitrary directory, provide it an Instance name & GO.)

which means, we need to figure out this:

Code: Select all

2026-02-26 18:43:11.014: WriteFile GetOverlappedResult failed 109
2026-02-26 18:43:11.015: _service_client_ioctrl failed to write
2026-02-26 18:43:11.015: failed to check service version 6

[therube]

Troubleshooting /rox/:

Code: Select all

Everything 1.5.0.1405a (x86)
OS:	Windows NT 6.1 7601 (x64)
Admin:	0
Service:	2 (disconnected / installed and not running)
Command line:	-instance DUP.from.K -read-only -debug
Binary:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything1405.exe
Profile:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.ini
Database:	C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.db
Instance:	DUP.from.K

Config:
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

Troubleshooting /ro/:

Code: Select all

Everything 1.5.0.1405a (x86)
OS:	Windows NT 6.1 7601 (x64)
Admin:	0
Service:	6 (connected / partially installed)
Command line:	-instance DUP.from.K -read-only
Binary:	C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything1405.exe
Profile:	C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.ini
Database:	C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.db
Instance:	DUP.from.K

Config:
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

(by this point, i think they flipped, the connected/disconnected?)


Debug Log /ro/

Code: Select all

2026-02-26 18:59:22.230: Everything 1.5.0.1405a (x86)
2026-02-26 18:59:22.230: OS: Windows NT 6.1 7601 (x64)
2026-02-26 18:59:22.230: Admin: 0
2026-02-26 18:59:22.230: Service: 6 (connected / partially installed)
2026-02-26 18:59:22.230: Command line: -instance DUP.from.K -read-only
2026-02-26 18:59:22.230: Binary: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything1405.exe
2026-02-26 18:59:22.230: Profile: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.ini
2026-02-26 18:59:22.230: Database: C:\DEV\Locate\DUP.from.KKK\KKK-ro\Everything-DUP.from.K.db
2026-02-26 18:59:22.230: Instance: DUP.from.K
2026-02-26 18:59:22.230: 
2026-02-26 18:59:22.230: Config:
2026-02-26 18:59:22.230: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-26 18:59:22.230: 
2026-02-26 18:59:22.230: Policy:
2026-02-26 18:59:22.230: 
2026-02-26 18:59:22.230: Plugins:
2026-02-26 18:59:22.230: 
2026-02-26 18:59:23.575: SYSCOMMAND 0000f095 0110038d
2026-02-26 18:59:25.363: COMMAND 40089
2026-02-26 18:59:25.431: WM_ACTIVATE 00000000 004e03e0
2026-02-26 18:59:25.431:  lastfocus 00460744
2026-02-26 18:59:25.431:  current focus 00460744
2026-02-26 18:59:25.431:  current foreground 06cd0fb0
2026-02-26 18:59:25.431:  minimized 00000000
2026-02-26 18:59:26.299: WM_ACTIVATE 00000001 004e03e0
2026-02-26 18:59:26.299:  lastfocus 00460744
2026-02-26 18:59:26.299:  current focus 06290524
2026-02-26 18:59:26.299:  current foreground 06cd0fb0
2026-02-26 18:59:26.299:  minimized 00000000
2026-02-26 18:59:26.299: FOCUS 0
2026-02-26 18:59:26.299: FOCUS restore 00460744
2026-02-26 18:59:26.300: FOCUS restore 00460744
2026-02-26 18:59:27.353: SYSCOMMAND 0000f095 0115036f
2026-02-26 18:59:29.420: COMMAND 40210

Debug Log /rox/

Code: Select all

2026-02-26 18:43:11.014: WriteFile GetOverlappedResult failed 109
2026-02-26 18:43:11.015: _service_client_ioctrl failed to write
2026-02-26 18:43:11.015: failed to check service version 6
2026-02-26 18:43:11.015: Everything 1.5.0.1405a (x86)
2026-02-26 18:43:11.015: OS: Windows NT 6.1 7601 (x64)
2026-02-26 18:43:11.015: Admin: 0
2026-02-26 18:43:11.015: Service: 2 (disconnected / installed and not running)
2026-02-26 18:43:11.015: Command line: -instance DUP.from.K -read-only
2026-02-26 18:43:11.015: Binary: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything1405.exe
2026-02-26 18:43:11.015: Profile: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.ini
2026-02-26 18:43:11.015: Database: C:\DEV\Locate\DUP.from.KKK\KKK-rox\Everything-DUP.from.K.db
2026-02-26 18:43:11.015: Instance: DUP.from.K
2026-02-26 18:43:11.015: 
2026-02-26 18:43:11.015: Config:
2026-02-26 18:43:11.015: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-26 18:43:11.015: 
2026-02-26 18:43:11.015: Policy:
2026-02-26 18:43:11.015: 
2026-02-26 18:43:11.015: Plugins:
2026-02-26 18:43:11.015: 
2026-02-26 18:43:14.666: COMMAND 40089
2026-02-26 18:43:14.668: WriteFile GetOverlappedResult failed 109
2026-02-26 18:43:14.668: _service_client_ioctrl failed to write
2026-02-26 18:43:14.668: failed to check service version 6
2026-02-26 18:43:14.673: WM_ACTIVATE 00000000 06c40fb0
2026-02-26 18:43:14.674:  lastfocus 002906a4
2026-02-26 18:43:14.674:  current focus 002906a4
2026-02-26 18:43:14.674:  current foreground 003505f4
2026-02-26 18:43:14.674:  minimized 00000000
2026-02-26 18:43:17.954: WM_ACTIVATE 00000001 06c40fb0
2026-02-26 18:43:17.954:  lastfocus 002906a4
2026-02-26 18:43:17.954:  current focus 04f40e80
2026-02-26 18:43:17.954:  current foreground 003505f4
2026-02-26 18:43:17.954:  minimized 00000000
2026-02-26 18:43:17.954: FOCUS 0
2026-02-26 18:43:17.954: FOCUS restore 002906a4
2026-02-26 18:43:17.955: FOCUS restore 002906a4
2026-02-26 18:43:20.808: SYSCOMMAND 0000f095 01100368
2026-02-26 18:43:26.115: COMMAND 40210

Service Debug /15/ (as can't debug the 2,disconnected Instance)

Code: Select all

2026-02-26 18:48:20.879: Everything 1.5.0.1405a (x86)
2026-02-26 18:48:20.879: OS: Windows NT 6.1 7601 (x64)
2026-02-26 18:48:20.879: Admin: 1
2026-02-26 18:48:20.879: Service: 1 (connected / installed and running)
2026-02-26 18:48:20.880: Command line: -svc
2026-02-26 18:48:20.880: Binary: C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:20.880: Profile: C:\DEV\Locate\15.1405\Everything-1.5a.ini
2026-02-26 18:48:20.880: Database: C:\DEV\Locate\15.1405\Everything-1.5a.db
2026-02-26 18:48:20.880: Instance: 1.5a
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Config:
2026-02-26 18:48:20.880: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Policy:
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Plugins:
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: client 8: client 0 0000017c 1 0 8 ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor count: 10
2026-02-26 18:48:20.880: client 8: ntfs monitor 0: \\?\Volume{.......................-09c64c792a24} 2 1 0 0 000001d8 00000198
2026-02-26 18:48:20.880: client 8: ntfs monitor 1: \\?\Volume{.......................-7713ca54f116} 3 1 0 1000 000001dc 000001a0
2026-02-26 18:48:20.880: client 8: ntfs monitor 2: \\?\Volume{.......................-806e6f6e6963} 1 2 0 30000 ffffffff ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor 3: \\?\Volume{.......................-5139169e8464} 1 2 0 30000 ffffffff ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor 4: \\?\Volume{.......................-3a83d8b46a3a} 2 1 0 0 ffffffff 000001a8
2026-02-26 18:48:20.880: client 8: ntfs monitor 5: \\?\Volume{.......................-fc757594da94} 2 1 0 0 ffffffff 000001b0
2026-02-26 18:48:20.880: client 8: ntfs monitor 6: \\?\Volume{.......................-bd601c5ecf5d} 2 1 0 0 ffffffff 000001b8
2026-02-26 18:48:20.880: client 8: ntfs monitor 7: \\?\Volume{.......................-40d21d415d94} 2 1 0 0 ffffffff 000001c0
2026-02-26 18:48:20.880: client 8: ntfs monitor 8: \\?\Volume{.......................-2796ba3da1c3} 2 1 0 0 ffffffff 000001c8
2026-02-26 18:48:20.880: client 8: ntfs monitor 9: \\?\Volume{.......................-aec9ea04d92e} 2 1 0 0 ffffffff 000001d0
2026-02-26 18:48:20.880: client 8: refs monitor count: 0
2026-02-26 18:48:20.880: client 8: client 8 000003b0 0 1 0 ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor count: 0
2026-02-26 18:48:20.880: client 8: refs monitor count: 0
2026-02-26 18:48:20.880: client 8: write pipe 0 8
2026-02-26 18:48:20.880: client 8: wait 2 0
2026-02-26 18:48:20.880: client 8: awake
2026-02-26 18:48:20.880: client 8: pipe read event
2026-02-26 18:48:20.880: client 8: GetOverlappedResult failed 109
2026-02-26 18:48:20.881: client 8: update read failed
2026-02-26 18:48:20.881: server awake
2026-02-26 18:48:20.881: event 1 018b0048
2026-02-26 18:48:20.881: client 8: disconnected
2026-02-26 18:48:20.881: client 0: awake
2026-02-26 18:48:20.881: client 0: pipe read event
2026-02-26 18:48:20.881: client disconnected
2026-02-26 18:48:20.881: listen_handle 00000144
2026-02-26 18:48:20.881: pipe listen GetOverlappedResult 996
2026-02-26 18:48:20.881: server wait 2 0
2026-02-26 18:48:20.881: client 0: data read size 44
2026-02-26 18:48:20.881: client 0: read pipe 34 52
2026-02-26 18:48:20.881: client 0: got command 22 44
2026-02-26 18:48:20.881: client 0: write pipe 0 288
2026-02-26 18:48:20.881: client 0: wait 9 1
2026-02-26 18:48:20.881: client 0: awake
2026-02-26 18:48:20.881: client 0: pipe read event
2026-02-26 18:48:20.881: client 0: data read size 44
2026-02-26 18:48:20.881: client 0: read pipe 34 52
2026-02-26 18:48:20.881: client 0: got command 22 44
2026-02-26 18:48:20.881: client 0: write pipe 0 16
2026-02-26 18:48:20.881: client 0: data read size 12
2026-02-26 18:48:20.881: client 0: read pipe 35 20
2026-02-26 18:48:20.881: client 0: got command 23 12
2026-02-26 18:48:20.881: client 0: write pipe 0 131
2026-02-26 18:48:20.881: client 0: data read size 12
2026-02-26 18:48:20.881: client 0: read pipe 35 20
2026-02-26 18:48:20.882: client 0: got command 23 12
2026-02-26 18:48:20.882: client 0: write pipe 0 65
2026-02-26 18:48:20.882: client 0: data read size 44
2026-02-26 18:48:20.882: client 0: read pipe 34 52
2026-02-26 18:48:20.882: client 0: got command 22 44
2026-02-26 18:48:20.882: client 0: write pipe 0 16
2026-02-26 18:48:20.882: client 0: data read size 44
2026-02-26 18:48:20.882: client 0: read pipe 33 52
2026-02-26 18:48:20.882: client 0: got command 21 44
2026-02-26 18:48:20.882: client 0: RESUME NTFS 1 3
2026-02-26 18:48:20.882: client 0: write pipe 0 8
2026-02-26 18:48:20.882: client 0: wait 9 1
2026-02-26 18:48:21.882: client 0: awake
2026-02-26 18:48:21.882: client 0: update monitor 1 read: hcjoverlapped 000001a0
2026-02-26 18:48:21.882: client 0: READING NTFS 1 9
2026-02-26 18:48:21.882: client 0: wait 10 1
2026-02-26 18:48:22.882: client 0: awake
2026-02-26 18:48:22.882: client 0: wait 10 1
2026-02-26 18:48:23.882: client 0: awake
2026-02-26 18:48:23.882: client 0: wait 10 1
2026-02-26 18:48:24.882: client 0: awake
2026-02-26 18:48:24.882: client 0: wait 10 1
2026-02-26 18:48:25.882: client 0: awake
2026-02-26 18:48:25.882: client 0: wait 10 1
2026-02-26 18:48:26.645: server awake
2026-02-26 18:48:26.645: listen_handle 00000144
2026-02-26 18:48:26.645: client 9: connecting...
2026-02-26 18:48:26.645: client 9: validating...
2026-02-26 18:48:26.645: client 9: process 000001e4
2026-02-26 18:48:26.646: client 9: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:26.646: client 9: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:26.646: client 9: connected
2026-02-26 18:48:26.646: listen_handle ffffffff
2026-02-26 18:48:26.646: client 9: awake
2026-02-26 18:48:26.646: listening...
2026-02-26 18:48:26.646: client 9: data read size 0
2026-02-26 18:48:26.646: client 9: read pipe 0 8
2026-02-26 18:48:26.646: client 9: got command 00 0
2026-02-26 18:48:26.646: client 9: write pipe 0 12
2026-02-26 18:48:26.646: connect error 997
2026-02-26 18:48:26.646: server wait 2 0
2026-02-26 18:48:26.646: client 9: ReadFile failed 109
2026-02-26 18:48:26.646: client 9: update read failed
2026-02-26 18:48:26.646: server awake
2026-02-26 18:48:26.646: event 1 018b0048
2026-02-26 18:48:26.646: client 9: disconnected
2026-02-26 18:48:26.646: client disconnected
2026-02-26 18:48:26.646: listen_handle 00000224
2026-02-26 18:48:26.646: pipe listen GetOverlappedResult 996
2026-02-26 18:48:26.646: server wait 2 0
2026-02-26 18:48:26.882: client 0: awake
2026-02-26 18:48:26.882: client 0: wait 10 1
2026-02-26 18:48:27.882: client 0: awake
2026-02-26 18:48:27.882: client 0: wait 10 1
2026-02-26 18:48:28.882: client 0: awake
2026-02-26 18:48:28.882: client 0: wait 10 1
2026-02-26 18:48:29.883: client 0: awake
2026-02-26 18:48:29.883: client 0: wait 10 1
2026-02-26 18:48:30.883: client 0: awake
2026-02-26 18:48:30.883: client 0: wait 10 1
2026-02-26 18:48:31.883: client 0: awake
2026-02-26 18:48:31.883: client 0: wait 10 1
2026-02-26 18:48:32.883: client 0: awake
2026-02-26 18:48:32.883: client 0: wait 10 1
2026-02-26 18:48:33.883: client 0: awake
2026-02-26 18:48:33.883: client 0: wait 10 1
2026-02-26 18:48:34.883: client 0: awake
2026-02-26 18:48:34.883: client 0: wait 10 1
2026-02-26 18:48:35.883: client 0: awake
2026-02-26 18:48:35.883: client 0: wait 10 1
2026-02-26 18:48:36.883: client 0: awake
2026-02-26 18:48:36.883: client 0: wait 10 1
2026-02-26 18:48:37.883: client 0: awake
2026-02-26 18:48:37.883: client 0: wait 10 1
2026-02-26 18:48:38.883: client 0: awake
2026-02-26 18:48:38.883: client 0: wait 10 1
2026-02-26 18:48:38.885: server awake
2026-02-26 18:48:38.885: listen_handle 00000224
2026-02-26 18:48:38.885: client 10: connecting...
2026-02-26 18:48:38.885: client 10: validating...
2026-02-26 18:48:38.885: client 10: process 000001e4
2026-02-26 18:48:38.885: client 10: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:38.885: client 10: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:38.885: client 10: connected
2026-02-26 18:48:38.885: listen_handle ffffffff
2026-02-26 18:48:38.885: client 10: awake
2026-02-26 18:48:38.885: listening...
2026-02-26 18:48:38.885: client 10: data read size 0
2026-02-26 18:48:38.885: client 10: read pipe 0 8
2026-02-26 18:48:38.885: client 10: got command 00 0
2026-02-26 18:48:38.885: client 10: write pipe 0 12
2026-02-26 18:48:38.886: connect error 997
2026-02-26 18:48:38.886: client 10: data read size 0
2026-02-26 18:48:38.886: client 10: read pipe 101 8
2026-02-26 18:48:38.886: client 10: got command 65 0
2026-02-26 18:48:38.886: client 10: write pipe 0 12
2026-02-26 18:48:38.886: server wait 2 0
2026-02-26 18:48:38.886: client 10: data read size 0
2026-02-26 18:48:38.886: client 10: read pipe 98 8
2026-02-26 18:48:38.886: client 10: got command 62 0
2026-02-26 18:48:38.886: client 10: write pipe 0 12
2026-02-26 18:48:38.886: client 10: ReadFile failed 109
2026-02-26 18:48:38.886: client 10: update read failed
2026-02-26 18:48:38.886: server awake
2026-02-26 18:48:38.886: event 1 018b0048
2026-02-26 18:48:38.886: client 10: disconnected
2026-02-26 18:48:38.886: client disconnected
2026-02-26 18:48:38.886: listen_handle 000003b0
2026-02-26 18:48:38.886: pipe listen GetOverlappedResult 996
2026-02-26 18:48:38.886: server wait 2 0
2026-02-26 18:48:39.883: client 0: awake
2026-02-26 18:48:39.883: client 0: wait 10 1
2026-02-26 18:48:40.883: client 0: awake
2026-02-26 18:48:40.883: open volume \\?\Volume{.......................-806e6f6e6963}
2026-02-26 18:48:40.883: GetVolumeInformationW \\?\Volume{.......................-806e6f6e6963} 3
2026-02-26 18:48:40.883: opened ffffffff 0.000053
2026-02-26 18:48:40.883: client 0: open volume 2 ffffffff
2026-02-26 18:48:40.883: client 0: update monitor 2 read: hcjoverlapped ffffffff
2026-02-26 18:48:40.883: check journal ids volume ffffffff
2026-02-26 18:48:40.883: DeviceIoControl failed 3 (\\?\Volume{.......................-806e6f6e6963}) retrying in 30 seconds...
2026-02-26 18:48:40.883: open volume \\?\Volume{.......................-5139169e8464}
2026-02-26 18:48:40.883: GetVolumeInformationW \\?\Volume{.......................-5139169e8464} 3
2026-02-26 18:48:40.883: opened ffffffff 0.000033
2026-02-26 18:48:40.883: client 0: open volume 3 ffffffff
2026-02-26 18:48:40.883: client 0: update monitor 3 read: hcjoverlapped ffffffff
2026-02-26 18:48:40.883: check journal ids volume ffffffff
2026-02-26 18:48:40.883: DeviceIoControl failed 3 (\\?\Volume{.......................-5139169e8464}) retrying in 30 seconds...
2026-02-26 18:48:40.883: client 0: wait 10 1
2026-02-26 18:48:41.612: server awake
2026-02-26 18:48:41.612: listen_handle 000003b0
2026-02-26 18:48:41.612: client 11: connecting...
2026-02-26 18:48:41.612: client 11: validating...
2026-02-26 18:48:41.612: client 11: process 000001e4
2026-02-26 18:48:41.612: client 11: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:41.612: client 11: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:41.612: client 11: connected
2026-02-26 18:48:41.612: listen_handle ffffffff
2026-02-26 18:48:41.612: client 11: awake
2026-02-26 18:48:41.612: listening...
2026-02-26 18:48:41.612: connect error 997
2026-02-26 18:48:41.613: server wait 2 0
2026-02-26 18:48:41.613: client 11: data read size 0
2026-02-26 18:48:41.613: client 11: read pipe 0 8
2026-02-26 18:48:41.613: client 11: got command 00 0
2026-02-26 18:48:41.613: client 11: write pipe 0 12
2026-02-26 18:48:41.613: client 11: data read size 0
2026-02-26 18:48:41.613: client 11: read pipe 97 8
2026-02-26 18:48:41.613: client 11: got command 61 0

Service Debug /ro/

Code: Select all

2026-02-26 18:48:20.879: Everything 1.5.0.1405a (x86)
2026-02-26 18:48:20.879: OS: Windows NT 6.1 7601 (x64)
2026-02-26 18:48:20.879: Admin: 1
2026-02-26 18:48:20.879: Service: 1 (connected / installed and running)
2026-02-26 18:48:20.880: Command line: -svc
2026-02-26 18:48:20.880: Binary: C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:20.880: Profile: C:\DEV\Locate\15.1405\Everything-1.5a.ini
2026-02-26 18:48:20.880: Database: C:\DEV\Locate\15.1405\Everything-1.5a.db
2026-02-26 18:48:20.880: Instance: 1.5a
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Config:
2026-02-26 18:48:20.880: columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Policy:
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: Plugins:
2026-02-26 18:48:20.880: 
2026-02-26 18:48:20.880: client 8: client 0 0000017c 1 0 8 ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor count: 10
2026-02-26 18:48:20.880: client 8: ntfs monitor 0: \\?\Volume{.......................-09c64c792a24} 2 1 0 0 000001d8 00000198
2026-02-26 18:48:20.880: client 8: ntfs monitor 1: \\?\Volume{.......................-7713ca54f116} 3 1 0 1000 000001dc 000001a0
2026-02-26 18:48:20.880: client 8: ntfs monitor 2: \\?\Volume{.......................-806e6f6e6963} 1 2 0 30000 ffffffff ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor 3: \\?\Volume{.......................-5139169e8464} 1 2 0 30000 ffffffff ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor 4: \\?\Volume{.......................-3a83d8b46a3a} 2 1 0 0 ffffffff 000001a8
2026-02-26 18:48:20.880: client 8: ntfs monitor 5: \\?\Volume{.......................-fc757594da94} 2 1 0 0 ffffffff 000001b0
2026-02-26 18:48:20.880: client 8: ntfs monitor 6: \\?\Volume{.......................-bd601c5ecf5d} 2 1 0 0 ffffffff 000001b8
2026-02-26 18:48:20.880: client 8: ntfs monitor 7: \\?\Volume{.......................-40d21d415d94} 2 1 0 0 ffffffff 000001c0
2026-02-26 18:48:20.880: client 8: ntfs monitor 8: \\?\Volume{.......................-2796ba3da1c3} 2 1 0 0 ffffffff 000001c8
2026-02-26 18:48:20.880: client 8: ntfs monitor 9: \\?\Volume{.......................-aec9ea04d92e} 2 1 0 0 ffffffff 000001d0
2026-02-26 18:48:20.880: client 8: refs monitor count: 0
2026-02-26 18:48:20.880: client 8: client 8 000003b0 0 1 0 ffffffff
2026-02-26 18:48:20.880: client 8: ntfs monitor count: 0
2026-02-26 18:48:20.880: client 8: refs monitor count: 0
2026-02-26 18:48:20.880: client 8: write pipe 0 8
2026-02-26 18:48:20.880: client 8: wait 2 0
2026-02-26 18:48:20.880: client 8: awake
2026-02-26 18:48:20.880: client 8: pipe read event
2026-02-26 18:48:20.880: client 8: GetOverlappedResult failed 109
2026-02-26 18:48:20.881: client 8: update read failed
2026-02-26 18:48:20.881: server awake
2026-02-26 18:48:20.881: event 1 018b0048
2026-02-26 18:48:20.881: client 8: disconnected
2026-02-26 18:48:20.881: client 0: awake
2026-02-26 18:48:20.881: client 0: pipe read event
2026-02-26 18:48:20.881: client disconnected
2026-02-26 18:48:20.881: listen_handle 00000144
2026-02-26 18:48:20.881: pipe listen GetOverlappedResult 996
2026-02-26 18:48:20.881: server wait 2 0
2026-02-26 18:48:20.881: client 0: data read size 44
2026-02-26 18:48:20.881: client 0: read pipe 34 52
2026-02-26 18:48:20.881: client 0: got command 22 44
2026-02-26 18:48:20.881: client 0: write pipe 0 288
2026-02-26 18:48:20.881: client 0: wait 9 1
2026-02-26 18:48:20.881: client 0: awake
2026-02-26 18:48:20.881: client 0: pipe read event
2026-02-26 18:48:20.881: client 0: data read size 44
2026-02-26 18:48:20.881: client 0: read pipe 34 52
2026-02-26 18:48:20.881: client 0: got command 22 44
2026-02-26 18:48:20.881: client 0: write pipe 0 16
2026-02-26 18:48:20.881: client 0: data read size 12
2026-02-26 18:48:20.881: client 0: read pipe 35 20
2026-02-26 18:48:20.881: client 0: got command 23 12
2026-02-26 18:48:20.881: client 0: write pipe 0 131
2026-02-26 18:48:20.881: client 0: data read size 12
2026-02-26 18:48:20.881: client 0: read pipe 35 20
2026-02-26 18:48:20.882: client 0: got command 23 12
2026-02-26 18:48:20.882: client 0: write pipe 0 65
2026-02-26 18:48:20.882: client 0: data read size 44
2026-02-26 18:48:20.882: client 0: read pipe 34 52
2026-02-26 18:48:20.882: client 0: got command 22 44
2026-02-26 18:48:20.882: client 0: write pipe 0 16
2026-02-26 18:48:20.882: client 0: data read size 44
2026-02-26 18:48:20.882: client 0: read pipe 33 52
2026-02-26 18:48:20.882: client 0: got command 21 44
2026-02-26 18:48:20.882: client 0: RESUME NTFS 1 3
2026-02-26 18:48:20.882: client 0: write pipe 0 8
2026-02-26 18:48:20.882: client 0: wait 9 1
2026-02-26 18:48:21.882: client 0: awake
2026-02-26 18:48:21.882: client 0: update monitor 1 read: hcjoverlapped 000001a0
2026-02-26 18:48:21.882: client 0: READING NTFS 1 9
2026-02-26 18:48:21.882: client 0: wait 10 1
2026-02-26 18:48:22.882: client 0: awake
2026-02-26 18:48:22.882: client 0: wait 10 1
2026-02-26 18:48:23.882: client 0: awake
2026-02-26 18:48:23.882: client 0: wait 10 1
2026-02-26 18:48:24.882: client 0: awake
2026-02-26 18:48:24.882: client 0: wait 10 1
2026-02-26 18:48:25.882: client 0: awake
2026-02-26 18:48:25.882: client 0: wait 10 1
2026-02-26 18:48:26.645: server awake
2026-02-26 18:48:26.645: listen_handle 00000144
2026-02-26 18:48:26.645: client 9: connecting...
2026-02-26 18:48:26.645: client 9: validating...
2026-02-26 18:48:26.645: client 9: process 000001e4
2026-02-26 18:48:26.646: client 9: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:26.646: client 9: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:26.646: client 9: connected
2026-02-26 18:48:26.646: listen_handle ffffffff
2026-02-26 18:48:26.646: client 9: awake
2026-02-26 18:48:26.646: listening...
2026-02-26 18:48:26.646: client 9: data read size 0
2026-02-26 18:48:26.646: client 9: read pipe 0 8
2026-02-26 18:48:26.646: client 9: got command 00 0
2026-02-26 18:48:26.646: client 9: write pipe 0 12
2026-02-26 18:48:26.646: connect error 997
2026-02-26 18:48:26.646: server wait 2 0
2026-02-26 18:48:26.646: client 9: ReadFile failed 109
2026-02-26 18:48:26.646: client 9: update read failed
2026-02-26 18:48:26.646: server awake
2026-02-26 18:48:26.646: event 1 018b0048
2026-02-26 18:48:26.646: client 9: disconnected
2026-02-26 18:48:26.646: client disconnected
2026-02-26 18:48:26.646: listen_handle 00000224
2026-02-26 18:48:26.646: pipe listen GetOverlappedResult 996
2026-02-26 18:48:26.646: server wait 2 0
2026-02-26 18:48:26.882: client 0: awake
2026-02-26 18:48:26.882: client 0: wait 10 1
2026-02-26 18:48:27.882: client 0: awake
2026-02-26 18:48:27.882: client 0: wait 10 1
2026-02-26 18:48:28.882: client 0: awake
2026-02-26 18:48:28.882: client 0: wait 10 1
2026-02-26 18:48:29.883: client 0: awake
2026-02-26 18:48:29.883: client 0: wait 10 1
2026-02-26 18:48:30.883: client 0: awake
2026-02-26 18:48:30.883: client 0: wait 10 1
2026-02-26 18:48:31.883: client 0: awake
2026-02-26 18:48:31.883: client 0: wait 10 1
2026-02-26 18:48:32.883: client 0: awake
2026-02-26 18:48:32.883: client 0: wait 10 1
2026-02-26 18:48:33.883: client 0: awake
2026-02-26 18:48:33.883: client 0: wait 10 1
2026-02-26 18:48:34.883: client 0: awake
2026-02-26 18:48:34.883: client 0: wait 10 1
2026-02-26 18:48:35.883: client 0: awake
2026-02-26 18:48:35.883: client 0: wait 10 1
2026-02-26 18:48:36.883: client 0: awake
2026-02-26 18:48:36.883: client 0: wait 10 1
2026-02-26 18:48:37.883: client 0: awake
2026-02-26 18:48:37.883: client 0: wait 10 1
2026-02-26 18:48:38.883: client 0: awake
2026-02-26 18:48:38.883: client 0: wait 10 1
2026-02-26 18:48:38.885: server awake
2026-02-26 18:48:38.885: listen_handle 00000224
2026-02-26 18:48:38.885: client 10: connecting...
2026-02-26 18:48:38.885: client 10: validating...
2026-02-26 18:48:38.885: client 10: process 000001e4
2026-02-26 18:48:38.885: client 10: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:38.885: client 10: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:38.885: client 10: connected
2026-02-26 18:48:38.885: listen_handle ffffffff
2026-02-26 18:48:38.885: client 10: awake
2026-02-26 18:48:38.885: listening...
2026-02-26 18:48:38.885: client 10: data read size 0
2026-02-26 18:48:38.885: client 10: read pipe 0 8
2026-02-26 18:48:38.885: client 10: got command 00 0
2026-02-26 18:48:38.885: client 10: write pipe 0 12
2026-02-26 18:48:38.886: connect error 997
2026-02-26 18:48:38.886: client 10: data read size 0
2026-02-26 18:48:38.886: client 10: read pipe 101 8
2026-02-26 18:48:38.886: client 10: got command 65 0
2026-02-26 18:48:38.886: client 10: write pipe 0 12
2026-02-26 18:48:38.886: server wait 2 0
2026-02-26 18:48:38.886: client 10: data read size 0
2026-02-26 18:48:38.886: client 10: read pipe 98 8
2026-02-26 18:48:38.886: client 10: got command 62 0
2026-02-26 18:48:38.886: client 10: write pipe 0 12
2026-02-26 18:48:38.886: client 10: ReadFile failed 109
2026-02-26 18:48:38.886: client 10: update read failed
2026-02-26 18:48:38.886: server awake
2026-02-26 18:48:38.886: event 1 018b0048
2026-02-26 18:48:38.886: client 10: disconnected
2026-02-26 18:48:38.886: client disconnected
2026-02-26 18:48:38.886: listen_handle 000003b0
2026-02-26 18:48:38.886: pipe listen GetOverlappedResult 996
2026-02-26 18:48:38.886: server wait 2 0
2026-02-26 18:48:39.883: client 0: awake
2026-02-26 18:48:39.883: client 0: wait 10 1
2026-02-26 18:48:40.883: client 0: awake
2026-02-26 18:48:40.883: open volume \\?\Volume{.......................-806e6f6e6963}
2026-02-26 18:48:40.883: GetVolumeInformationW \\?\Volume{.......................-806e6f6e6963} 3
2026-02-26 18:48:40.883: opened ffffffff 0.000053
2026-02-26 18:48:40.883: client 0: open volume 2 ffffffff
2026-02-26 18:48:40.883: client 0: update monitor 2 read: hcjoverlapped ffffffff
2026-02-26 18:48:40.883: check journal ids volume ffffffff
2026-02-26 18:48:40.883: DeviceIoControl failed 3 (\\?\Volume{.......................-806e6f6e6963}) retrying in 30 seconds...
2026-02-26 18:48:40.883: open volume \\?\Volume{.......................-5139169e8464}
2026-02-26 18:48:40.883: GetVolumeInformationW \\?\Volume{.......................-5139169e8464} 3
2026-02-26 18:48:40.883: opened ffffffff 0.000033
2026-02-26 18:48:40.883: client 0: open volume 3 ffffffff
2026-02-26 18:48:40.883: client 0: update monitor 3 read: hcjoverlapped ffffffff
2026-02-26 18:48:40.883: check journal ids volume ffffffff
2026-02-26 18:48:40.883: DeviceIoControl failed 3 (\\?\Volume{.......................-5139169e8464}) retrying in 30 seconds...
2026-02-26 18:48:40.883: client 0: wait 10 1
2026-02-26 18:48:41.612: server awake
2026-02-26 18:48:41.612: listen_handle 000003b0
2026-02-26 18:48:41.612: client 11: connecting...
2026-02-26 18:48:41.612: client 11: validating...
2026-02-26 18:48:41.612: client 11: process 000001e4
2026-02-26 18:48:41.612: client 11: exe C:\DEV\Locate\15.1405\Everything.exe
2026-02-26 18:48:41.612: client 11: 018b0048, read buf 018c0048, write buf 018b0048
2026-02-26 18:48:41.612: client 11: connected
2026-02-26 18:48:41.612: listen_handle ffffffff
2026-02-26 18:48:41.612: client 11: awake
2026-02-26 18:48:41.612: listening...
2026-02-26 18:48:41.612: connect error 997
2026-02-26 18:48:41.613: server wait 2 0
2026-02-26 18:48:41.613: client 11: data read size 0
2026-02-26 18:48:41.613: client 11: read pipe 0 8
2026-02-26 18:48:41.613: client 11: got command 00 0
2026-02-26 18:48:41.613: client 11: write pipe 0 12
2026-02-26 18:48:41.613: client 11: data read size 0
2026-02-26 18:48:41.613: client 11: read pipe 97 8
2026-02-26 18:48:41.613: client 11: got command 61 0

[void]

Thanks for the latest logs therube,

It's a bug with WinVerifyTrust on Windows 7.
WinVerifyTrust fails for moved exe files on Windows 7.
WinVerifyTrust will cache the initial check and that will succeed.
Once you move the exe file, WinVerifyTrust will fail.
A reboot will clear the cache.

The Everything Service MUST check and validate the signature of the client exe by default to fix CVE-2025-12683.

Please re-enable service_allow_untrusted_connections:

• From the Start menu, search for:
  regedit
• Right click Registry Editor and click Run as administrator.
• In the Registry Editor, navigate to:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies
• Create the following key:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools
• Create the following key:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\voidtools\Everything
• In this new key, on the right, create a new DWORD value.
• Set the value name to:
  service_allow_untrusted_connections
• Set the value data to:
  1

The issue doesn't exist on Windows 10 and later.
WinVerifyTrust will succeed for moved exe files on Windows 10 and later.