Everything Normal Service won't start

[nagan]

949b Win 7 X64
Logged in as Admin. Ensured no service is running. Logged in as a standard user. Attempted to start service. It immediately puts an alert that it cannot run as Admin , but still Everything service box remains ticked. I untick that , and again get the same message.
1.If it could not run the service , it should be either unticked or indeterminate?

Came back to the Admin.Tried to start Service.
2.Service would not start. A certain Bug.

[void]

Thanks for the bug report.

Logged in as Admin. Ensured no service is running. Logged in as a standard user. Attempted to start service. It immediately puts an alert that it cannot run as Admin

When you install the Everything service from the general options, Everything will execute the following command:

Code: Select all

Everything.exe -install-service

This command should request a UAC prompt.
I think you mention before you have the UAC prompt disable, although this should still run the command as admin.

Please try running Everything in debug mode to see if there are any errors when running this command.
Check for the following error message:

Code: Select all

ShellExecuteExW(): GetLastError(): 1223: failed to execute C:\...\Everything.exe

Try running this command manually from a command prompt with a standard user account.
Are there any programs that might stop this process from running as admin on your computer?

but still Everything service box remains ticked. I untick that , and again get the same message.
1.If it could not run the service , it should be either unticked or indeterminate?

I have changed this for the next release, the checkbox will stay checked, but you will receive an error message and should be able to hit apply again.

Came back to the Admin.Tried to start Service.
2.Service would not start. A certain Bug.

The service would not start as admin? was there any error messages?
Does

Code: Select all

Everything.exe -start-service

give any errors messages?
If its reproducible please send some debug output.

[nagan]

When I try to launch service from UI I get 1072 error. Thru command prompt if I tried the error message is 1058.

I have attached the debug info while launching thru UI.

Code: Select all

load localization
load everything icon
create mutex
bookmarks
set hook
create tray
db_load
new thread (0)
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 864 0.000627
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 868 0.000491
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 868 0.000688
WM_ACTIVATE 00000001 00000000, lastfocus 00000000, current focus 00000000
update filesystem C:
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 872 0.000435
updated in 0.000967 seconds
update filesystem D:
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 888 0.000307
updated in 0.000595 seconds
update filesystem F:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 892 0.000776
updated in 0.001451 seconds
loaded db in 0.061534 seconds
enter setfocus
leave setfocus
invalidate
enter main loop
_DB_WAIT: _db_load_successful_proc waiting...
_DB_WAIT: _db_load_successful_proc waited 0.000518 seconds
start all monitors (3)
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 900 0.000991
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
search '' filter ''
term 00706588, flags: 0148, next: 00000000, notnext: 00000000
folderop: 0, fileop: 0, term:
new thread (1)
opened 912 0.000862
found 30433 folders, size 131460, db search time taken: 0.000056 seconds
_DB_WAIT: db_get_result_count waiting...
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
found 194554 files, size 787464, db search time taken: 0.001013 seconds
opened 932 0.002479
waiting for 4 handles, isdelay 0...
_DB_WAIT: db_get_result_count waited 0.003736 seconds
new thread (2)
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000085 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001989 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000049 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001263 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000245 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.003073 seconds
WM_INITMENUPOP 00af085d 00000005
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000000 008d0838, lastfocus 00200f98, current focus 00200f98
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000181 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.003059 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000058 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002234 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000001 008d0838, lastfocus 00200f98, current focus 008d0838
WM_INITMENUPOP 00af085d 00000005
WM_ACTIVATE 00000000 001e0e98, lastfocus 00200f98, current focus 00200f98
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000180 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000235 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000001 001e0e98, lastfocus 00200f98, current focus 001e0e98
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000239 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001098 seconds
waiting for 4 handles, isdelay 0...
destroy ui
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
WM_ACTIVATE 00000000 00a90a78, lastfocus 00200f98, current focus 00200f98
update filesystem C:
updated in 0.000149 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.001249 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000073 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002565 seconds
waiting for 4 handles, isdelay 0...

Let me know if you need any other details.In Xp it works fine. This issue I find in Win 7 x 64.

[void]

Thanks for the debug info.

Error code 1072: ERROR_SERVICE_MARKED_FOR_DELETE

This will occur if you tried to delete the Everything service when it was still running.
I am not certain how this error is occurring because Everything should stop the service before uninstalling it from the UI or command line.

Restarting your computer will delete the service and should fix the problem.

