Separate names with a comma.
Discussion in 'Support' started by djspits, Sep 23, 2016.
Here it's no problem - tested via elevated and not elevated TCMD and TCC.
v20.00.20 on Win 10 Pro x64 1607 ...
Runs your everything as service too?
There's one set of circumstances under which I'm sure that will happen: the service is not running and the (one) instance of EVERYTHING.EXE is running elevated. The service running, or not, may be irrelevant. This is because the inter-process communication needed to open the options dialog is, by default, disallowed between the different integrity levels. I discussed this with the author in an Everything forum. While the elevated instance could allow the communication, he did not seem inclined to make it do so.
Aha, good to know, thanks!
Your right, running it elevated opens the dialog as expected.