Yesterday I upgraded to Boxcryptor 2.3.401.400 (released on 7/7/2016) on my Windows 7 Ultimate SP1 computer and after rebooting the computer I started to see the following warning message in the Event Viewer Application Log:
The description for Event ID 0 from source Boxcryptor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ReleaseSemaphore failed in Lock::leave().
Error code: 298 (0x12a)
Upon further review, the warning message appears approximately every 10 to 20 seconds in the Application Log when the Boxcryptor application is not running on my computer. In fact, within 16 hours of installing this version of the Boxcryptor application, over 3,400 Boxcrytor warning messages were logged to my Application Log.
By the way, this warning message did not show up when I had Boxcrytor 2.2.423.322 (released on 4/4/2016) installed on this computer. However, this is not the first issue I have raised on this forum over the logging of somewhat useless warning messages in the Application Log. Last year I also reported the logging of Error code: 2 (0x2) in the Application Log after I installed Boxcryptor 2.2.403.216 on the same computer and this issue has still not been fixed in subsequent builds of the Boxcrytor application. Build 2.3.401.400 is still logging these error messages on occasion to the Application Log.
If it helps, I am running Boxcryptor with a local account and I do not have the application running as a service and it does not auto-start. I manually run the application when I need to access my encrypted files. Also, I performed a clean installation of the Boxcrytor application after I removed the previous version and I rebooted my computer after the removal and the installation of Boxcryptor.
I would like to suggest one of the following two solutions to the logging of these warning messages:
1) Could you please ask your development team to either address this issue with the CBFS developers and have them fix this problem in their software or create/release a new build of the Boxcrytor application that stops logging these useless warning messages in the Application Log by default? If these error messages are needed by your developer for troubleshooting purposes, then add a logging/debug option to the Boxcyptor settings that is disabled by default. Boxcrytor users can then enable it on an as needed basis if they are having issues with the Boxcryptor application on their computers.
2) If your developers would like to record these events when the Boxcrytor application is/is not running, then how about they log all of the warnings, errors, and information events to a separate Boxcrytor log file and move it to the Application and Services Log section of the Event Viewer instead? That way I can continue to monitor my Application, System, and Security Logs for real issues that are taking place on my computer, while still being able to log and review the separate Boxcryptor Log when needed.