Error code 1058: ERROR_SERVICE_DISABLED

I think this is related to the above error, please try restarting your computer.

Does Task Manager still show an Everything process running as system?
(Make sure you check show processes from all users)

[nagan]

Does Task Manager still show an Everything process running as system?
(Make sure you check show processes from all users)

From the Task Manager it appears the service is stopped. I generally do not run the service. Just to check if the crash while trying to run service from standard user is fixed , I ran it today. That aspect has been taken care of and it does not loop now. Please check whether any introduction of this edition is not causing the present issue. For the time I prefer to keep the system under hibernation/resume and will let you know when I restart.

[void]

There does seem to be a small delay (~30 seconds) when deleting the service, during this time if you try to re-install the service you will get the 1072 error message.

I will look into this issue more..

[nagan]

Ok. I restarted my Win 7 x 64 system and then tried to run the service from 649b. It does not run , but strangely no errors also. I close it and run 645b , and try to run the service. It runs fine and shows up in the Process explorer. I have attached the debugs of both.
649b - Service not working..

Code: Select all

load localization
load everything icon
create mutex
bookmarks
set hook
create tray
db_load
new thread (0)
SHChangeNotifyRegister: 1 299
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 900 0.000922
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 900 0.000590
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
WM_ACTIVATE 00000001 00000000, lastfocus 00000000, current focus 00000000
opened 900 0.000376
enter setfocus
leave setfocus
invalidate
enter main loop
update filesystem C:
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 896 0.000337
updated in 0.000774 seconds
update filesystem D:
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 908 0.000848
updated in 0.001560 seconds
update filesystem F:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 912 0.000712
updated in 0.001143 seconds
loaded db in 0.087184 seconds
_DB_WAIT: _db_load_successful_proc waiting...
_DB_WAIT: _db_load_successful_proc waited 0.001040 seconds
start all monitors (3)
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 920 0.000348
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
search '' filter ''
opened 924 0.000685
term 0073f758, flags: 014a, next: 00000000, notnext: 00000000
folderop: 0, fileop: 0, term:
new thread (1)
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
_DB_WAIT: db_get_selection_count waiting...
found 30391 folders, size 131460, db search time taken: 0.000092 seconds
opened 948 0.002226
found 193270 files, size 787460, db search time taken: 0.000772 seconds
waiting for 4 handles, isdelay 0...
_DB_WAIT: db_get_selection_count waited 0.003238 seconds
new thread (2)
WM_INITMENUPOP 00130885 00000005
WM_ACTIVATE 00000000 000609e2, lastfocus 00090984, current focus 00090984
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000158 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.003454 seconds
DeviceIoControl already complete (C:)!
waiting for 3 handles, isdelay 1...
update filesystem C:
updated in 0.000144 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002159 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
update filesystem C:
updated in 0.000123 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000790 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000001 000609e2, lastfocus 00090984, current focus 000609e2
WM_ACTIVATE 00000000 00000000, lastfocus 00090984, current focus 00090984
WM_ACTIVATE 00000001 00000000, lastfocus 00090984, current focus 00000000
WM_INITMENUPOP 00130885 00000005
WM_ACTIVATE 00000000 000f0986, lastfocus 00090984, current focus 00090984
WM_ACTIVATE 00000001 000f0986, lastfocus 00090984, current focus 000f0986
WM_ACTIVATE 00200000 00000000, lastfocus 00090984, current focus 00000000

645b -Service Working

Code: Select all

