Service not working
Service not working
I've just tried installing the latest everything..
It appears that the Everything service isn't working..I reverted back to 1384 and the service is fine.
It appears that the Everything service isn't working..I reverted back to 1384 and the service is fine.
Re: Service not working
What do you mean by the service is not working?
Does the service run?
Does Everything detect changes?
What is the service status under Help -> Troubleshooting information?
There was no changes to the Everything Service in 1384 - 1391.
Does the service run?
Does Everything detect changes?
What is the service status under Help -> Troubleshooting information?
There was no changes to the Everything Service in 1384 - 1391.
Re: Service not working
Run as service is ticked, but I'm getting a UAC box pop up.
I've reverted back and the problem goes away.
The service on my computer appears to be running. I haven't made any changes from 1384.
Admin: 0
Service: 1 (connected / installed and running)
I'm using portable everything on Win 7.
This is the first time this has ever happened.
I've reverted back and the problem goes away.
The service on my computer appears to be running. I haven't made any changes from 1384.
Admin: 0
Service: 1 (connected / installed and running)
I'm using portable everything on Win 7.
This is the first time this has ever happened.
Re: Service not working
avoid 1384, it has issues with the alpha instance.
Please try 1391 instead.
Please try 1391 instead.
Re: Service not working
I'm running 1384 since November and it's has been fine.
It's 1391 that I'm having the problem with.
It's 1391 that I'm having the problem with.
Re: Service not working
Maybe it's caused by running 1384.
Please make sure 1391 is installed correctly:
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Compatibility tab.
* Uncheck Run this program as an administrator.
* Click OK.
Please make sure Everything is running as a standard user:
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Shortcut tab.
* Click the Advanced button.
* Uncheck Run as administrator.
* Click OK.
* Click OK.
Please make sure Everything is running as a standard user:
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Compatibility tab.
* Click the Change settings for all users button at the bottom.
* Uncheck Run this program as an administrator.
* Click OK.
Please make sure 1391 is installed correctly:
- In Everything, from the Tools menu, click Options.
- Click the General tab on the left.
- Check Store settings and data in %APPDATA%\Everything.
- Uncheck Run as administrator.
- Check Everything Service. (Please make sure this is tick-checked and not square-checked)
- Click OK.
- Exit Everything (from the File menu, click Exit).
- Restart Everything.
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Compatibility tab.
* Uncheck Run this program as an administrator.
* Click OK.
Please make sure Everything is running as a standard user:
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Shortcut tab.
* Click the Advanced button.
* Uncheck Run as administrator.
* Click OK.
* Click OK.
Please make sure Everything is running as a standard user:
* Right click your Everything.exe or a shortcut to Everything
* Click Properties.
* Click the Compatibility tab.
* Click the Change settings for all users button at the bottom.
* Uncheck Run this program as an administrator.
* Click OK.
Re: Service not working
Everything is running correctly, I have made no changes whatsoever before updating. I've upgraded many times but never come across this problem.
before.
Using the same installation, up to 1390 works, 1391 is the only one with the service problem.
It's definitely 1391 that's causing me problems.versions under 1391 are working fine.
before.
Using the same installation, up to 1390 works, 1391 is the only one with the service problem.
It's definitely 1391 that's causing me problems.versions under 1391 are working fine.
Re: Service not working
I am unable to reproduce the issue on Windows 7/10 with a limited account.
When is the UAC prompt shown? (when you launch Everything? when you perform an action in Everything? is it only once or all the time?)
Please send your Help -> Troubleshooting information.
When is the UAC prompt shown? (when you launch Everything? when you perform an action in Everything? is it only once or all the time?)
Please send your Help -> Troubleshooting information.
Re: Service not working
Thanks David.
File attached..I did a text compare, no difference between the two files.
This Everything is an instance.
D:\david\Everything64.exe -instance david
UAC prompt just appears when starting Everything each time.
File attached..I did a text compare, no difference between the two files.
This Everything is an instance.
D:\david\Everything64.exe -instance david
UAC prompt just appears when starting Everything each time.
Re: Service not working
No, it works fine as it is..I've been running it like this for several years.
Re: Service not working
Could you test the following?
- Exit Everything completely (File => Exit or through the system tray)
- Stop the Everything Service(s?)
- Replace the line:
with:
- Start the service
- Start Everything
( But highly recommended for people like me, who forget the quotes otherwise .. )
- Exit Everything completely (File => Exit or through the system tray)
- Stop the Everything Service(s?)
- Replace the line:
Code: Select all
service_pipe_name=\\.\pipe\Everything Service (1.5a)
Code: Select all
service_pipe_name=
- Start Everything
If there are no spaces or special characters in the instance name, quoting is not strictly needed.
( But highly recommended for people like me, who forget the quotes otherwise .. )
Re: Service not working
Thanks,
Unfortunately, that didn't work..still getting the UAC prompt
Unfortunately, that didn't work..still getting the UAC prompt
Re: Service not working
Thank you for your Help -> Troubleshooting information.
I was unable to reproduce the issue with your settings and david instance.
Are you using the NO_ALPHA_INSTANCE file in the same location as your Everything.exe?
This will control the service pipe name.
With NO_ALPHA_INSTANCE:
\\.\PIPE\Everything Service
Without NO_ALPHA_INSTANCE:
\\.\PIPE\Everything Service (1.5a)
Do you have multiple Everything.exe files?
Is the service running on another Everything.exe ? (different to the one used for your david instance)
-I don't think this is a service issue as the help -> troubleshooting information shows a good connection.
It's very odd that Everything is running as a standard user after the UAC prompt.
Are you cancelling the UAC prompt?
How are you launching Everything?
I was unable to reproduce the issue with your settings and david instance.
Are you using the NO_ALPHA_INSTANCE file in the same location as your Everything.exe?
This will control the service pipe name.
With NO_ALPHA_INSTANCE:
\\.\PIPE\Everything Service
Without NO_ALPHA_INSTANCE:
\\.\PIPE\Everything Service (1.5a)
Do you have multiple Everything.exe files?
Is the service running on another Everything.exe ? (different to the one used for your david instance)
-I don't think this is a service issue as the help -> troubleshooting information shows a good connection.
It's very odd that Everything is running as a standard user after the UAC prompt.
Are you cancelling the UAC prompt?
How are you launching Everything?
Re: Service not working
I have made absolutely no changes whatsoever. There is no problem starting from !390 and downwards.
In fact, I've now switched between 1390, 1384 and 1391 several times, and keep coming up with the same problem only on 1391.
T do have a couple of other instances running under the same service as well, but I haven't started these for quite a while, and again, it's only 1391 that is the problem.
I'm not using a NO_ALPHA_instance, in fact I'm not even sure what that is.
If I was having the same problem with older versions of Everything, I may have though that it's something to do with my system, but, as I mentioned, older versions are working fine.
I normally launch Everything instance (D:\david\Everything64.exe -instance david) from my task bar, but I also tried launching it directly, and directly from the shortcut, but (only) 1391 still brings up the UAC.
Would seeing my ini file help, maybe an entry in there that's affecting 1391?
In fact, I've now switched between 1390, 1384 and 1391 several times, and keep coming up with the same problem only on 1391.
T do have a couple of other instances running under the same service as well, but I haven't started these for quite a while, and again, it's only 1391 that is the problem.
I'm not using a NO_ALPHA_instance, in fact I'm not even sure what that is.
If I was having the same problem with older versions of Everything, I may have though that it's something to do with my system, but, as I mentioned, older versions are working fine.
I normally launch Everything instance (D:\david\Everything64.exe -instance david) from my task bar, but I also tried launching it directly, and directly from the shortcut, but (only) 1391 still brings up the UAC.
Would seeing my ini file help, maybe an entry in there that's affecting 1391?
Re: Service not working
2harryray2 & NotNull
Thank you for your information regarding instance names.
This is what it looks like when I start an 'Everything' instance as an administrator.
File: NO_ALPHA_INSTANCE (without extension!)
Thank you for your information regarding instance names.
This is what it looks like when I start an 'Everything' instance as an administrator.
File: NO_ALPHA_INSTANCE (without extension!)
Re: Service not working
UPDATEharryray2 wrote: ↑Fri Jan 10, 2025 10:58 pm I have made absolutely no changes whatsoever. There is no problem starting from !390 and downwards.
In fact, I've now switched between 1390, 1384 and 1391 several times, and keep coming up with the same problem only on 1391.
T do have a couple of other instances running under the same service as well, but I haven't started these for quite a while, and again, it's only 1391 that is the problem.
I'm not using a NO_ALPHA_instance, in fact I'm not even sure what that is.
If I was having the same problem with older versions of Everything, I may have though that it's something to do with my system, but, as I mentioned, older versions are working fine.
I normally launch Everything instance (D:\david\Everything64.exe -instance david) from my task bar, but I also tried launching it directly, and directly from the shortcut, but (only) 1391 still brings up the UAC.
Would seeing my ini file help, maybe an entry in there that's affecting 1391?
I just created a new blank Everything folder and tried running 1391, with absolutely nothing else in the folder, and I'm still getting the UAC.
Re: Service not working
That doesn't change anything if you don't use a portable version.
You have to remove the Everything ini file to get a fresh environment.
On the first start it will ask how to index.
Select install the service
and let the client start with the system.
Re: Service not working
I have tested this and my guess is that you did NOT change the default setting for portable installations from:
◉ Run indexing process as administrator (recommended) ... to ... ◉ "Install the "Everything" service during installation - please see point 3.
First, use the Task Manager to check that there is NO 'Everything Service' with the status 'Running' - please see point 1 and 8.
Check your 'Everything' instance(s) to see if the option: 'Run indexing process as administrator' is checked.
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
Run indexing process as administrator | Everything Service
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
Re: Service not working
Thanks Tuska,
No, everything is exactly as it has been before..I've always used the portable version.
As I mentioned, Everything has been fine up until the latest version.
I tried running Everything 1391 from scratch with no adjustments apart from Everything service and I still have the same problem, so it's obviously nothing that I have altered in the past that is causing this.
Apart from the context menu entries and services does Everything portable make any registry entries. I'm wondering if anything in the registry is causing this?
It seem unlikely though as it's been fine for several years up to now.
Possibly an entry exclusive o 1391? But again, this seems unlikely as no one else seems to be having this problem.
The Everything service is running as it should.
I'm completely baffled.
No, everything is exactly as it has been before..I've always used the portable version.
As I mentioned, Everything has been fine up until the latest version.
I tried running Everything 1391 from scratch with no adjustments apart from Everything service and I still have the same problem, so it's obviously nothing that I have altered in the past that is causing this.
Apart from the context menu entries and services does Everything portable make any registry entries. I'm wondering if anything in the registry is causing this?
It seem unlikely though as it's been fine for several years up to now.
Possibly an entry exclusive o 1391? But again, this seems unlikely as no one else seems to be having this problem.
The Everything service is running as it should.
I'm completely baffled.
Re: Service not working
Can you please show the settings window of Everything Options - 1.5.0.1391a (x64) in a picture,
and only of “General” (after you have started 'Everything' and confirmed the UAC prompt).
The path to the test installation would also be interesting.
and only of “General” (after you have started 'Everything' and confirmed the UAC prompt).
The path to the test installation would also be interesting.
Re: Service not working
In the UAC prompt, click Show more details.
Please send a screenshot of the UAC prompt.
Please download Process Explorer from Microsoft:
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
Please keep the UAC prompt dialog open.
In Process Explorer, left click the ⌖ Find Window toolbar button and keep holding down left mouse button.
---The Process Explorer window will disappear until the left mouse button is released.
Release the left mouse button on the UAC prompt.
In Process Explorer, what process is selected? and what is the parent process?

