Hello, these are the february 2026 Release Notes of NDD Print, we have a lot of news, and we hope you like it.
Here you can download the latest versions.
See a summary of all updates and click on the links to navigate each one.
NDD Print Client Lexmark 5.16.2
fixes
NDD Print Tracer 5.4.3
fixes
NDD Print MF HP 5.31.3
fixes
-
Script does not create the ‘UnregisteredPrinters’ table in Postgres
-
Failure to migrate XML data to the database after creating the database via script
-
Creation script does not configure the “Auto-close” property in SQL Server
-
NDD Print Client HP - Error when releasing more than 25 documents
NDD Print Client Lexarmk - 5.16.2
Released in 27 february 2026
Fixes
Logout Performance Fix
How did the problem happen? A progressive delay was identified in the initialisation of the embedded interface immediately after logout. This behaviour generated a cumulative delay that reached up to 60 seconds on some occasions. As a workaround, the equipment was restarted, but the slowness returned with continued use of the embedded solution.
When did the problem ? The failure manifested itself in scenarios with high user turnover, specifically when multiple logins and logoffs were performed sequentially in a short period of time.
Where did the problem happen? The instability was detected on specific equipment using the installed Lexmark Client.
What was done to fix it? The session termination architecture was refactored. The logout process was centralised into a single, optimised method. This change prevents redundant calls to screens and background processes during user logout, eliminating the bottlenecks that caused systemic slowness
NDD Print Tracer - 5.4.3
Released on 20 February 2026
Fixes
JSON file fix
How did the problem occur? When clicking on a cell in the Log Receiver tab that contained a message with json
When did the problem occur? When the json contained semicolons
Where did the problem occur? In the parser of logs received by Kyocera equipment with NDD Print authentication
What was done to fix it? Changed the parser logic so that semicolons are no longer used to break up the information to be displayed in the grid
NDD Print MF HP - 5.31.3
Released on 18 February 2026
Fixes
Script does not create the ‘UnregisteredPrinters’ table in Postgres
How did the problem happen? When migrating the database from SQL Server to Postgres, the UnregisteredPrinters table was not generated at the destination.
When did the problem ? During the data migration process between the SGDBs (SQL Server → Postgres).
Where did the problem happen? In the PostgreSQL database (visible via PGAdmin), where the absence of the table was noted.
What was done to fix it? The creation of the table was implemented in the DatabaseMigration.GetCreateTableSql method, ensuring that the creation script is executed correctly for Postgres.
Failure to migrate XML data to the database after creating the database via script
How did the problem happen? An error occurred when attempting to migrate printer data contained in XML from older versions (e.g., 5.24.1) to a new database (5.31.2) created via script.
When did the problem ? When applying the new configuration after updating MF HP, where migration from the legacy (XML) to the database is mandatory.
Where did the problem happen? In the path: MF HP Admin > Tools > Settings > Database.
What was done to fix it? Connection validation was adjusted so that the system validates both the master database and the specific database entered by the user, bypassing permission restrictions.
Creation script does not configure the “Auto-close” property in SQL Server
How did the problem happen? The database configuration failed when the user only had db_reader and db_writer permissions, as the script attempted to change properties without the proper permissions or validations.
When did the problem ? When attempting to connect to SQL Server using a user with restricted permissions.
Where did the problem happen? In the menu: MF HP Admin > Tools > Settings > Databases.
What was done to fix it? Added the AUTO_CLOSE OFF setting to the CreateDatabaseSQLServerMFHP.sql script, with a prior validation that only executes the command if the account has sufficient permissions.
Base64 error when loading Admin with decrypted passwords
How did the problem happen? Shared folder passwords stored in plain text (legacy versions) caused a conversion error when read by methods that expected encryption
When did the problem ? When opening Admin after updating a very old version that did not use encryption in the <secret> tag of the PrinterManager table.
Where did the problem happen? On the main screen (loading) of MF HP Admin.
What was done to fix it? An exception handler (FormatException) was implemented. If the password is in raw format, the system returns it normally and encrypts it on the next change/save.
Reference failure in “TestConfiguration”
How did the problem happen? The tool could not locate the DLLs needed to register the reader, resulting in an exception.
When did the problem ? When attempting to make the Register HP Reader call.
Where did the problem happen? In the TestConfiguration utility tool.
What was done to fix it? Adjusted the NuGet package references in the TestConfigurations project, ensuring that all dependencies are available for registration calls.
Port conflict in Postgres installation
How did the problem happen? The installer incorrectly identified port 5432 as busy if there were any processes on similar ports (e.g., 54321, 15432).
When did the problem ? During the installation of NDD Print MF HP when selecting the option to install Postgres locally.
Where did the problem happen? In the installation wizard (MF HP Installer).
What was done to fix it? Changed the verification command to use adjusted Regex, ensuring that only the exact port 5432 is validated.
“Auto-close” validation prevents updating of older versions
How did the problem happen? The system attempted to read the SettingsData.json file to validate “Auto-close”, but this file does not exist in versions prior to 5.25.0, causing the process to crash.
When did the problem ? During the Update Wizard starting from legacy versions (e.g. 5.23).
Where did the problem happen? In the NDD Print MF HP update wizard.
What was done to fix it? The “Auto-close” validation process was restricted to occur only if the source version is higher than 5.25.0.
Printers not added to the print group (MS Entra ID)
How did the problem happen? The GetSettingsV2 method (used for Entra ID) returned domains in a different order than the standard GetSettings, generating divergent keys between MF and NDD Print Releaser.
When did the problem ? When deploying printers in environments configured with Entra ID (version 5.30.0+).
Where did the problem happen? In NDD Printer Deploy, section ‘Printer registered for secure release’.
What was done to fix it? Standardised the use of the GetSettings method for the deployment logic, ensuring consistency in key generation regardless of the use of Entra ID.
NDD Print Client HP - Error when releasing more than 25 documents
How did the problem happen? The release of many simultaneous documents exceeded the standard waiting time (10 seconds), resulting in the error ‘A task was cancelled’.
When did the problem ? In scenarios with station retention, when the Agent's response time exceeded the HP Client limit.
Where did the problem happen? On the pending document release screen on the printer panel (NDD Print MF Client HP).
What was done to fix it? The standard request timeout was increased to 10 minutes and the possibility of manual configuration via a custom settings file was enabled.