load localization
load everything icon
create mutex
bookmarks
set hook
create tray
db_load
create thread PeakWorkingSetSize: 15253504, WorkingSetSize: 15253504
SHChangeNotifyRegister: 1 299
WM_ACTIVATE 00000001 00000000, lastfocus 00000000, current focus 00000000
enter setfocus
leave setfocus
invalidate
enter main loop
update filesystem C:
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 900 0.000276
updated in 0.000506 seconds
update filesystem D:
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
opened 888 0.000149
updated in 0.000244 seconds
update filesystem F:
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
opened 908 0.000145
updated in 0.000342 seconds
loaded db in 0.077646 seconds
_DB_WAIT: _db_load_successful_proc waiting...
_DB_WAIT: _db_load_successful_proc waited 0.001544 seconds
start all monitors (3)
create thread PeakWorkingSetSize: 26361856, WorkingSetSize: 26333184
open volume \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963}
opened 864 0.000740
search '' filter ''
open volume \\?\Volume{4664a6b1-8fed-11e1-8c14-806e6f6e6963}
term 003c5bb0, flags: 014a, next: 00000000, notnext: 00000000
folderop: 0, fileop: 0, term:
create thread PeakWorkingSetSize: 26390528, WorkingSetSize: 26390528
opened 912 0.001257
_DB_WAIT: db_get_selection_count waiting...
found 30391 folders, size 131460, db search time taken: 0.000099 seconds
open volume \\?\Volume{1e20383c-a7d0-11e2-901b-dd8a203cfbaa}
found 193271 files, size 787460, db search time taken: 0.000718 seconds
opened 924 0.001931
waiting for 4 handles, isdelay 0...
_DB_WAIT: db_get_selection_count waited 0.003507 seconds
create thread PeakWorkingSetSize: 27336704, WorkingSetSize: 27336704
create thread PeakWorkingSetSize: 27353088, WorkingSetSize: 27353088
WM_INITMENUPOP 0197010d 00000005
WM_ACTIVATE 00000000 000e09e0, lastfocus 000a0818, current focus 000a0818
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
create thread PeakWorkingSetSize: 28450816, WorkingSetSize: 28389376
update filesystem C:
updated in 0.000551 seconds
_DB_WAIT: _db_ready_proc waiting...
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waited 0.004172 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
create thread PeakWorkingSetSize: 28532736, WorkingSetSize: 28532736
update filesystem C:
updated in 0.000039 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002145 seconds
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
create thread PeakWorkingSetSize: 28569600, WorkingSetSize: 28565504
update filesystem C:
waiting for 3 handles, isdelay 1...
updated in 0.000182 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000848 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000001 000e09e0, lastfocus 000a0818, current focus 000e09e0
WM_ACTIVATE 00000000 00000000, lastfocus 000a0818, current focus 000a0818
WM_ACTIVATE 00000001 00000000, lastfocus 000a0818, current focus 00000000
WM_INITMENUPOP 0197010d 00000005
WM_ACTIVATE 00000000 000909aa, lastfocus 000a0818, current focus 000a0818
WM_ACTIVATE 00000001 000909aa, lastfocus 000a0818, current focus 000909aa
create thread PeakWorkingSetSize: 28876800, WorkingSetSize: 28565504
update filesystem C:
updated in 0.000180 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000758 seconds
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 1...
waiting for 3 handles, isdelay 1...
waiting for 4 handles, isdelay 0...
Updating \\?\Volume{4664a6b0-8fed-11e1-8c14-806e6f6e6963} (C:):
waiting for 3 handles, isdelay 0...
create thread PeakWorkingSetSize: 28876800, WorkingSetSize: 28565504
update filesystem C:
updated in 0.000054 seconds
waiting for 3 handles, isdelay 1...
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.002499 seconds
waiting for 4 handles, isdelay 0...
WM_ACTIVATE 00000000 00000000, lastfocus 000a0818, current focus 000a0818
WM_ACTIVATE 00000001 00000000, lastfocus 000a0818, current focus 00000000
WM_ACTIVATE 00200000 00000000, lastfocus 000a0818, current focus 00000000

[void]

Thanks for the debug output.

The debug logs do not show any attempt to install the Everything service.



This issue appears to be cause by having the UAC set to Never notify and being logged in with a normal user account.

649 should display an error message stating that Everything failed to run as administrator.
645 will get stuck in a nasty loop.

Everything can not run as administrator if you have the UAC set to Never notify and are logged in with a normal user account.

You will need to install the service with an administrator account or increase the UAC notify to atleast: notify me only when programs try to make changes to my computer.

[nagan]

This issue appears to be cause by having the UAC set to Never notify and being logged in with a normal user account.

No I logged in as Admin.And 649b service runs fine in XP. Normal user = Standard user?
How is it that service of 645b works and not 649b in the Admin mode?
I have UAC set to Never Notify , because it hampers or silently kills many older applications.Can the shortcut/Properties >>compatibility be altered to run as a Admin?

[void]

Normal user = Standard user?

Yes

What happens if you try to install the 649b service manually from the command line with admin privileges:

Code: Select all

Everything.exe -install-service

I think I know what is happening, the 645b service is still running or is marked for deletion.
When you try to install 649b it will not work (error 1072), its strange that there is no error message...

Please make sure the service is uninstalled in 645b and restart your computer.
You should be able to install the 649b service after the restart.

