Internally Fixed Bug Event Log error about error log file

[Tyubo]

Software Version

5.1.1

Operating System

Windows 11 (64 bit)

Hello!

After every power-on/reboot, I read this in the system log!
What can cause it?

Event ID 101 from Spybot 3 source cannot be found. The component that triggered the event is not installed on the local computer, or the installation is corrupted. You can install or repair the component on the local computer.

If the source of the event is a different computer, the display information must have been saved with the event.

The following information is associated with the event:

Unable to open file "<$LOCALAPPDATA>Safer-Networking Ltd.Spybot Anti-BeaconSpybot3AntiBeacon.log": The syntax of the file©,©directory or folder icon is incorrect.
TSpybot3Logger.AddLineToLogFile({Spybot3AntiBeacon.exe} 15CC:161C [08:10:09.016 +00:00.001] < [unit finalization] RegistryCache)
Drogram Files (x86)Safer-Networking LtdSpybot Anti-BeaconSpybot3AntiBeacon.exe
5.1.1.325
5.1.1.0

The system cannot find the specified file


Thanks!
Czap Gábor

 

[PepiMK]

Thank you Czap,

I've flagged it as an open bug and added it to our 5.2 todo list.
You can ignore this error, since it's only about a log file you will not need.

But maybe you can check if the folder C:\Users\YourName\AppData\Local\Safer-Networking Ltd.\Spybot Anti-Beacon\ exists?

 

[Tyubo]

OK!
Thanks!

 

[Tempak]

Same issue, Spybot Anti-Beacon Plus v5.1.1, Windows 10 x64

Plenty "Spybot 3" events complaining about invalid log path:

Unable to open file "<$LOCALAPPDATA>\Safer-Networking Ltd.\Spybot Anti-Beacon\Spybot3AntiBeacon.log"

Process Monintor shows that app tries to access following, invalid path:

D:\Program Files\Spybot Anti-Beacon\<$LOCALAPPDATA>\Safer-Networking Ltd\Spybot Anti-Beacon\

Where D:\Program Files\Spybot Anti-Beacon\ is folder where app is installed on my PC.
Looks like <$LOCALAPPDATA> is not substituted with %LOCALAPPDATA% value

And there is no %LOCALAPPDATA%\Safer-Networking Ltd\ folder on my PC, because app tries to create it with invalid name.

BTW. I'm also afraid, that "VMWare Customer Experience Improvement Program" immunizer cannot find existing %APPDATA%\VMWare\preferences.ini file because another path substitution failure.

 

[PepiMK]

I think I'll split of the last thing into a new thread here to keep things separated.
The <$LOCALAPPDATA> issue is fixed (path templates were loaded too late for this to work).