FreeCommander XE showing non-existent files and not showing existent files

[H5JCa3y4quRpwN0g]

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 FC XE 2024 public 32-bit on Windows 10 Enterprise 22H2 with all updates installed that were available at the time of writing. FC is showing the wrong contents in the directory

Code: Select all

C:\Windows\System32\Recovery

Please have a look at the attached screenshots. The first one is from Windows Explorer which lists the correct contents. The second one is from the Windows command prompt where the "dir" command also outputs the correct contents; the second screenshot also shows that there is nothing special with the attributes of the files in that directory. The third screenshot is from FC which lists the wrong contents.

As we can see, FC does not list the file "ReAgent_Merged.xml1" which definitely exists (I can open it with any text editor using Windows explorer, change it and save it), and lists the file "Winre.wim" which definitely does not exist.

Any ideas?

Please note the following:

- In Windows Explorer, I have turned on "Show hidden files, folders and drives", and I have turned off "Hide protected operating system files (Recommended)".
- In FC, I have turned on "Show hidden items" and "Show system items".
- I am usually working as a non-administrative user. However, if I log in as Administrator, the situation does not change: Still Windows Explorer and Windows command prompt show the correct directory contents, but FC shows a file that does not exist and does not show a file that exists.
- Yes, I have hit Ctrl+R a zillion time in FC in the respective window pane.
- I have not installed any plugins in FC. The only that I possibly did was to change some options in "Tools -> Settings".
- I have made sure that I have no filters turned on in FC. But anyway, filters shouldn't make FC list files that don't exist.

[horst.epp]

Not confirmed

[H5JCa3y4quRpwN0g]

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 list the existent "ReAgent_Merged.xml1" file.

I also have run "sfc /scannow" and "chkdsk c:". In both cases, no problems have been reported.

I am quite sure that the problem is due to a bug in FreeCommander, not due to a corrupted file system, because 1) file system tools did not report any error, and because 2) Windows Explorer lists the files in that folder correctly. I believe that with the current settings in Windows Explorer and in FreeCommander (both are configured to always show every file, including hidden and system files), FreeCommander always should show exactly the same files as Windows Explorer. At least, unless I am moronic enough to have an active filter somewhere that I forgot about. But even then, this wouldn't explain why FreeCommander is listing a file that definitely does not exist.

Is there some sort of caching in FreeCommander that survives Ctrl+R? If yes, can I turn it off?

[H5JCa3y4quRpwN0g]

@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 "Winre.wim" appear in the directory in question, and FreeCommander should list it if you have configured it to list hidden and system files.
- Issue the following command: "reagentc /enable".
- This restores the original situation and makes "Winre.wim" disappear again from that directory.
- The thrilling question is if FreeCommander nevertheless still lists "Winre.wim" in that directory.

Short explanation:

"Winre.wim" contains the Windows Recovery Environment, which e.g. can be activated when your computer boots and can't start Windows any more for some reason. If you do not have a Windows Recovery partition on your disk, "Winre.wim" is used to provide the recovery environment. Naturally, that's usually not a good choice because it means that you need access to your normal Windows installation to get into the recovery environment at all. Therefore, keeping the recovery environment in its own partition usually is the better choice, because that partition normally is not touched by Windows and thus is more reliable in case of problems.

However, Windows lets you choose. "reagentc /disable" deactivates the extra recovery partition (of course it doesn't delete it), builds "Winre.wim" in "C:\Windows\System32\Recovery" and tells Windows to use this WIM file to provide the recovery environment. "reagent /enable" effects the opposite. It (re-) activates the extra recovery partition; that is, it moves the contents of "Winre.wim" to the recovery partition, tells Windows to use the recovery environment from the recovery partition in case of problems, and deletes "Winre.wim".

For certain reasons, I had to play around with "reagentc" yesterday, which may have caused the situation. Unfortunately, I really don't know whether or not this is the case. I didn't visit "c:\windows\system32\recovery" before and can't tell if FC has behaved correctly before.

But regardless of whether or not "reagentc" has caused the problem: FC must show the same directory contents as Windows Explorer if both are configure the same way (show hidden files, show system files). It would be exciting to know if you run into the same issue after the actions shown above.

[horst.epp]

I tried your scenario.
No problem with FC.
It works perfect here under Windows 11 24H2.
The screenshots show the FC display after disabling and after enable it again.

[H5JCa3y4quRpwN0g]

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 my place) vs. Windows 11 (at your place). I have a second PC where FC also behaves the wrong way in the exactly same folder. On that other PC, it lists "ReAgent.xml", but not "ReAgent_Merged.xml1", although the latter exists. Interestingly, it does not list "Winre.wim" there (which is correct).

So we have two failing FreeCommander installations on two PCs that have been installed at different times and where the installation is totally different otherwise. The only common thing is that both run Windows 10 Enterprise 22H2.

Best regards, and thanks again!

[Karol]

Check the info about 32 bit version:

32 bit programs are redirected from “%windir%\system32” to “%windir%\SysWOW64” automatically.

[H5JCa3y4quRpwN0g]

@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 of FC and therefore didn't encounter the problem.

So actually this is not a bug. Would somebody kind enough to move this thread to the right place?

Thanks @all again.