Page 1 of 1

Total7zip Plugin inconvenient usage in installed version of FC after importing settings from portable FC

Posted: 27.01.2025, 20:53
by Forez
I have installed the Total7zip Plugin 1.5 for my portable x64 version - and it works A-OK. It is located at

C:\q\FreeCommander\Plugins\wcx\Total7zip

And if I will install the same plugin for the installed x86 version of FreeCommander it will also work when using this version of FC. But if I will then import settings from my portable FC to the installed one and then in while using installed FC I will attempt to navigate to inside of an archive file I will get the pop-up saying
Can not load plugin "C:\Program Files (x86)\FreeCommander XE\Plugins\wcx\Total7zip\Total7zip.wcx64"
So how am I suppose to have quickly in my [auxiliary] installed version of FreeCommander the same settings as in my [daily used] portable FC, if after importing settings to the [less important to me] installed versions from [my go-to] portable FC the path to the plugin becomes broken?


I am using Build 911 64-bit Donor Portable & Build 901 32-bit Public Installed on Windows 10 Enterprise 20H2 x64 [10.0.19042]; but this has been happening also with earlier builds

Re: Total7zip Plugin inconvenient usage in installed version of FC after importing settings from portable FC

Posted: 10.03.2026, 18:23
by Forez
This issue could be solved by addition of a doppelganger field for the

FreeCommander > Tools > Settings > Archiver plugins > WCX > Total7zip > Plugin File

i.e. by making it possible for user to pick a separate path for the 64-bit and the 32-bit version

Re: Total7zip Plugin inconvenient usage in installed version of FC after importing settings from portable FC

Posted: 15.03.2026, 10:07
by Forez
Or maybe alternatively this could be dealt with by addition of a new field / column, in which user would choose by which version is the path (from currently available field) is to be used?

This way users would have to same plugin entry two times - but with a different >>Plugin File<< value