Known and Corrected issues

Upgrade

Symptom: The BCM Agent upgrade to 25.1.01 fails on Linux Debian 13.1 relay servers when you run the Linux64Upgrade operational rule or manually execute mtxupgrade.sh. This happens because Debian 13.1 uses OpenSSL 3.5.1, and the installer expects OpenSSL 3.4.0.

Workaround: Use a Debian version that supports OpenSSL 3.4.0, or add the required OpenSSL libraries on Debian 13.1 before you run Linux64Upgrade or mtxupgrade.sh.

26.1.00

Agent

Rebooting the device manually instead of using BCM shows a pop-up message:
CRISTON_PRECISION_SYSTRAY_WINDOWS_CLASS, and user interaction is required before the device reboots. The issue relates to mtxproxy.exe.

Workaround: Use BCM to initiate the reboot. This prevents the pop-up and allows the device to reboot without user interaction.

26.1.00,

25.1.01,

24.1.02,

22.4.06

Patch Management

The Master server cannot download patches when the Master and Patch Manager are on different machines. The FileStore module saves the patch file with a size of 0 bytes, so the Relay rejects the upstream request.

Workaround: Add checks in the FileStore module to ensure the patch file content is saved correctly before sending it upstream.

26.1.00,

25.1.01,

24.1.02,

22.4.06

DRZKZ-8043

Web console

Symptom: When an administrator sets their console language preference to French, any query that uses a date‑based criterion fails to work correctly. Depending on the date format defined in the user’s preferences, the selected date is not applied, the query criterion fails to execute, and the chosen date value is not saved to the database.

26.1.00, 

25.1.01, 

24.1.02, 

22.4.06

DRZKZ-8053

26.1.00, 

25.1.01

Login becomes case‑sensitive, and the console treats the session as valid only when the login is entered with the exact same case as stored in the administrator record.
If the account is defined as LOCAL\Admin but the user logs in as LOCAL\ADMIN, the system considers it a different user and invalidates the session token after 1 minute.

26.1.00, 

25.1.01

DRZKZ-8065

Agent

Symptom: A macOS device connected through GlobalProtect VPN does not communicate with its parent relay because the VPN IP address is not sent to the Relay List server. As a result, the device cannot synchronize or upload its identity.

26.1.00, 

25.1.01,

24.1.02

Symptom: When a patch is superseded by a newer patch, the console shows the superseded patch instead of the superseding one. This causes incorrect visibility of patch relevance and update status.

26.1.00, 

25.1.01

Symptom: The software catalog currently supports Trellix versions up to 5.7.x. Devices running Trellix 5.8 do not populate this software in the BMC Helix CMDB because the catalog does not include this newer version.

Remote Control

Symptom: After updating Linux packages, both remote control and direct access no longer work on Linux endpoints.
Additionally, when the Linux system uses Wayland as the window manager, remote control fails completely.

26.1.00, 

25.1.01

Operational Rules

Symptom: The operational rule executes twice on the endpoint. During execution, the rule runs under two different thread IDs, which indicates that the rule is being triggered multiple times instead of running as a single continuous execution.

26.1.00, 

25.1.01

Web Console

Symptom: The MyApps kiosk remains accessible even when the system variable intended to block access is enabled.
When block access to MyApps is set in Global Settings → System Variables → Security, the published operational rules disappear from the kiosk, but the user can still open the MyApps interface. No warning or popup appears to indicate that access is blocked.

OS Deployment

Symptom: When adding WinPE drivers to a project, the OSD Manager does not detect the drivers and the project build fails if the storage path is set to the default relative location. The project log shows error 0x80070002 because the driver cannot be found.

Workaround: Update the OSD Manager configuration to use an absolute storage path such as C:\OSDStorage. After saving the configuration, the OSD Manager moves the streams to the new path and the project builds successfully.

26.1.00,

25.1.01

Agent

Symptom: The BMC Client Management Agent service stops due to improper handling of internal socket buffer resizing during tunnel operations.

Workaround: Stop the agent, edit the mtxagent.ini file, and set the following four parameters to the same value:

• TunneledSocketSendBufferSize
• TunneledSocketReceiveBufferSize
• TunneledSocketSendBufferSizeForTunnel
• TunneledSocketReceiveBufferSizeForTunnel
  Save the file and restart the agent.

