We recently introduced a preview version of a new rule type, Windows Log Event that continuously checks the Windows event log for any events matching the rule condition.

However, this may impact the system performance especially if there are multiple users on a computer (e.g., on a VDI/RDP setup) or the Windows event log becomes too large for other reasons.

To mitigate that, the feature will be automatically disabled if no rules are using this rule type and enabled if there is any active rule(s) using this rule type.

Due to a bug, MS Teams meetings and calls wouldn't get captured for both the Web and Desktop versions when a personal account was used. Business/corporate accounts weren't affected.

The bug seemed to affect Agent version 23.31.x but other versions might be affected too.

The bug is fixed now so that meetings/calls using a personal account will be captured and reported on the Monitoring > Online Meetings report:

Due to a bug, the EXCEPT conditions in a behavior rule might get ignored entirely in some situations.

This could happen if you had more than one type of condition in the EXCEPT field (Equals, Contains, Match, etc.), the whole EXCEPT condition might get ignored.

For example, if you used the rule below, the entire EXCEPT field would be ignored if an email didn't match the first hotmail.com condition even if it equaled any item from the gmail Shared List, or matched any item in the outlook Shared List:

The bug is fixed now.

Due to a bug, the Hidden Agent could stop monitoring a user when they logged in after a shutdown/restart/logout event. As a result, the user might show offline on the Dashboard.

This could happen if the shutdown, restart, or log-out process didn't finish properly causing the Agent to become unstable.

This could especially happen on a virtual desktop (e.g., a Windows Hyper-V VM) but it could also happen on a host if any process/service got hung up.

The bug seemed to affect Agent version 23.37.x but other versions might be affected too.

The bug is fixed now.

Due to a bug, a Websites-based rule containing a Request Type: Webpage Visited condition would get triggered even when the user wasn't visiting the website(s) mentioned in the rule.

In the example below, if a user previously visited careerbeacon.com and immediately minimized the browser window or switched to another tab, the rule would continue to trigger for the careerbeacon.com page and multiple alerts would show up on reports like the BI Reports > Behavior Alerts, Behavior > Alerts, etc.:

The bug is fixed now so that the Request Type: Webpage Visited condition will only trigger the rule when the user visits the website. It will not trigger the rule if the browser tab/window is inactive or in the background.

Due to some recent changes introduced by Opera, the DISABLE BUILT-IN PASSWORD MANAGER OF KNOWN BROWSERS on the Advanced settings window (Monitoring Settings > Monitoring Profile > ADVANCED button) would no longer work for the Opera browser. The user would get prompted to save their password:

The bug is fixed now.

Due to a bug, the Clipboard Monitoring Service (clm.exe) of the Hidden Agent wouldn't stop when the Agent itself was stopped or exited.

The bug is fixed now.

In some rare situations, the Agent might crash if it encountered any issues or disruption while recording the screen. This could happen for several reasons but one possible scenario is if you had a multi-monitor setup and switched between the screens and apps, connected/disconnected the monitors, etc.

The bug seemed to affect Agent version 23.38.x but other versions might be affected too.

The bug is fixed now.