Windows 10 LTSC 2019 – Event Log error related to update check

[gycsisz]

Current Behavior

Hi Igor!

I would like to report an issue I noticed with the Windows Memory Cleaner 3.0.8 application.

Previously I was using Windows 10 Pro, and this issue did not occur on that system. I recently switched to Windows 10 LTSC 2019, and the problem appeared only after this change.

The application itself works correctly, memory cleaning functions as expected. However, an error regularly appears in the Windows Event Viewer under the Application log when the automatic update check runs.

The core error message is:
“The requested security protocol is not supported.”

The error is logged in the Application channel and is related to the Update method. It does not affect system stability and occurs only during the automatic update check.

At the moment, the issue is resolved on my system by disabling automatic update checking in the application settings. With this option turned off, the Event Log remains clean and the application continues to work normally.

I am reporting this because it seems possible that the security protocol used during the update check is not compatible with the Windows 10 LTSC 2019 environment. This might be something worth handling in a future version, for example by performing a compatibility check in advance or using a silent fallback mechanism.

I have reported issues before and had a very positive experience with your response, so I wanted to share this as a constructive and potentially useful report.

Thank you for your work and for the application.

Best regards,
gycsisz

WinMemoryCleaner.xml

Expected Behavior

At the moment, the issue is resolved on my system by disabling automatic update checking in the application settings. With this option turned off, the Event Log remains clean and the application continues to work normally.

Steps to Reproduce

At the moment, the issue is resolved on my system by disabling automatic update checking in the application settings. With this option turned off, the Event Log remains clean and the application continues to work normally.

App Version

3.0.8

Windows Version

Windows 10

Additional Context

No response

Checklist

• I have searched the existing issues to make sure this bug has not been reported yet.
• I have tested with the latest version of the application.

[gycsisz]

Hi,

I would like to clarify and extend my previous bug report regarding the Windows Memory Cleaner 3.0.8 application.

After further testing, it became clear that the issue is not resolved simply by disabling automatic update checking in the application settings.

The following behavior can be consistently reproduced on Windows 10 LTSC 2019:

– Automatic update checking is disabled in the application settings
– The application starts automatically with Windows
– Despite this, the Update method still runs during application startup
– This results in an Event Viewer error on every system startup:

“The requested security protocol is not supported.”

If I disable the application from starting automatically with Windows, the error no longer appears. However, in that case the application does not run at all unless started manually.

This indicates that the update check is executed as part of the application startup process, independently of the automatic update setting, meaning that the setting is currently not honored on this system.

The application otherwise works correctly, and the issue affects only the startup update check on Windows 10 LTSC 2019.

I am sending this clarification because it may help identify the root cause more accurately, for example by skipping the update check at startup when automatic updates are disabled or when the application is running on LTSC systems.

Thank you for your time and for your work on the application.

Best regards,
gycsisz

[IgorMundstein]

Hi @gycsisz

Thank you so much for the incredibly detailed report and the follow-up clarification. It is rare to see such a high-quality issue report with logs, reproduction steps, and analysis—it made identifying the root causes much faster!

I have dug into the code and found two distinct issues that validate exactly what you were experiencing on Windows 10 LTSC 2019:

1. The "Start on Boot" Bug: You were absolutely right. There was a logic flaw in the update check condition (&& instead of ||), which meant that if "Automatic Updates" were disabled, the app would actually accidentally proceed to check for updates immediately on startup.
2. The Security Protocol Error: The application was strictly forcing TLS 1.3 (SecurityProtocolType.Tls13). While this works on Windows 11 and newer Windows 10 builds, the LTSC 2019 environment (and likely Server 2019) does not support this flag in the .NET provider, causing the crash you saw in the Event Viewer.

The Fix:

I have corrected the update logic to properly respect your settings and adjusted the security protocol to use TLS 1.2, which is fully secure and supported on your system.

Try this beta version with the fixes and some UI updates not released yet.

Please give it a try when you have a moment, and let me know if the Event Viewer errors are gone.

[gycsisz]

Hi Igor,

I downloaded and tested the 3.0.9 beta version.
After 2–3 Windows restarts it works perfectly.

I am attaching the Event Viewer entry as well, so you can see it on your side.

Thank you very much for the quick help and the fix. I really appreciate it.

Best regards,
your friend,
gycsisz

[IgorMundstein]

@gycsisz

I've removed your event files from the message to prevent any data exposure from your system.

These fixes will be included in the next release.