JAWS LogManUI.exe tool

    Setup your system so nothing other than JAWS and any affected app that helps demonstrate the problem are running. If this is a crash at startup, exit JAWS, set up FSI Log to start running, then launch JAWS.
    Go to c:\Program Files\Freedom Scientific\JAWS\2025\Support folder. You can leave it open.
    Launch LogManUI.exe.
    Once you are ready to start the steps to reproduce the problem, press the Start Logging button on the FSI Log.
    Proceed to reproduce the bug.
    Note: If this involves a crash with shutting down, wait until JAWS has indeed shut down before you stop logging. If needed, use Task Manager > Processes to end the JFW.exe component in the Processes list.
    Press ALT+TAB to return to the FSI Log dialog and select Stop Logging. At this point, the log file will be created in the Support folder with an extension .etl.
    Get the latest ETL files created in the Support folder from step 2. It should look like this: Logcomponents0001.part1.etl. The first number indicates the log that's running, and there can be multiple parts, e.g. part2, part3, etc. if the log gets too large. Each new file produced is incremented in number.
    You can now run the FS Support Tool, which will gather all .etl files created from logging. Submit a bug report and reference the report package.

    Tips for using LogMan with JAWS

    LogMan never collects passwords, nor the raw keyboard stream. It only collects events that happen with JAWS and the operating system, to try to reconstruct the state that causes misbehavior.
    Log Manager should continue to log even in the Secure Desktop.
    A log file should finish being created even if the system shuts down or you must power-off mid-logging.
    You can keep the LogMan app running, but if you need to find it after use of other apps, it will have moved to the System Tray represented by a gray and white icon.
    Development often likes to have the log from the starting launch of the FS Product, through the reproducible issue, to the point you fully close the FS Product.
    If the ETL file is large, development can be helped if you indicate about what time you got the issue, so they can more quickly find the area in the ETL file to target.
    When logging, if data during logging reaches a maximum files size (.5 GB), the logging will continue by creating a second file in a series. It will continue to create files as needed within a series to capture the amount of data. ETL files for the same logging session will accrue, each with the same number but a different part. When sending log files for a specific incident, be sure to send all within the same series.

Keyboard Logging with LogManUI tool