Installing Everything silently doesn't remove the old version

[KernalCheddar]

I push the new client silently but it doesn't remove the old version, it just adds the new one, so now I have users with multiple versions of the software on their machine. why would this be happening? Below is the line I'm using to install it:

Everything-1.4.1.1005.x64-setup.exe /S -install-options "-install-config Everything.ini -install-client-service -install-desktop-shortcut -disable-run-as-admin -install-efu-association -install-folder-context-menu -install-run-on-system-startup -install-service -install-start-menu-shortcuts -install-url-protocol"

[therube]

You didn't specify a directory to install to.
So maybe the (default) install to location has changed?
(Suppose ? something like that could happen if you switched from x86 to x64 version?)

Into what directories are the old & new versions installed into?

[void]

I push the new client silently but it doesn't remove the old version

What is left over from the old version?
Is there an old Start menu shortcut?
Is there an old Desktop shortcut?

Uninstalling Everything

[KernalCheddar]

Sorry for the delay on this, after a second look it looks like the software does actually update correctly, it just leaves a listing for the old version if programs and features. weird. any thoughts on how to remove it? trying to "uninstall" the old version breaks the new one.

[therube]

I've not used it, but you can see what (Nirsoft's) ShortcutsMan might do?

ShortcutsMan displays the details about all shortcuts that you have on your desktop and under your start menu. Broken shortcuts (shortcuts that point to file that doesn't exist) are automatically painted with pink color. You select one or more shortcuts, and then delete them, resolve them or save the shortcut's details to HTML/Text/XML file.

[void]

Everything uses the following registry keys to be listed in Programs and Features:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Everything

The Wow6432Node one is used when you install the x86 version of Everything on a x64 OS.

Please check if you have installed the x86 or x64 version. (Help -> About)

If you have installed the x64 version, please delete the:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Everything
key to remove the duplicated Everything from Programs and Features.

[b767mike*]

Have there been any updates to this problem of not removing from Programs the old version entry?
Using the /S silent install and and both versions show up in my Programs & Features.

[void]

Thanks for the issue report b767mike*,

I haven't been able to reproduce the issue my end.

Everything-1.4.1.1026.x64-Setup.exe /S

and

Everything-1.4.1.1028.x64-Setup.exe /S

update the single uninstall entry for me.



Everything writes the uninstall entry to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything

Could you please check if there's another entry under:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything

Everything will never write here, but it would explain the duplicated uninstall entry.
-If this key doesn't exist, please try a search in the registry editor for

Everything 1.4.1.1028 (x64)

Where doesn't this value show up?

[therube]

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything

Everything will never write here, but it would explain the duplicated uninstall entry.

And what, something like that would only occur if Everything was installed under a User context?
(So something like, without a UAC elevation prompt?)


Nirsoft's RegScanner might aid in a (registry) search.
(Note the History for 2.75, Added Automatically skip a corrupted recursive key' option. If RegScanner crashes while scanning the Registry on your system, try to turn on this option. That did come into play on one of my systems.)

[b767mike*]

Tried 3 routines.

1. Clean computer, install 1026, UAC prompt, installed, Help/ About shows 1026, update 1028, UAC prompt, installed, Programs and Features shows ver 1028 entry, Help / About shows 1028. Everything works.

2. Clean computer, install as above but from command line using /S, same results

I use a Network Management Tool called Action1. I know you are not concerned with what or how Action1 interacts with Everything, but added this as just extra info.

3. Install Everything ver 1026 with /S. No UAC prompt All good. Help / About shows 1026. Action1 alerts me ver 1028 is available. Update. Ver 1028 installed, Help / About shows ver 1028. Programs and Feature shows both Vers. And Action1 shows there is an update available even though 1028 is installed.

So I am assuming that Programs and Features and Action1 get ver info from same place in registry.

Pictures
#1 & #2 show registry entry when Programs And Features show 2 vers installed
#3 entries left after Uninstall of both programs. Revo Uninstaller removed this.
#4 Action1 showing update even though ver 1028 installed.

[void]

And what, something like that would only occur if Everything was installed under a User context?
(So something like, without a UAC elevation prompt?)

It will never happen.
I was just noting the Windows will pull the uninstall information from those two locations.

3. Install Everything ver 1026 with /S. No UAC prompt All good. Help / About shows 1026. Action1 alerts me ver 1028 is available. Update.

How are you updating? through Action1?
It looks like the msi installer was used which writes uninstall information differently.

Uninstall both versions and try the official Everything installer:
Everything-1.4.1.1028.x64-Setup.exe.

[therube]

So in a case like that, the .msi installer is unaware that there was a prior install via a .exe installer.
Likewise, a .exe installer would be unware of an installation made by a .msi installer.

(Now, assuming the actual installations were made to the same directory, say a place like, /program files/everything/, an uninstall, or update, of one or the other would, theoretically, work correctly, because it is dealing with a singular install location, & theoretically the same sets of program files.)

[b767mike*]

Been busy and haven't had time to uninstall and reinstall via .exe. Will get to that tomorrow and reply back. Just didn't want to think I was ignoring you.

[b767mike*]

Was curious and you were correct. 1026 was the MSI file and 1028 was the exe. Changed 1026 to exe and will give it a try.