26.1.00,

25.1.01

DRZKZ-8103

Agent

Symptom: On macOS 15.4.0, the BMC Client Management agent incorrectly displays shutdown as the currently connected user, even if a different user is actively logged in via the console.

26.1.00,

25.1.01

DRZKZ-8115

Operational Rules

Symptom: When copying and pasting a step within the same operational rule, a popup message repeatedly appears indicating that the rule will be paused, even after the rule is already in paused status. If the rule is assigned to both individual devices and device groups, only individual device assignments are paused while group assignments remain active.

26.1.00,

25.1.01

DRZKZ-8121

Patch Management

Symptom: Firefox and Thunderbird patches fail to download because the patch URL contains a space character, causing a network access error.

26.1.00,

25.1.01

DRZKZ-8126

Web Console

Symptom: RSSO authentication fails in the BCM Web Console when using Microsoft Azure AD because IFRAME-based redirection is blocked in some environments.

Workaround: Replace the Webconsole folder with the patched version provided in the defect attachment to bypass IFRAME and use plain redirection.

26.1.00

DRZKZ-8129

Direct Access

Symptom: Windows event logs in Direct Access show a timestamp delay of one hour before daylight saving time starts.

26.1.00,

25.1.01

DRZKZ-8133

Remote Control (Java Console)

Symptom: When the system variable Request system credentials for Windows remote access is set to Yes, the Java console does not display a window to enter credentials for remote control access. The message appears stating that credentials are required, but no input window is shown.

26.1.00,

25.1.01

DRZKZ-8134

Agent

Symptom: The BCM agent crashes when BeyondTrust version 25.2 or newer is installed and the BeyondTrust service starts. The crash occurs immediately after the service starts and during auto-restart attempts.

26.1.00,

25.1.01

DRZKZ-8140

Console

Symptom: In the Application list under Application Monitoring, minitab 22 22.1 appears twice, with one entry showing zero installations. This results in duplicate data in the BCM database.

26.1.00,

25.1.01

DRZKZ-8144

Hardware Inventory

Symptom: In Hardware Inventory, when you select Display by Property for Media Type, the view is blank. The attributes appear correctly when you select Display by Instance. This issue occurs only for Media Type; other attributes display correctly in both views.

26.1.00,

25.1.01

Console

Symptom: When you click Customization under Global Settings, the menu options do not appear in the right-hand pane. Java logs show a NullPointerException related to color decoding.
Workaround: Replace the EndUserCustomization.xml file with the default version.

26.1.00,

25.1.01

DRZKZ-8163

Console 

Symptom: The In use column in the Software License dashboard shows no values, while the corresponding report displays the usage count.

26.1.00,

25.1.01

DRZKZ-8166

Patch Management

Symptom: When updating a Patch Job window through the REST API, the selected products in the Patch Job criteria are lost. Even when the API call returns success, the product list is not updated as expected.

26.1.00, 

25.1.01

DRZKZ-8168

Patch Management

Symptom: A user with read-only access to devices and device groups can merge devices and edit FAM data. The Merge devices option is not disabled for read-only users. The merge operation only combines FAM data and does not remove the merged device entry.

26.1.00,

25.1.01

DRZKZ-8175

Compliance Management

Symptom: The Master service crashes repeatedly when a compliance rule remains stuck in Evaluating status. Logs do not indicate the issue, and the service fails to stay running. Clearing the compliance rule entry from the work queue resolves the problem.

26.1.00,

25.1.01

DRZKZ-8179

Agent

Symptom: macOS Tahoe (version 26, Darwin 25) was not detected by BMC Client Management.

26.1.00,

25.1.01

DRZKZ-8192

Symptom: The Remedyforce URL for external integration is incorrect. The URL needs to be updated from version 24.0 to 54.0.

26.1.00,

25.1.01

DRZKZ-8197

Warranty End Date

Symptom: Collecting the warranty end date from a device console node returns no value. The issue occurs when the request is initiated from the console but works correctly when triggered by an operational rule step.
Workaround: Use an operational rule step to collect the warranty end date until the fix is applied.

26.1.00,

25.1.01

DRZKZ-8198

Warranty End Date

