Log4OM

When I try and install 2.9.0 I get the following error message; If I check the file properties, (right click on the folder and files) and check security properties, then all combinations are ticked "Allow" for permissions. If I select "Skip this file", then everything else installs OK and I can run the programme.
I am not installing as an Administrator.
Any ideas?

Hi Peter,
Not helpful but I get a similar response when trying to upgrade from 2.8 to 2.9.
In my case the MoveFile failed error code is 2 and the explanation "The system cannot find the file specified"
OS is W10 64bit Home. I am installing as Administrator.
I have not tried to install using the skip file option but will give it a go.

Find the original configmanager file and I think you will find its read only or blocked in the properties, a recent Windows update did that to many files.

Hi Terry, Thanks for that.
In my case the installation error shows it cannot find the L4ONG.ConfigManager.exe file, when I look in Log4OMNextGen folder I can find
such a file but with the .config suffix (L4ONG.ConfigManager.exe.config) This file is dated 30/07/2020 and 5KB.

I can confirm now that skip the file during the 2.9 install does allow the the install to complete and the application appears to work OK.

This is my file properties for L4ONG.ConfigManager.exe. I cannot see what is blocking it?

Without Log4OM running try deleting the file then re-install 2.9

The file is only a tool we muse occasionally to update and change factors, not that important to you

I get the same message so I did a little more digging. My antivirus software (Bitdefender) is blocking the installation, so I investigated that a little more too. This is the warning message it gives me:
The file C:\Program Files (x86)\IW3HMH\Log4OM NextGen\is-0PH49.tmp is infected with Gen:Variant.Barys.8268.
Now this is not a good sign!
I'm going to hold off on installing 2.9 until someone investigates this.
Mark
G0TMT

The dBITefender is a false positive, I have installed 2.9.0.0 several times and it's was checked by various A/V software without incident

I have same issue, it is 100% a BitDefender false positive, and in my case it is also a BitDefender bug, because the antivirus warn me about a threat but it doesn't tell me which one, there is no information in the bit defender warning list, and I can not instruct BitDefender to ignore it
I suggest to anyone who has the same problem to go to the web page https://www.bitdefender.com/submit/ and submit Log4OM reporting it as a false positive so that they will verify it... if more people make the same report, maybe they fix it more quickly

Be like me and dump the software, I have relied just on Windows Defender and MalwareBytes for many years, got fed up with antivirus software taking over my PC and changing things without warning.