After updating with the same newest installer v36.52.88 to activate EVERYTHING, EVERYTHING was downgraded

[Alpengreis]

Before I had no more selected EVERYTHING while installing TCMD updates (had not activated EVERYTHING).

Today I decided to activate and install EVERYTHING again. So I reinstalled TCMD with the same newest v36.52.88 and selected EVERYTHING this time.
After the EVERYTHING installer was finished, EVERYTHING versions were downgraded to older versions (including ES).

Means: the in TCMD integrated EVERYTHING installer package includes older versions.

Just for info ...

 

[Eric Pement]

Before I had no more selected EVERYTHING while installing TCMD updates (had not activated EVERYTHING).

Today I decided to activate and install EVERYTHING again. So I reinstalled TCMD with the same newest v36.52.88 and selected EVERYTHING this time.
After the EVERYTHING installer was finished, EVERYTHING versions were downgraded to older versions (including ES).

Means: the in TCMD integrated EVERYTHING installer package includes older versions.

Just for info ...

There is a version difference between ES.EXE (the command-line interface to everything) and EVERYTHING (the GUI interface). Here is what I get with TCC v36.52.81,

[c:\program files\jpsoft\tcmd36]
[12:39] > es.exe -version
1.1.0.37

[c:\program files\jpsoft\tcmd36]
[12:40] > *everything /v
1.5.1396

Note that the command-line interface "es.exe" is a tool built by Rex, not by voidtools. It's not supposed to match the version number of everything.exe.

When I visit https://voidtools.com/downloads/ , the most recent full version of everything is v1.4.1.1032, while the latest beta version is 1.5.0.1423b Beta.

So it looks to me like Everything bundled with TCC has a higher version number than the version number available directly from voidtools.com. So maybe you're not downgraded after all.

 

[Alpengreis]

The thing is: if you don't select EVERYTHING while you install TCMD update, you will have newer versions than if you select it (nevertheless not the newest but newer). So the integrated EVERYTHING INSTALLER includes much older versions of EVERYTHING and ES.

 

[Joe Caverly]

Off topic, but you can also get the everything version by doing;

R:\>es.exe -get-everything-version
1.5.0.1418

C:\...\TCMD36>*everything /v
1.5.1418

C:\...\TCMD36>verdir Everything64.exe
1.5.0.1418  Everything64.exe

•  1 file found in 0.003 seconds.

VERDIR is from the FileUtils Plugin

Ref: FileUtils Plugin

Joe

 

[vefatica]

Hmmm! I have this one installed with TCC 36.52.88. Where did 1418 come from?

v:\> es /v
1.5.0.1396

 

[Joe Caverly]

C:\...\TCMD36>es.exe -get-everything-version
1.5.0.1418

C:\...\TCMD36>ver

TCC  36.52.86 x64   Windows 10 [Version 10.0.19045.7663]

Joe

 

[Joe Caverly]

I just updated TCC to 36.52.88,
and the following is reported,

C:\...\TCMD36>everything /v
1.5.1418

C:\...\TCMD36>es.exe -version
1.1.0.27

C:\...\TCMD36>es.exe -get-everything-version
1.5.0.1418

C:\...\TCMD36>verdir Everything64.exe
1.5.0.1418  Everything64.exe

•  1 file found in 0.004 seconds.

C:\...\TCMD36>ver

TCC  36.52.88 x64   Windows 10 [Version 10.0.19045.7663]

C:\...\TCMD36>

Joe

 

[vefatica]

Thanks. I see what's happening and it was my fault. I use these aliases when I want to use Everything. I will update them to make them use the same everything.exe that the service uses.

es1=sc start Everything & rundown "d:\tc35\everything64.exe -startup"
es0=d:\tc35\everything64.exe -quit & sc stop Everything