Symptom: Fetching Dell warranty information fails with error code 401 due to invalid client credentials. As a result, the warranty end date is not populated for Dell devices.

26.1.00,

25.1.01

DRZKZ-8208

Console

Symptom: The console does not contain any option to disable Allow Service to interact with Desktop in Rollout Configuration. This causes agent installation failures in environments that block interactive services.

26.1.00,

25.1.01

OS Deployment

Symptom: OS deployment fails on some target devices with the error failed to create an entity provider. The issue occurs when using PXE menu for target list instead of MAC address. Logs show repeated multicast transfer failures and inability to create an entity provider for unattended files. Devices affected typically use USB NICs without onboard NICs.

Workaround: Create a new target list using the MAC address of the affected device, rebuild and sync the project, then deploy. Deployment succeeds when MAC-based target list is used instead of PXE menu.

26.1.00,

25.1.01

Web Console

26.1.00

Console

Symptom: The console does not display complete hardware details for VMware version 8.03 after upgrading from version 6.7. Information such as BIOS and core count is captured in scanner logs but is not processed or shown in the console.

26.1.00,

25.1.01

Directory Server

Symptom: Active Directory synchronization incorrectly syncs a deprecated device instead of the active device with the same hostname. When a device is deprecated and a new device with the same hostname is brought online, the AD group continues to display the old record instead of the new active device.

Workaround: Stop the BCM Master service, back up the existing file, copy the provided fix to the ../Modules/Agent folder, and restart the BCM Master service. This flushes LDAP sync information for the deprecated device and ensures the active device is synced.

26.1.00,

25.1.01

ITSM Integration

Symptom: Configuration Items (CI) are not populated in incidents created by BMC Client Management in Smart IT. The alert is generated for a device, and the incident is created, but the CI field remains empty.

26.1.00,

25.1.01

Database

Symptom: An incorrect foreign key definition in the Stream table of the StreamDatabase SQLite file prevents deletion of entries.

Workaround: Run SQL queries to recreate the Stream table with the correct foreign key definition:

PRAGMA foreign_keys = 0;
CREATE TABLE sqlitestudio_temp_table AS SELECT * FROM Stream;
DROP TABLE Stream;
CREATE TABLE Stream (Id INTEGER PRIMARY KEY, FamilyId INTEGER REFERENCES StreamFamily(Id), Name VARCHAR, Suffix VARCHAR, SynchronizationType SMALLINT);
INSERT INTO Stream (Id, FamilyId, Name, Suffix, SynchronizationType) SELECT Id, FamilyId, Name, Suffix, SynchronizationType FROM sqlitestudio_temp_table;
DROP TABLE sqlitestudio_temp_table;
PRAGMA foreign_keys = 1;

26.1.00,

25.1.01

Web Console

Symptom: The Action menu in the web console is not displayed for administrators who do not have view or manage permissions for Credentials or Instant Messaging Recording. As a result, some administrators cannot access the top menu in the web console.
Workaround: Add the View capability for object types Credentials or Instant Messaging Recording to the administrator profile.

26.1.00

DRZKZ-8268

Patch Management

Symptom: Patch kb5063878 shows a size of only 1 KB in the console, even though the actual downloaded patch size in the Vision64Database folder is 2.5 GB. Patching is not impacted, but the displayed size is incorrect.
Workaround: Stop the master agent, move the update.bin file from pmupdates/current to pmupdates/pending, run SQL queries to alter column types for FileSize and DownloadSize, recreate statistics, and restart the master agent.

26.1.00

DRZKZ-8270

OS Deployment

Symptom: When the console language is set to French, or when you open the properties of an existing image of type Windows WIM Sysprep image, the image type automatically changes to Windows Setup.

26.1.00

DRZKZ-8283

Remote Control

Symptom: When taking remote control of a device, the resolution and font clarity in applications such as Microsoft Word, Microsoft Outlook, and Microsoft Teams are degraded. After ending the remote session, the poor font quality persists until the affected application is restarted.

26.1.00

DRZKZ-8300

Web Console

Symptom: When opening MyApps on a terminal server, no session ID is generated. The user appears undefined, and the application logs in automatically without creating a session ID.
Workaround: Log out from MyApps and log in again to generate the session ID.

26.1.00

DRZKZ-8306

