[953] CRASH involving files with MoTW

[Free4all]

FreeCommander XE 2026 Build 953 64-bit in Windows 11

Steps to reproduce (STR):

1. Download a file from the internet so that it has a MoTW, or add a MoTW to any existing file (if you're not familiar with MoTW, see https://en.wikipedia.org/wiki/Mark_of_the_Web).
2. In FC, open the Search Files/Folders window.
3. Perform any search so the file from #1 appears in the search results.
4. In the search results, double-click on the file from #1.
5. Windows will provide a dialog box asking if you want to open that file.
6. In that dialog box, click 'Cancel'.
7. FC will crash 100% of the time.

[Odamn-Ete]

I followed your steps to reproduce and I can only partially confirm this bug.
After clicking cancel on in the Windows UAC dialog FC did not crash. FC presented me with an error message, see below:



On the error message I clicked on "continue application" without incurring further issues.
(A note to the translators, I am running FC with German language settings and the error message is in english.)

Following are the file types I tested including the results.


I Tested the following file types:
*.exe -> error message
*.bz2 -> no Windows UAC dialog
*.tar.gz -> no Windows UAC dialog
*.ids -> no Windows UAC dialog
*.jpg -> no Windows UAC dialog
*.png -> no Windows UAC dialog
*.iso -> error message
*.txt -> error message
*.csv -> no Windows UAC dialog
*.xml -> no Windows UAC dialog
*.pdf -> no Windows UAC dialog
*.run -> no Windows UAC dialog
*.webp -> no Windows UAC dialog
*.zip -> no Windows UAC dialog

FreeCommander XE 2026 Build 953 64-bit non public
Windows 11 Pro 64-bit Version 25H2 Build 26200.9457

Identical behavior using
FreeCommander XE 2026 Build 9542 64-bit non public TEST!

@Marek: I repeated the actions for the 3 file types above that incurred errors and have sent you bug reports regarding this issue.

[Odamn-Ete]

UPDATE

I was asked to send files with MoTWs causing issues. As I had already deleted all MoTWs, I redownloaded the specific files and this time I did not have the issues described in my previous post.
Actually, I had no issues whatsoever.

The only changes that had occurred on my system between my post above and the second try were updates of Windows Defender signature files and an update to my browser.
I would think the issue was with the browser and not FC because the browser saves metadata to the alternate streams (MoTWs) of downloaded files.

@Free4all: If I may, I would suggest updating your browser, deleting your existing MoTWs, redownloading the specific files and testing again.

Best Regards