DocumentationAPI ReferenceRelease Notes
Release Notes
These docs are for v26.1. Click to read the latest docs for v26.4.

EPM GPO 26.4.1

This release updates the EPM for Windows agent and Privilege Management Reporting for Group Policy deployments: the PM Reporting Database and its Reporting Pack and Event Parser. It begins the rollout of QuickStart version 2 and adds smart card authentication with Pointsharp Net iD Client. Deploy the updated Windows agent to get the endpoint changes, and read the action panel before you upgrade.

📦 At a glance

ComponentRuns onWhat changedYour action
PM Reporting DatabaseDatabase serverFixesUpgrade
 Reporting PackReporting serverNo changesUpgrade with the database
 Event ParserDatabase serverNo changesUpgrade with the database
EPM for WindowsEndpointNew features, enhancements, fixesDeploy

See Build numbers for versions for every component.

🚨 Action required before upgrade

  • The minimum .NET Framework version rises from 4.6.2 to 4.7.2 for Power Rules, PowerShell audit scripts, Agent Protection, Trace Config and the RADIUS authentication dialog. On Windows Server 2016 you must install 4.7.2 or later to keep using those features.

⭐ Highlights

QuickStart V2, on Windows and macOS

On Windows, QuickStart has been rebuilt as a single policy that covers both desktop and Windows Server, so there is no longer a separate server template to select or maintain. The new policy reflects the configuration our field teams have found works best in real customer environments, which means it can be deployed as it ships without needing to be modified by hand first. Administrators get a trusted starting point and protection on day one, rather than a template that has to be reworked before it is useful.

The macOS QuickStart policy has also been refreshed. Both policies have been updated to meet current accessibility and branding standards.

If you are already using QuickStart, nothing changes in your environment. Your existing policy continues to run exactly as it does today, and the new version is available for you to adopt when you are ready. Guidance for bringing the new content into a running policy is published in the knowledge base.

ℹ️ Requires Windows agent 26.4. Group Policy deployments use EPM for Windows only, so the Windows QuickStart is the one that applies here.

For more information, see QuickStart policy adoption guide.

Smart card authentication with Pointsharp Net iD Client

EPM for Windows now supports smart cards that use Pointsharp Net iD Client, so users can authenticate in EPM messages on their device with the same card they use to sign in to Windows.

ℹ️ Requires Windows agent 26.4.

🧩 Changes by component

Issues reported by customers through an escalation are listed first.

Privilege Management Reporting Database 26.4.1

PM Reporting Database 26.4.2.1

🛠️ Issues resolved

DescriptionResolution
The Discovery All report timed out and failed to load when the On-Demand / Auto filter was applied to a large number of events.The Discovery All report now loads without timing out when the On-Demand / Auto filter is applied, even with a large number of events.

Reporting Pack: No new features or enhancements. Upgrade it with the database.

Event Parser: No new features or enhancements. Upgrade it with the database.

EPM for Windows 26.4.1

🆕 New features

  • QuickStart V2: One Windows policy for desktop and server. See Highlights.
  • Added support for smart cards managed by 3rd party key storage providers. See Highlights.

✨ Enhancements

.NET runtime updated to 10.0.14

Updated the .NET runtime bundled with the endpoint app to 10.0.14 to apply Microsoft's latest security patches.

Minimum .NET Framework version is now 4.7.2
  • The minimum .NET Framework version for Power Rules, PowerShell audit scripts, Agent Protection, Trace Config and the RADIUS authentication dialog box is now 4.7.2 (previously 4.6.2). Microsoft ends support for 4.6.2 on 12 January 2027.

  • Windows Server 2019 and later include 4.7.2.

  • On Windows Server 2016, install .NET Framework 4.7.2 or later to use these features.

🛠️ Issues resolved

