Please ensure you are using the “latest version of LogTag® Analyzer”
as the bug you are encountering may already be resolved in the latest version.