Update 1422b does not get installed over the older version 1409a

[Raindrops]

I have 1409a.

I downloaded the latest version, 1422b, and installed it on top of it (without uninstalling 1409a).
But even now, the old version (1409a) launches when I press the keyboard shortcut.
Further, the 1409a's help>Check for updates... menu shows "Everything is up to date".

I have not uninstalled 1409a because I have many 4TB USB disks, which are offline.
I fear that if I uninstall 1409a, it will also lose the indexed data for those disks.

What should I do to update Everything?

[Herkules97]

Just make a backup of all the files before uninstalling?

You could also start using them in "portable" mode. Then you can let the 1409a folder be and move to 1422b and if anything goes wrong you have 1409a intact. Like a copy but more involved maybe.

Or just don't update, unless 1410-1422 contains something you want.

[therube]

This should explain what's going on, Everything 1.5a Alpha - Upgrade Guide.

[Raindrops]

I followed all steps.
Still it cannot install 1422b.

How do I take a backup of all index files?

[therube]

Further, the 1409a's help>Check for updates... menu shows "Everything is up to date".

I'll assume cause it is expected that the Alpha does not automatically update to the Beta (& so in that respect, 1409 Alpha is "up to date").

I have not uninstalled 1409a because I have many 4TB USB disks, which are offline.
I fear that if I uninstall 1409a, it will also lose the indexed data for those disks.

Back up.
Help | Troubleshooting should show where your .db (& other data files are).
Back them up.
(Plus, you need not necessarily uninstall 1409a.)

But even now, the old version (1409a) launches when I press the keyboard shortcut.

This keyboard shortcut is set where/how? An Everything setting itself or something external?
Have to suspect it is (obviously) simply pointing to 1409a rather then 1422b.
So disable it from pointing to 1409a & set it to point to 1422b.

If you ran the 1422b .exe itself, 1422b would then be running, no?

[void]

Everything 1.5 alpha runs alongside Everything 1.5 beta.

You can run both at the same time.

How do I take a backup of all index files?

What is your Tools -> Options -> General -> Store settings and data in %APPDATA%\Everything?

If checked, backup the following folders:

%APPDATA%\Everything

%LOCALAPPDATA%\Everything

If unchecked, backup the same location as your Everything.exe



Once you have a backup, install 1.5b and on the last install options page, before you hit install, check Copy Everything 1.5a settings and data.
Once you see all your settings and data in 1.5b, uninstall 1.5a.

[Raindrops]

Thanks for your guidance!

By mistake, I overlooked the fact that the beta created a new subfolder called Everything, whereas the older alpha was running from Everything 1.5a.

All the time I thought that the beta hd already overwritten the alpha.

[Herkules97]

OK, so how do I copy the keyboard shortcuts from 1409a to 1423b?

I just did a test as I don't use custom shortcuts and it's inside the .ini
On my 1411b instance, the keybinds start at file_new_window_keys.
Idk why you didn't just copy the ini as-is alongside all other files, but you can just copy either the entire section of shortcuts and paste-to-replace in the newer build's .ini or only copy the shortcuts that are different by using a file comparison tool. Notepad++'s Compare/ComparePlus would probably work. I used AJC Diff as I save all .ini versions with AJC Active Backup.

If they aren't in the ini you think had them, then Idk..Use EBV itself to find .inis that could have them. Maybe use agent ransack on them to find all lines for one of the shortcuts you've modified. Presumably only the ini that has the custom shortcut would have anything after =.

[Raindrops]

@Herkules97

Many thanks for that extra effort!

After posting, I bit the bullet and deleted the 1409a alpha.
The 1423b beta worked just fine.
Note: I had to manually launch it once.

Based on this successful trial, I removed the original message, and posted that Everything works fine now.

Sorry for the inconvenience!