FreeCommander Forum

I migrated my FreeCommander to a new computer and updated it to Build 889 64-bit while doing so.

(It seems that) since then, it takes more than 30 seconds to open the settings menu.

During this time, FC is frozen. Windows says it is "Not Responding". However, it still consumes below 1% CPU. FC is also starting at normal speed and everything else seems to be working well as usual.

Any ideas would be welcome.
-fk

Try to start FC with a fresh new settings-file:

Use start parameter
freecommander.exe /NewIni=.\settings\fctest.ini

Maybe there are false paths in the ini for your new computer.
Did you change from 32 to 64bit system?

Should I be worried if I have to wait for ~3 seconds before window of Settings shows up? No matter if it is my main 64-bit portable, old FC 32-bit installed, or some brand new temporary version with default INI files?

It has been so slow for me also on my previous Windows 10 machine; and I do use programs in which getting to actually see their options is either quick or even immediate. In a matter of fac it is only FC what is annoyingly slow is this regard

I recently updated to the latest Build 892 64-bit donor and did some more testing. Still no significant improvement.

It may also be useful to know that I use the portable version of FC. But directly in a directory of the C: drive of my built-in SSD on a fairly new Dell Precision running an up-to-date Windows 11 Enterprise.

Opening the settings of my old installation takes approximately 20 seconds, now. Same symptoms as initially stated.

I freshly unzipped the Build 892 portable zip file into a new directory and started FreeCommander.exe from there.
Opening settings from this brand new instance took approx 15+ seconds.

Suspicious if the portable version is referring to any file outside of its portable directory, I searched for freecommander files on my remaining drive, found the following (mostly in the temp dir) and renamed them:

• FreeCommander34860 - dir, empty
• https+++freecommander.com - dir, few files
• FreeCommander36568 - dir, empty
• Fc_NewIni_Test_Settings - dir, multiple files

No improvement. Any other ideas welcome!

Here in the actual FC version it takes about 3 seconds, which I find ok.

Suspicious if the portable version is referring to any file outside of its portable directory,

Portable version does not use other/old files.

Is this time every time you open settings or just the first time you open it?
Could you first open the tree and then try to open the settings?

Hi Marek, please note that you can consider this a low-priority issue and I would be fine if you'd say that it is what it is. I'm not using settings that often. But happy if you want to dig into it.

On my freshly unzipped portable version, time to open settings is constantly between 13 and 15 seconds. No matter if tree opened or not, tree opened first, or opening settings repeatedly.

After clicking the settings menu or F12:
- Immediately the FC app freezes, mouse pointer hovering over FC window stays normal
- After 5 seconds, FC window title changes to "FreeCommander XE (Not Responding) and mouse pointer changes to type busy
- After 15 seconds, settings window opens

horst.epp wrote: 02.08.2023, 17:38 Here in the actual FC version it takes about 3 seconds, which I find ok.

Well, for me acceptable [but nevertheless still annoying] would be a 1 second load-up time of any configuration in any program

I was wondering if it is due to the fact that the directory is dropboxed.

But an unmirrored directory shows exactly the same delays.

With my old portable installation, I recently reached a 40 seconds delay.

Just an update for whom wants to know how the story continued:

• Meanwhile on B.892 64bit
• Dropbox gone, now everything is on OneDrive
• settings now opens in around 5 secs

No clue what really caused the improvement. But I'm good.