Messages

1

Support and Feedback / Re: "Quick Look'n Feel" resets to defaults

« on: March 28, 2023, 09:26:42 »

I think it is like the Event Log says, Defender reverts the configuration changes:

Microsoft Defender Antivirus has removed history of malware and other potentially unwanted software

2

Support and Feedback / Re: "Quick Look'n Feel" resets to defaults

« on: March 27, 2023, 10:57:23 »

I think that was it 
I haven't seen the problem for some time now.

All I did was to add the folder
...\AppData\Roaming\MultiCommander\Config
as an exclusion to Microsoft Defender Antivirus scans.

It's a bit annoying that Microsoft considers MultiCommander "potentially unwanted software"!

3

Support and Feedback / Re: "Quick Look'n Feel" resets to defaults

« on: March 20, 2023, 09:36:09 »

Thanks, AlanJB. I think that's a qualified guess.

The Event Viewer has a log entry around the time it happened last time:

Code: [Select]

EventID 1013
Microsoft Defender Antivirus has removed history of malware and other potentially unwanted software.
  Time: 2023-03-01T10:06:11Z
  User: NT AUTHORITY\SYSTEM
The log entry doesn't tell which files were affected, but I'll try to add an Exclusion to Microsoft Defender and see if that helps.

4

Support and Feedback / "Quick Look'n Feel" resets to defaults

« on: March 17, 2023, 13:26:23 »

I have selected "Windows Explorer" style in the "Quick Look'n Feel" dialogue. But after a few days MultiCommander loses this setting and reverts to the default "Commander" style settings without my interaction.

This reverts the following files in \AppData\Roaming\MultiCommander\Config\
CustomKeymappings.xml
ExplorerPanel.xml
MultiCommander.xml

A workaround is to click "Windows Explorer" style again and work with this setting for a few more days, but if I have custom key bindings they are lost in the process since CustomKeymappings.xml is overwritten.

I'm not actually sure if it is MultiCommander itself that reverts the setting, or if it is some mysterious Windows cleanup, but I suspect it is MultiCommander. I'm on Windows 11 Enterprise, Version 22H2.

Any idea what's causing this or if this is a bug in MultiCommander?

Kind regards a long time user,
Anders