-If the parent process is Everything, please send a mini crash dump when the UAC prompt is shown:
What is the sha256 sum of your Everything64.exe ? (for version 1391a)
Please send a screenshot of the UAC prompt.
Please download Process Explorer from Microsoft:
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
Please keep the UAC prompt dialog open.
In Process Explorer, left click the ⌖ Find Window toolbar button and keep holding down left mouse button.
---The Process Explorer window will disappear until the left mouse button is released.
Release the left mouse button on the UAC prompt.
In Process Explorer, what process is selected? and what is the parent process?

-If the parent process is Everything, please send a mini crash dump when the UAC prompt is shown:
- Please keep the UAC prompt dialog open.
- Download Process Explorer from Microsoft:
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer - In Process Explorer, select Everything64.exe (If there is two, select the one using the most memory)
- Right click Everything64.exe and under Create Dump, select Create Mini Dump.
- Choose a filename and click Save.
- Please upload this dmp file in a bug report
What is the sha256 sum of your Everything64.exe ? (for version 1391a)
Re: Service not working
No path to the test installation as such, I just put Everything portable 1391 in a new folder in a new folder and ran it clean.
Just to reiterate, the settings are absolutely correct, Everything service is running correctly on my system , and it's only 1391 that is the problem.
I have had the same setting for many versions of Everything, when updating, I just drop the new portable .exe file into my Everything folder, replacing the old version.
The troubleshooting in Everything also shows that the service is running correctly, and David confirmed this when I sent him a copy of trobleshooting file.
If I revert to an earlier version, again, I just drop it into my existing folder. I updated from 1384 to 1391, 1391 showed the UAC prompt, so I replaced 1391 to 1390 which I'm currently using and is not showing the UAC prompt.
I'm wondering, as I said, whether there could be some sort of rogue registry entry relating to 1391.
Just to reiterate, the settings are absolutely correct, Everything service is running correctly on my system , and it's only 1391 that is the problem.
I have had the same setting for many versions of Everything, when updating, I just drop the new portable .exe file into my Everything folder, replacing the old version.
The troubleshooting in Everything also shows that the service is running correctly, and David confirmed this when I sent him a copy of trobleshooting file.
If I revert to an earlier version, again, I just drop it into my existing folder. I updated from 1384 to 1391, 1391 showed the UAC prompt, so I replaced 1391 to 1390 which I'm currently using and is not showing the UAC prompt.
I'm wondering, as I said, whether there could be some sort of rogue registry entry relating to 1391.
Re: Service not working
Thanks David, I've already got process explorer installed on my system so I will do that.
Re: Service not working
Have you checked that the EveryThing64.exe properties have NOT been set to run as Administrator?
Re: Service not working
Absolutely nothing has been changed, and all previous versions are working. Run as admin has never been enabled.
Re: Service not working
How do you do that?
When I start Everything64.exe as administrator, I get the UAC prompt window.
Then I only see the UAC prompt window and my desktop in the background.
I cannot use ALT+TAB to switch to any task, e.g. Process Explorer.
Determine parent process of 'Everything' - I have now done it this way:
After confirming the UAC prompt(!), the window will close and it is possible to use Process Explorer:
- Left-click on the button “Find Window's Process (drag over window)” and hold the left mouse button pressed
- Drag over the 'Everything' installation window, then release the left mouse button
Re: Service not working
Basically you can't.
The UAC prompt runs under a different account (SYSTEM?)and will be shown on its own secure desktop.
If one really wants to (not recommended), one could reconfigure the UAC settings to a less strict one that will show the UAC prompt on the desktop of the current user.
At least, that is how it used to be.
EDIT:
Still possible:
- run C:\Windows\System32\wscui.cpl
- Select Security
- Select User Account Control
- Set to one level below the default
(Names might differ slightly; I'm currently on a Dutch Windows 11)
Don't forget to reset to default afterwards

Re: Service not working
2NotNull
Thanks!
It works as you described.
(Task bar >
Search: uac ... is also possible).
I suspect, however, that this only determines the parent process of the 'UAC prompt' in Process Explorer
(because I am pointing the Process Explorer cursor at the UAC prompt window:
"... Release the left mouse button on the UAC prompt. ...").
Thanks!
It works as you described.
(Task bar >
I suspect, however, that this only determines the parent process of the 'UAC prompt' in Process Explorer
(because I am pointing the Process Explorer cursor at the UAC prompt window:
"... Release the left mouse button on the UAC prompt. ...").
Re: Service not working
Not confirmed.
Everything 1.5.0.1391a (x64) & Windows 11 Pro (x64) Version 24H2 (OS Build 26100.2605)
I made an installation in C:\Everything_Test -> Install the “Everything” service.
After that, I made an installation in D:\david by running:
D:\david\Everything64.exe -instance david
The “david” instance was opened immediately and without any further prompts.
Re: Service not working
Could this be the same problem, just started happening for me today. Certificate related.
I'm using 1389
I try start it within system informer and I get this error message. Update: also get this error when trying to run the installer, preventing me from updating or installing a new or previous version.
Seems to have occurred after the latest windows update (jan 2025), kb5050021.
Update: I reproduced this issue, and confirmed by image recovery prior to windows update kb5050021; everything worked fine, after updating windows once again to kb5050021 it says the certificate was revoked by issuer for your installer and loading the service.
I'm using 1389
I try start it within system informer and I get this error message. Update: also get this error when trying to run the installer, preventing me from updating or installing a new or previous version.
Seems to have occurred after the latest windows update (jan 2025), kb5050021.
Update: I reproduced this issue, and confirmed by image recovery prior to windows update kb5050021; everything worked fine, after updating windows once again to kb5050021 it says the certificate was revoked by issuer for your installer and loading the service.
Last edited by k2013 on Wed Jan 15, 2025 11:08 pm, edited 7 times in total.
Re: Service not working
Thank you for your post k2013,
DigiCert has not revoked the voidtools code signing certificate.
Could you please send the sha256 hash for your Everything installer and Everything64.exe
Version 1391a should be:
Everything-1.5.0.1391a.x64-Setup.exe 08712d7f9e87cb8181664b58471ab4addde4396566acc15b57b6c7de24a0425a
Everything64.exe bdacc22ca03f5cee95fd8d3abf2bda3b5206b6b5ec086234a01cb562b21e58df
DigiCert has not revoked the voidtools code signing certificate.
Could you please send the sha256 hash for your Everything installer and Everything64.exe
Version 1391a should be:
Everything-1.5.0.1391a.x64-Setup.exe 08712d7f9e87cb8181664b58471ab4addde4396566acc15b57b6c7de24a0425a
Everything64.exe bdacc22ca03f5cee95fd8d3abf2bda3b5206b6b5ec086234a01cb562b21e58df
Re: Service not working
Currently I am using 1389
1389, Everything64.exe 49963337475730A9AFE8FEFED40BEB8FEC036DDDE84C1DD7E233DF92091DC75B (worked without a hitch before windows update)
Everything-1.5.0.1391a.x64-Setup.exe 08712D7F9E87CB8181664B58471AB4ADDDE4396566ACC15B57B6C7DE24A0425A
Every version freshly downloaded from your site has this issue; windows update did something to the certificates. I deleted and re-imported 'DigiCert Trusted Root G4' from their website into 'Trusted Root Certification Authorities', this didn't seem to help anything.
Any ideas?
I am seeing no problems when I right click your executable and view certificate
1389, Everything64.exe 49963337475730A9AFE8FEFED40BEB8FEC036DDDE84C1DD7E233DF92091DC75B (worked without a hitch before windows update)
Everything-1.5.0.1391a.x64-Setup.exe 08712D7F9E87CB8181664B58471AB4ADDDE4396566ACC15B57B6C7DE24A0425A
Every version freshly downloaded from your site has this issue; windows update did something to the certificates. I deleted and re-imported 'DigiCert Trusted Root G4' from their website into 'Trusted Root Certification Authorities', this didn't seem to help anything.
Any ideas?
I am seeing no problems when I right click your executable and view certificate
Last edited by k2013 on Thu Jan 16, 2025 2:16 am, edited 1 time in total.
Re: Service not working
I downloaded and re-imported DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, which actually did have a different hash than the original on my PC (how is that possible?); but im still getting the same error.
update:
I ran both versions of the cert through virustotal, the old one was found previously with many different names, starting in 2022, the new one downloaded from digicert's website today appears to be brand new, and hasn't been detected before.
Update: I opened a ticket here https://answers.microsoft.com/en-us/win ... 0bc7dfc21b
update:
I ran both versions of the cert through virustotal, the old one was found previously with many different names, starting in 2022, the new one downloaded from digicert's website today appears to be brand new, and hasn't been detected before.
Update: I opened a ticket here https://answers.microsoft.com/en-us/win ... 0bc7dfc21b
Last edited by k2013 on Thu Jan 16, 2025 5:46 am, edited 5 times in total.
Re: Service not working
It seems that microsoft has added your cert to the "vulnerable driver blocklist" found here: https://learn.microsoft.com/en-us/windo ... lock-rules
Code: Select all
<Signer ID="ID_SIGNER_VOIDTOOLS" Name="voidtools (Thumbprint: 4DA2AD938358643571084F75F21AFDDD15D4BAE9)">
<CertRoot Type="TBS" Value="2AAA2A578BDEB2F1DBAAE27B6358B87D14143B7FA98518A6AC576172677225AC"/>
Tried redownloading the installer and running it and i get the certificate error aswell.
I am on windows 11 Version 23H2 (0S Build 22631.4751)
I have the "vulnerable driver blocklist" option enabled in microsoft defender
Re: Service not working
Isn't harry's issue going to be different, as he is on Win7, & so (generally, unless paid or hacked) there are no Windows "updates" to contend with (to break things
).
That is expected.
But what is happening with 1391 is that you are now also getting a UAC prompt when attempting to open the Everything GUI, Everything.exe.
And you do have the Service running.
And you are not attempting to run the Everything GUI "as Administrator", just as a "normal" user.
@David, has the "Service" remained consistent (over versions) or are there actual potential differences in the service itself?
Very possible that harry is running a very old Service version that for whatever reason, is no longer liking 1391?
(On my end, I always -uninstall-service / -install-service - as a matter of course [on updating].)
(Note my post on "aberrations" as to the "service level", if you will, being "reported", if it is in fact "reporting".)
@harry, verify that you in fact are not installing any (current) Windows updates.
Maybe even confirm that you have updated all past, available updates, including the
"2019-03 Servicing Stack Update for Windows 7 for x64-based Systems (KB4490628)".

To be clear, when you install or uninstall the Service itself, you do get a UAC prompt.harry wrote:but I'm getting a UAC box pop up
That is expected.
But what is happening with 1391 is that you are now also getting a UAC prompt when attempting to open the Everything GUI, Everything.exe.
And you do have the Service running.
And you are not attempting to run the Everything GUI "as Administrator", just as a "normal" user.
It is going to be one of those other instances that is the "parent" (if you will) of the Service (that the Service was initiated from).T do have a couple of other instances running under the same service as well, but I haven't started these for quite a while, and again, it's only 1391 that is the problem.
@David, has the "Service" remained consistent (over versions) or are there actual potential differences in the service itself?
Very possible that harry is running a very old Service version that for whatever reason, is no longer liking 1391?
(On my end, I always -uninstall-service / -install-service - as a matter of course [on updating].)
(Note my post on "aberrations" as to the "service level", if you will, being "reported", if it is in fact "reporting".)
@harry, verify that you in fact are not installing any (current) Windows updates.
Maybe even confirm that you have updated all past, available updates, including the
"2019-03 Servicing Stack Update for Windows 7 for x64-based Systems (KB4490628)".
Re: Service not working
I am having the certificate issue as user k2013. don't know what the issue of the original poster of this thread is sorry. came here from search results. maybe we should split into a new thread?
Re: Service not working
(Yes, probably should be split, but I'll let others decide on that.
That said, your issue will still be seen.)
That said, your issue will still be seen.)
Re: Service not working
Just to note, Default, & one level below default, are exactly the same (as far as "Protection" is concerned).Still possible:
- run C:\Windows\System32\wscui.cpl
- Select Security
- Select User Account Control
- Set to one level below the default
Don't forget to reset to default afterwards
Only difference is in dimming, or not (& also one level below does not "block", allowing you to do "stuff" without first dismissing the UAC prompt).
(On some systems, "dimming" can be "obtrusive" where "one level below" is not.)
@tuska, is not the parent process of (your) Everything, TOTALCMD64.exe.
Re: Service not working
On my end, Win7 x64, Everything x86, Service is installed, runs all the time, GUI only runs on demand, started manually.In the UAC prompt, click Show more details.
I am (my User Account) is Administrator, though running as a Standard user.
I do not install, only use the ZIP's.
I do not get any UAC prompts - except from Service changes, never the GUI, even 1391 (& the GUI is not running "as Admin").
This was from an attempted uninstall of the Service, not an opening of the GUI:
. Note that the (UAC) "Program location:" only relates to the path/.exe that caused the UAC request, & is not really related to anything else.
Yes, that will be the case.Is the service running on another Everything.exe ? (different to the one used for your david instance)
Otherwise, he would not be able to "when updating, I just drop the new portable .exe file into my Everything folder, replacing the old version" - without first uninstalling the service (or at least temporarily Stopping it). (Or at least in the not in the \david\ directory.)
(I'll note that you cannot run x86 & x64 instances simultaneously - at least not with the same Service.)
Re: Service not working
@harry, in Process Explorer, double-click on the Everything.exe service, Image (tab), what does Version: show?
Version:, should reflect the version of the Service that you are running (I'm guessing ? - or at least the version of the Everything.exe that was used to install the Service).
I suspect you have a rather old Version: displaying.
You can try, but I threw in 1200, & still 1391 GUI did not complain (with UAC prompt).
Version:, should reflect the version of the Service that you are running (I'm guessing ? - or at least the version of the Everything.exe that was used to install the Service).
I suspect you have a rather old Version: displaying.
Or not.And if that is so, I'd suspect if you uninstalled the Service, then installed it anew - but by using the 1391 Everything.exe, your issue may subside?
You can try, but I threw in 1200, & still 1391 GUI did not complain (with UAC prompt).
Re: Service not working
There is no difference between the "portable" Everything.exe & an installer Everything.exe.
With his new directory, & throwing Everything.exe into it, AND with the Service already in a running state, & with no .ini, Everything will by default use the Service (& also store his settings in that newly created directory, "portable", if you will).
He is simply piggy-backing on the already running Service.
Aside from context-menu, es: URL protocol, file associations, or similar, Everything "portable" does not using the Window registry (& pretty sure ? neither does the .exe installer).harry wrote:Apart from the context menu entries and services does Everything portable make any registry entries. I'm wondering if anything in the registry is causing this?
In his test case, he is simply throwing Everything.exe into a directory - somewhere.tuska wrote:The path to the test installation would also be interesting.
He is not installing or uninstalling (the Service) or even supplying an switches to the .exe.
The directory should be irrelevant.
(Now, possibly, if you were running from within a "protected" area, like /Program files/, which is "protected", things could be different, but he's not doing that.)
Correct. (And that, as you've shown, is consent.exe.)
OK, I'm now out of ideas aside from something silly like antivirus (or a hacked Everything.exe).
Re: Service not working
> Only difference is in dimming, or not ...therube wrote: ↑Thu Jan 16, 2025 6:40 pmJust to note, Default, & one level below default, are exactly the same (as far as "Protection" is concerned).Still possible:
- run C:\Windows\System32\wscui.cpl
- Select Security
- Select User Account Control
- Set to one level below the default
Don't forget to reset to default afterwards
Only difference is in dimming, or not (& also one level below does not "block", allowing you to do "stuff"
without first dismissing the UAC prompt). (On some systems, "dimming" can be "obtrusive" where "one level below" is not.)
@tuska, is not the parent process of (your) Everything, TOTALCMD64.exe.
... and that the highest level is “Recommended” by Microsoft and the second highest level is “Not Recommended” (Windows 11 Pro).
> @tuska, is not the parent process of (your) Everything, TOTALCMD64.exe.
Yes, I see it that way too.
Thank you for your further explanations regarding my posts.
In my opinion, harryray2 still has to provide some answers to the questions asked
in order to enable further support on this topic.
Re: Service not working
Thank you for finding that gem and sharing it here. So it wasn't revoked by the issuer, it was revoked by Microsoft... in their driver blocklist, which is incorrect because voidtools is not a driver, it is a piece of software that basically leaves windows search lightyears behind. Their blanket ban of your products might be an illegal act of monopolistic behavior.adg23ds wrote: ↑Thu Jan 16, 2025 12:59 pmIt seems that microsoft has added your cert to the "vulnerable driver blocklist" found here: https://learn.microsoft.com/en-us/windo ... lock-rulesThe everything app v1.4.1.1026 x64 fails to launch with the same error for me "A certificate was explicitly revoked by its issuer."Code: Select all
<Signer ID="ID_SIGNER_VOIDTOOLS" Name="voidtools (Thumbprint: 4DA2AD938358643571084F75F21AFDDD15D4BAE9)"> <CertRoot Type="TBS" Value="2AAA2A578BDEB2F1DBAAE27B6358B87D14143B7FA98518A6AC576172677225AC"/>
Tried redownloading the installer and running it and i get the certificate error aswell.
I am on windows 11 Version 23H2 (0S Build 22631.4751)
I have the "vulnerable driver blocklist" option enabled in microsoft defender
Contact the Federal Trade Commission (FTC): Visit the FTC's website and use their online complaint form or call their Consumer Response Center.
Reach out to the Department of Justice (DOJ): The Antitrust Division of the DOJ handles antitrust complaints. You can submit information about potential antitrust violations through their website.
HP, Creative and Levono are in that block list, but with specific files or drivers signed by 'DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1', but not a sweeping ban like was done to voidtools.
I am unable to disable driver blocklist, it is greyed out and not enforced by group policy either; I checked and it was already set to disabled in the registry.
So I updated the policy and removed Voidtools from the list. I downloaded a copy of SiPolicy_Enforced.xml, [1], removed voidtools from the list, converted it to a p7b, [2] imported it and ran RefreshPolicy(AMD64).exe, claims "Rebootless ConfigCI Policy Refreshing Succeeded!" but its still blocking the executable. SiPolicy.p7b doesn't overwrite driversipolicy.p7b, it takes precedent over it... , so perhaps it need to be whitelisted. I don't see any tutorials for doing that.
The blocklist is regularly updated, usually 1-2 times per year with each new major release of Windows. Mind you, I was already using the latest driver blocklist before the latest windows update broke your software. I update it automatically via scheduled task.
@adg23ds. Can you test disabling driver blocklist to see if this problem is rectified?
[1] https://aka.ms/VulnerableDriverBlockList
[2] https://learn.microsoft.com/en-us/windo ... eployment-
Barring everything else, releasing an unsigned version for users experiencing this problem could be a temporary work around.
Update: I found a way to do it myself, and it worked.
signtool remove /s Everything64.exe
Thats it.
Last edited by k2013 on Sat Jan 18, 2025 11:24 am, edited 16 times in total.
Re: Service not working
(So on one hand, MS says that Code Signing is important. And with that MS can come along & block a code signed application - because it is code signed, & blocked in their VulnerableDriverBlockList. And then MS also supplies a tool SignTool that can be used to remove that very "important" signing, such that the application while still blocked, the application can then be used again.
I find that rather amusing, heh.
Mozilla signs its extensions. But if the extension is altered, the "signing key" no longer computes, so the extension cannot be installed. [Now granted, "signing" did not improve Mozilla "security", & even with signing, it is far from an end-all.])
I find that rather amusing, heh.
Mozilla signs its extensions. But if the extension is altered, the "signing key" no longer computes, so the extension cannot be installed. [Now granted, "signing" did not improve Mozilla "security", & even with signing, it is far from an end-all.])
-
- Posts: 1
- Joined: Sun Feb 02, 2025 1:53 pm
Re: Service not working
Howdy to all that came before me 
Is this the permanent fix for the issue?
"Update: I found a way to do it myself, and it worked.
signtool remove /s Everything64.exe"
Regards George

Is this the permanent fix for the issue?
"Update: I found a way to do it myself, and it worked.
signtool remove /s Everything64.exe"
Regards George