Can the shortcut/Properties >>compatibility be altered to run as a Admin?

You can not run Everything as administrator if you login with a standard user account with the UAC set to never notify.
shortcut/Properties >>compatibility -> run as a Admin will be grayed out.

[nagan]

The process explorer always shows an entry for Service when it is started thru 645b and also shows it being terminated when it is closed.
I can confirm there is no entry against everything except one number of the present running instance.
All these discussions pertain to the Admin log in only.Unless ofcourse certain issues where I have mentioned the log in as a standard user.

What happens if you try to install the 649b service manually from the command line with admin privileges:
Code: Select all
Everything.exe -install-service

I get the 1072 error.

[void]

This error message is not displayed when installing the Everything service in 649b fails?

[nagan]

This error message is not displayed when installing the Everything service in 649b fails?

Strangely as I write now , I get the 1072 error even when launched from the GUI.The earlier post was for the one from command line. Now with both command line normal and with Admin privileges I get 1058 (not 1072 )) error.

[void]

That is what should occur, strange that it was not showing the error messages before, I will keep an eye on it, please do the same..

Restarting will fix both errors.

[nagan]

Strange occurence now. Even 645b presents 1072 error when I tried it thru UI right now. Strangely after a restart I first checked 649b only. When it gave the 1072 error , I tried 645b and it seemed to open fine. Now even that is showing up.

What difference does it make to service installation if there are already other logged in users but trying to open the service thru Admin log in?

[nagan]

What difference does it make to service installation if there are already other logged in users but trying to open the service thru Admin log in?

Ok.I logged off all users except Admin, logged in as Admin and now I am able to start the service in 645b. But strangely not working for 649b. I do not think restarting is going to help my system as I had seen it early today. Do you conceive any essential difference between the service operation of 645b and 649b.,..

[void]

What difference does it make to service installation if there are already other logged in users but trying to open the service thru Admin log in?

Installing or uninstalling the service causes the 1072 1058 issue when multiple users are logged in.
I will review this for the next release.

Do you conceive any essential difference between the service operation of 645b and 649b.,..

None, but its related to which one you installed first.
The 645b service was installed first and is still register as a service but is marked for deletion.

[nagan]

As a test case , I made a registry search and found the following entry in the Registry..Registry Key : HKLM\SYSTEM\CurrentControlSet\services\Everything
Name : ImagePath
Type : REG_EXPAND_SZ
Data : "C:\Program Files (x86)\Everything\Everything-1.3.2.645b\Everything\Everything.exe" -svc
Key Modified Time : 09/05/2013 18:50:37
Data Length : 89
There was no entry similiar to that of 649b.
Next I deleted the key "Everything"totally under HKLM\SYSTEM\CurrentControlSet\services. Now when I launch the services from 649b , I get 2 alerts --1.Unable to update service 2,2.Unable to start service 3. It has to do something with this only.

[void]

There was no entry similiar to that of 649b.

Nor should there be, you can only install one instance of the Everything service.
It doesn't matter which version you install it from, the service is compatible with any version of Everything.

Now when I launch the services from 649b , I get 2 alerts --1.Unable to update service 2,2.Unable to start service 3. It has to do something with this only.

What are the error codes?

[nagan]

I will post the error codes ie from the command prompt a little later . The alerts I recd from UI was posted.
Meanwhile in XP I made a registry search when the service from 649b is started , and it correctly leads to "C:\Program Files\Everything\Everything-1.3.2.649b\Everything.exe" -svc under HKLM >> Services>> Everything. And if I close the service , the entry does not exist in the registry.So it means in Win 7 the 645b service entry was preventing itself from being updated or as you predicted , is not uninstalling even though the clue given from process explorer is it is closed.

[nagan]

After a restart ,today when I try to start the service from the command line while running 649b , for the first time it created another running instance. Next time it would not start , and there were no messages at all. From GUI of course everytime it does not start and there are no error messages either. From the registry scanner I find against services the entry for 645b version. So obviously in effect it has not terminated. Strange things....
EDIT
Would you consider giving a different name to the started service.

[void]

I try to start the service from the command line while running 649b

What do you mean by start the service from the command line?
Did you use -install-service or -start-service? or -svc??

for the first time it created another running instance.

Was this the service process?
What user name is the process running under?

Next time it would not start

-install-service will do nothing if the service is installed.
-start-service will do nothing if the service is started.

From GUI of course everytime it does not start and there are no error messages either.

