Total Commander

Hi!
Please setup call for cm_UnloadPlugins command from the any new item of the main menu.
Use some Lister plugin. Which will be easily to test to next step. For ex. PE Viewer.
Now try to move the appropriate plugin's WLX64 file (being using the T64 of course) - and
you should get "Access denied on file" warning dlg. It's Right + expected.
Now let's call pre-created new menu item with cm_UnloadPlugins cmd.
And retry to move the wlx64 file...
With surprise you will get again "Access denied on file" warning dlg. It's wrong + UN-expected.

IF you will try to call the same command but only from the Command line of the TC directly, so
from time to time it will work but mostly also will not(((

TC32 + plug WLX (x86) - this command will work always.

Not confirmed. After using PE Viewer and then calling cm_UnloadPlugins, I can move or even delete PEViewer.wlx64.

It is sad that a situation that seems to be quite easily reproducible - but on my side - turns out to have
some hidden circumstances that prevent the same easy reproduction, but on the other side...

It can be easily reproduced on a fresh installation. with this plugin alone.
And it is on the 64bit version of everything of course.

I cannot reproduce it either.

The last test I tried was on Windows Sandbox, where I did this:

• Installed tcmd1151x32_64.exe.
• Started TC 64-bit.
• Installed tc1151_win10x86_amd64_eng.zip (petermad's extended menu's that adds Cmd 2913 to menu).
• Installed wlx_peviewer_3.0.17.2.rar.
• Viewed tcmd1151x32_64.exe.
• Closed Lister.
• Tried to delete PEViewer.wlx64, or move to a different drive, which failed to delete the file.
• Selected the menu option to unload plugins.
• Tried to delete PEViewer.wlx64, or move to a different drive, which worked fine.

2AntonyD
Could you repeat the test with just the PE Viewer installed? To do this, open the wincmd.ini, and then
1. Rename the section [ListerPlugins] to [ListerPlugins.org]
2. Create a new section [ListerPlugins]
3. Look for the lines for PEViewer, e.g. 52=C:\path\PEViewer\PEViewer.wlx and 52_detect=detect string
4. Put them in the new section [ListerPlugins]
5. Change the number to zero, e.g. 0=C:\path\PEViewer\PEViewer.wlx and 0_detect=detect string
6. Close and re-open Total Commander

I can repeat it with ANY other Lister x64 plug.
PE Viewer was used in desc. only because it was the last one tested.

It's possible that another process holds a handle open to the Lister plugin files. They're DLLs after all so they could contain suspicious or even malicious code. Maybe repeat the same procedure in Windows Safe Mode to rule out almost all background programs and services (including anti-virus software).

I assumed this moment. Therefore, I disabled everything that I am aware of in my system.
And no, it didn't help. Always and only 64-bit extensions were blocked and did not
were closed by this cmd. With 32 bits, everything is fine.
I installed version 10.50 - and everything worked immediately.

If TC 10.50 works and the version you tested initially does not, maybe you can narrow it down further by testing the versions between these two. I'd ignore the beta versions for now. If you narrowed it down, maybe we can find some change in history.txt that might be responsible. Then Ghisler can check the code and maybe fix whatever issue there might be.

You could use the tool LockHunter to find out what is locking the file, and even unlock it:
https://lockhunter.com/download.htm
The tool can be used via context menu also in Total Commander.

If it indicates that Total Commander itself is locking the file, then it may be
1. Another plugin loading other plugins (Tab view in Lister?)
2. A virus scanner running in the context of Total Commander.

I already know it - TotalCmd64.exe

AntonyD wrote: 2025-04-25, 11:47 UTC I already know it - TotalCmd64.exe

How do you know it?

with help of lockhunter))
I just used it far before this post with suggestion was published...

AntonyD wrote: 2025-04-25, 13:26 UTC with help of lockhunter))

Good to know that. Have you tried disabling the virus scanner and/or make an exception for Total Commander?

Have you tried

Please remember this:

AntonyD wrote: 2025-04-23, 13:16 UTC Therefore, I disabled everything that I am aware of in my system.
And no, it didn't help.

this includes all what I am aware of... of course and VS.