Multi Commander > Beta Releases

Multi Commander v3.5 Alpha/Beta

<< < (5/6) > >>

Jungle:

--- Quote from: Mathias (Author) on August 21, 2013, 07:53:24 ---MC must have been installed before.. you only get that loop if it find it self under install programs.
--- End quote ---
I've cleaned registry and disk, so there're no MC entries neither for Administrator nor for User (note that User has admin rights).
The problem remains. Setup works properly only when launched as Administrator.
But maybe it is because of some local and domain rules?

Mathias (Author):
Well the registry entries MUST be there for it to loop.
It is what the installer check for.

( on 64bit you also must make sure to clear out the under the "Wow6432Node" key )
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

If you tweak local or domain policys and rules all kind of strange things happen. You can block and change behavior of everything in windows with that.
I have very limited knowledge about all the policy/domain settings.

Jungle:

--- Quote from: Mathias (Author) on August 21, 2013, 08:40:39 ---Well the registry entries MUST be there for it to loop.
It is what the installer check for.
--- End quote ---
I've played with installation/uninstallation and found out that:
1. If MC was installed for current user only, launching setup again doesn't ask for uninstall
2. If MC was installed for all users, launching setup again asks for uninstall

But the main issue remains - install/uninstall only work when launched as Administrator. Well, let's blame unidentified security settings :)

P.S. It seems that uninstall doesn't remove start menu/desktop shortcuts.

Mathias (Author):
Did some testing on a clean win7 system
On a normal Win7 (No network domain and no domain policies)
everything looks to work as it should. (also menu/desktop)
And the uninstaller will only elevate to admin if installed as admin else it will run as user.

Will test some corner cases later where it is installed/uninstalled with different modes and platform version on top if each other. I suspect that can mess with the registry and confuse the uninstaller.
If the ForAll/ForUser install modes get mixed up I guess it can miss to delete desktop shortcut since they are in different locations.

Mathias (Author):

Build 1490 might be the last release candidate before final release. Unless some major issue if found.

Navigation

[0] Message Index

[#] Next page

[*] Previous page