Is the Everything service unchecked, checked or indeterminate in the GUI?

Would you consider giving a different name to the started service

Once the service is installed, it should not be renamed.
Renaming the exe would require copying the exe to another filename and running that, something I would rather avoid.

[nagan]

What do you mean by start the service from the command line?
Did you use -install-service or -start-service? or -svc??

I used C:\Program Files (x86)\Everything\Everything-1.3.2.649b\Everything.exe -start-service

Was this the service process?
What user name is the process running under?

It was running as Everything.exe under the same user name. Hence in the image , both the instances though of different PID were referring to the same admin user .

Is the Everything service unchecked, checked or indeterminate in the GUI?

After failing it showed the indeterminate state.

Once the service is installed, it should not be renamed.
Renaming the exe would require copying the exe to another filename and running that, something I would rather avoid.

Ok. I was under some misconception again.

For the day , I started with C:\Program Files (x86)\Everything\Everything-1.3.2.649b\Everything.exe -unistall-service and it gives the same 1072 error.

Átleast there is an improvement that there is some message.Today I exempted Everything from Online Armor a firewall and HIPS software , as it had a reputation for silently suspending (not terminating) softwares without giving (or allowing them to give) any error messages.

I am sorry for having taken your time for this event which seems localised to my system. I will try some other combinations and try to post when it is finally solved.

[void]

I am sorry for having taken your time for this event which seems localised to my system.

Thanks for taking your time to report these issues, I really do appreciate it.
I really want to fix this issue before the next beta release..

Maybe we should start with the 1072 error when trying to uninstall the service.
This might be a future problem when upgrading to a new version of Everything and the old service fails to stop / uninstall.

Are you running multiple instances with 645b / 649b?
This could cause issues, the service should really include the instance name in the service name.

[void]

I have found one issue with -install-service where it does not update the executable path, it might be related.

[nagan]

Ok. For now Online Armor seems to be the main reason why there were misleading clues on the service issue. Now after adding to the exception list , I have been able to start/close 645b , 649bSEPARATELY for quiet some time. So for the time being it seems solved (unless there are some surprises.. .You may choose to add in the write up in general terms( need not take names) where to look to esp HIPS, Antivirus as the first-line if service start does not respond the way it should.
Though it has solved my case for the time being , you may pursue your point as you wish.

[nagan]

I have been observing since yesterday. Just wanted to ensure that it is a one time event .. Those issues of not being able to start the service is trivial to this matter now.
I do not usually shut down and always go with the Hibernate/Resume mode. Since yesterday after a Restart due to 1072 error Everything service is ON and was working fine. Today I tried closing the service from UI in the Admin. There were no errors and looking upon the list in Process Explorer , the service entry was still there. Came back to the UI , which showed indeterminate state for service , I clicked on the box again and pressed apply to get back the 1072 error. Now subsequent ticks to it always got the error. And moreover the Service entry in the PE is closed now. This will not start again from the UI because of the 1072 error.

I think Everything before closing down the Service completely puts up a blank/indeterminate check box which may have lead to this situation.Most probably I have to restart to get things right once again.... Everything is still in the excluded list of the HIPS app , so it is not from there....

EDIT Just wanted to add that at that moment two instances of Everything , one of Admin and Standard user each were running.

[nagan]

Hi,
Have you been able to identify the stray causes of the 1072 error. I was just switching amongst users when the error struck. I am not too sure what caused it , just replaying it.
1. Main user - Able to start and stop(both from the UI as well as Process Explorer PE) many times.
2. Started service , logged in as standard user , built the index.
3. Came back to admin , stopped the service via PE. Logged in as standard user to find only directories seen in the result.
4.Came back to admin , the service indicates indeterminate sign , tried to start service from GUI ,am getting the 1072 error.

[void]

Hi nagan,

1. Main user - Able to start and stop(both from the UI as well as Process Explorer PE) many times.
2. Started service , logged in as standard user , built the index.
3. Came back to admin , stopped the service via PE. Logged in as standard user to find only directories seen in the result.
4.Came back to admin , the service indicates indeterminate sign , tried to start service from GUI ,am getting the 1072 error.

The standard user account showing only root drives after the serviced is stopped is normal.
The indeterminate service state in Everything is normal, since its not running.
However, I have not had any luck reproducing this error 1072 following your steps.

There must be something holding a handle open to this service somewhere.. (Antivirus maybe??)