ES: URL Protocol & current 1.5's

[therube]

ES: URL Protocol & current 1.5's


Nirsoft, URLProtocolView:

Code: Select all

.../Everything.exe" -url "%1" -instance "15"

Always had it enabled.
Always worked.
(At some, relatively recent point... I'm guessing with the change dealing with "-instance" vs. 1.5a, maybe not ?... NOT.)

My [SeaMonkey/Firefox] bookmarklet now is asking to elevate (UAC) when I run it...
And I'm guessing that has to do with the '-instance "15"'?
I'm on 1317a, currently.


(I haven't actually allowed the UAC prompt, but I gather it will open a new instance of Everything?)



Everything GUI, says, "-instance 15".
Everything Service, says, "(1.5a)".


So if I disable/re-enable ES: protocol... that might fix it no?

Nope.
Not that easy.


Ah, so it's some sort of change between 1316a & 1317a.

1316a (& all before), just works.
1317a, asks for elevation (UAC).


1319, just works ?
And now 1317 just works too ?

Might have had to do with bitness?
I've always used x86, but changed to x64 with 1316aN1, but then went back to x86 with 1317a?


Oh, & I use my typical (though not necessarily needed) procedure:

Code: Select all

everything -uninstall-service -instance 15
copy <new|old> version overtop existing
(in the case of x64, rename Everything64.exe to Everything.exe)
everything -install-service -instance 15

[therube]

My other computer, also (went from 1316->1317, &) still on 1317, did not have that issue.

So whatever happened, maybe just a fluke?


(No changes, on either end [I guess you could say, period], that would account for this.
Neither computer has been restarted in some time. This one, 17 days. The other, probably longer.)

[void]

There is an Everything Service compatibility issue with 1319a.

Running Everything 1319a with an older version of the Everything Service will cause the Service to no longer respond.

Did you see the following dialog:


This dialog is shown if the service is not running or responding.
It's possible to launch Everything as admin from this dialog.

[therube]

No.

Before, I had only been up to 1317.

When I put 1319 in, I only did that to see if there was any change.
And when 1319 worked, I then reverted back to 1317 to see if it still failed (which it then did not).

So when I was seeing this, I'd not yet done anything with any version > 1317.


(On now on 1319.)

[void]

run_as_admin sometimes changes to 1 in portable version might be related.

I am still looking into the issue..

[void]

Everything 1.5.0.1321a fixes an issue with run_as_admin being enabled when changing a view setting.