Web Console

Symptom: In the web console, when searching for an operational rule during assignment, the search does not complete and keeps looping. Results appear in the background, but the search never ends.

26.1.00

DRZKZ-8307

Inventory Management

Symptom: Custom inventory is not updated on end devices. SQL errors appear in the master logs during integration because the system attempts to create a duplicate object type name (Bitlocker) that already exists in hardware inventory.

26.1.00

DRZKZ-8316

Security

Symptom: OpenSSL library used in BMC Client Management contained vulnerabilities.
Workaround: Upgraded OpenSSL to version 3.0.18 and integrated the latest FIPS 140-3 certified module to address security compliance.

26.1.00

DRZKZ-8321

Compliance Management

Symptom: In Compliance Management, the Find Value function does not return results when searching with criteria such as Contains or Equal to. The search window keeps looping and shows empty results even when valid values are entered.

26.1.00

DRZKZ-8339

Application Monitoring

Symptom: The installed count for an application in Application Monitoring does not match the count shown under Query Criteria for scanned applications. For example, PEL 1.4 shows 71 installations in Application Monitoring but only 34 in query results.

26.1.00

DRZKZ-8344

Mobile Device Management (MDM)

Symptom: The DeviceLock command fails on macOS devices because the required PIN parameter is missing.

26.1.00

DRZKZ-8359

Mobile Device Management (MDM)

Symptom: The Stop Lost Mode command fails on Android devices, even though the Start Lost Mode command works correctly. The issue occurs because the command requires a parameter placeholder to be set, even if no parameter is expected.

26.1.00

DRZKZ-8360

Patch Management

Symptom: Adding or removing a service pack in a patch group shows multiple issues:

• Language selection does not appear when adding a service pack.
• Removing a service pack from a patch group does not work.
• Service packs that do not affect any device do not appear in the Service Packs list.

26.1.00

DRZKZ-8374

Remote Control

Symptom: When ending a remote control session in the web console, an exception occurs that blocks the WASM module. This prevents all direct access operations and forces the user to refresh the web page.

26.1.00

DRZKZ-8379

Operational Rules

Symptom: Operational rules stored in the ExecutionQueue table do not execute after the agent initializes. The rules remain in Ready to run state even though they are queued during agent startup.

26.1.00

DRZKZ-8383

Database

Symptom: Some SQL queries retrieve data in the wrong column order, causing the Security popup in the dashboard to not display the topology type. Other queries do not impact the console.

26.1.00

DRZKZ-8384

Core Service

Symptom: The BCM service crashes every 5 minutes on the Helix Master server, making the production environment unavailable. Restarting the service does not resolve the issue.

26.1.00

DRZKZ-8388

Power Management

Symptom: Improper delete handling in the Power Management module caused objects to be deleted twice. The issue occurred because the code did not check the fResult value before performing the delete operation.

26.1.00

DRZKZ-8392

SCAP

Symptom: The Xerces and Xalan libraries used for SCAP are outdated and require an upgrade to fix issues and vulnerabilities. The libraries are updated to Xerces 3.3.0.0 and Xalan 1.12.0.0.

26.1.00,

25.1.01

DRZKZ-8063

Mobile Device Management (MDM)

Symptom: When deleting an administrator, the system tries to transfer associated objects to another administrator. For MDM devices, this process fails because the underlying object type is managed through a database view. As a result, an SQL error appears in the log: cannot update view "mdmappledevicesview".

26.1.00

DRZKZ-8277

Remote Control

Symptom:  The screen‑selection dropdown becomes disabled when the first remote screen is maximized during a multi‑screen Remote Control session in the Web Console. The UI overlay handling is incorrect in fullscreen mode, which prevents the dropdown from remaining active.

26.1.00

Directory Server

Symptom: Nested user groups fail to sync when their Distinguished Names contain escaped commas. BCM processes the escaped comma incorrectly and transforms the value, which causes the sync to fail.

26.1.00,

25.1.02

Operational Rules

Symptom: The copyfile.chl step fails to read a source file when the Operational Rule downloads it from an external HTTPS URL. The failure occurs during execution because the request does not include the required content‑range header when the destination file is empty, causing the remote server to reject the request. Local file copies work as expected.

​

26.1.00,

25.1.02