FreeCommander Forum

Thank you very much for the explanation.

However, I don't know whether this is the right direction. For example, there are 3 PCs and two laptops in our private household, and there are 4 family members, each of them with an own non-administrative account on each of the devices. Each device also has ...

Hello @Marek,

thank you very for your help and for the tip.

However, in my case, saving the settings does not effect anything. What else could I do? Would you mind explaining which entry in the INI files takes care of that alert?

I have verified that there are no permission problems. I went into ...

@Karol

Thank you very much!

I should have remembered this. You are totally correct. This probably causes the issue, and it explains the different behavior of Windows Explorer and Windows command prompt on one side and FreeCommander on the other side. I guess that @horst.epp uses the 64-bit version ...

Thank you very much for all your efforts! After all, it's Sunday ...

Well, then I believe I have to live with it. Probably the only way to solve the problem would be reinstalling Windows. That's not an option on the affected PC at the moment.

The last thing that comes to my mind is Windows 10 (at ...

@horst.epp

Would you mind conducting a further test? For this test, you would need to have a Windows recovery partition on your disk. The test works as follows:

- Open a command prompt with administrative permissions and issue the following command: "reagentc /disable".
- This makes the file ...

Thank you very much for trying to reproduce. However, it's still different for me.

Additionally, I have reproduced the problem using FreeCommander Portable (as recommended in the first sticky post in this sub-forum). The portable version also lists the non-existent "Winre.wim" file and does not ...

Dear all,

the following bug occurs with FreeCommander XE 2020 public 32-bit as well as FreeCommander XE 2024 public 32-bit. I did not test versions before 2020 or versions between 2020 and 2024, but assume that all versions beginning with 2020 (and probably earlier) are affected.

So I am running ...

Is FC a backer-upper :?:

I would not say so. It is a file manager and explorer replacement with great additional usability and features.


Does FC synch target with source :?:

Why not read about it in the manual ( http://www.freecommander.com/fchelpxe/en/FreeCommander.html?Synchronize.html ...

I am really not deep enough in that matter to answer your question, but some thoughts came to my mind:

1) I suppose FC relies on the "Send To" mechanism of the OS. I can't test at the moment, but I am not sure if the way you would like to behave it is the way it is supposed to work.

What happens ...

Dear Marek,

thanks for your fast reply, and please forgive me that I couldn't do the test yesterday.

The new version of FcContextMenu64 indeed did solve the problem.

I have copied the new version into the program folder, again did copy / rename it as per your instructions, and changed the .ini ...

Dear Marek,

thank you very much for your help and your hints.

The new version (FreeCommander XE 2018 Build 770 32 bit) did not solve the problem. It changed the behavior, but introduced a new bug. After having installed the new version, and after having followed the additional steps you mentioned ...

Hi Marek,

thank you very much! That was really fast.

We are excited that you did take care of our problem although our working method which is probably the root of the evil is quite exotic.

As an information for you (which might be interesting because probably only a few people have tried it ...

At first, thank you very much for providing that invaluable software! We are using it since some days now and are still excited about it. However, we have encountered a weird problem.

The version we use is: FreeCommander XE 2017 Build 740 32-bit public
Our O/S is: Windows 7 Pro x64 English, all ...