DescriptionResolution
An account filter on an Application Rule was ignored when the rule matched an uninstaller, so the rule applied to everyone the Workstyle covers.Uninstaller rules now honor the account filter for uninstalls started from Settings, Control Panel, or the command line, and apply only to the accounts in the filter.
When Endpoint Privilege Management elevated an Electron application that requires administrator rights for a standard user, the application could open a blank window and then close within a second of launch.Electron applications that require administrator rights now open and run correctly when Endpoint Privilege Management elevates them for a standard user.
A child process launched from the Open or Save dialog of an elevated application could keep the elevated rights when the rule matched the built-in Any Application group.The new secure built-in groups, such as <Any Application>, now force standard user rights on these dialogs. Policies that still use the deprecated Any groups keep the previous behavior until you switch them to the new groups, which Policy Assistant offers as a one-click fix.
When an application had Force standard user rights on File Open/Save common dialogs enabled, a Content Rule that allows access could let users create, rename, delete, or overwrite protected files from the Open or Save dialog.Users can no longer create, rename, delete, or overwrite protected files from these dialogs when this option is enabled, even when a Content Rule allows access.
The Privilege Management service could stop unexpectedly if a policy update was applied while a COM elevation with a PowerRules script was in progress.The Privilege Management service now keeps running when a policy update is applied during a COM elevation with a PowerRules script.
The Privilege Management service could stop unexpectedly if a policy update was applied while a process that inherits its rule from its parent process was starting.The Privilege Management service now keeps running when a policy update is applied while a process that inherits its rule from its parent process is starting.
Windows endpoints running Cortex XDR could stop unexpectedly with a KMODE_EXCEPTION_NOT_HANDLED blue screen error when Cortex XDR scanned running processes.Windows endpoints running Cortex XDR no longer stop with a blue screen error when Cortex XDR scans running processes.
When an Application Rule elevated Windows Settings, choosing Restart or Shut down from the Windows Start menu could do nothing, and no error appeared.Restart and Shut down now work as expected when an Application Rule elevates Windows Settings.
Processes matched through Child Inheritance, from grandchildren onward, could be missing application details such as the file path and hashes in their audit events, or might not receive the rule’s admin rights.Processes matched through Child Inheritance at every level now receive the rule’s admin rights, and their audit events include the full application details.
Audit events for child processes that inherited a rule through Child Inheritance showed a blank Application Group in Analytics, so you couldn’t filter or report on child process activity by Application Group.These audit events now show the Application Group, so you can filter and report on child process activity by Application Group in Analytics.
Application Rules that match on Product Name or Product Description could fail to match an application whose file version information was non-standard, so a different rule applied instead.These rules now match correctly when an application’s file version information is non-standard.
Agent Protection could turn back on soon after it was suspended with an uninstall token, which blocked the uninstall of Package Manager and the PMC Adapter. This happened when something checked the PMC Adapter’s service status, such as a WMI query.Agent Protection now stays suspended after you suspend it with an uninstall token, even when something checks the PMC Adapter’s service status, so you can uninstall Package Manager and the PMC Adapter.
Audit events for blocked applications reported the rule’s token, such as Add Admin Rights or Custom, instead of Passive (No Change).Block events in the event log, BeyondInsight, ePO, and PMC now report Passive (No Change), and the [PG_TOKEN_NAME] variable in audit scripts and messages returns Unmodified for Block rules.

🔐 Security fixes

ComponentSecurity fixesDetails
PM Reporting Database, Reporting Pack and Event Parser0No changes
EPM for Windows16Anti-tamper hardening, privilege-boundary and memory-protection fixes, and third-party runtime and library updates.

🔄 Compatibility

ComponentRecommendedAlso supported
PM Reporting Database26.4.2.1
EPM for Windows26.4.1.27326.3.1.289 | 26.2.1.417 | 26.1.23.0 | 25.8.12.0 | 25.4.270.0 | 25.4.184.0 | 25.2.1.0 | 24.8.98.0 | 24.7.425.0 | 24.5.361.0

Build numbers

ComponentBuild
PM Reporting Database26.4.2.1
EPM for Windows26.4.1.273

©2003-2026 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.