Hello, these are the january 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 MF Xerox 5.16.2
fixes
NDD Print MF Epson 5.9.1
fixes
NDD Print n-MF Ricoh 4.10.0
improvements
NDD Print Portal 360 5.79.0
fixes
NDD Print MF Sharp 5.4.2
fixes
NDD Print Digital Shift Epson 5.0.8
fixes
NDD Print MF Brother 5.12.0
fixes
Help Center
UPDATES
NDD Print MF Epson 5.9.0
new feature
NDD Print MF HP 5.31.2
fixes
NDD Print MF Xerox - 5.16.2
Released in 30 January 2026
Fix
Correction in Accounting Logic - IP Conflict
How did the problem happen? The error was triggered by the physical replacement of equipment on the network. When a printer was removed and a new unit was installed using the same IP address as the previous one, the system did not differentiate between the devices.
As a result, the new printer inherited the old equipment's record and count history in the storage file. This resulted in two critical behaviours:
-
Update Blocking: If the counter of the new printer was lower than the value already recorded in the file (inherited from the old printer), the system ignored the new readings. The update was only resumed when the physical counter of the new machine finally exceeded the static number saved in the file.
-
Return Inconsistency: If the new printer's counter was higher, the system updated normally. However, if the old printer was reconnected to the network with the same original IP, the blocking scenario described above would occur again.
When did the problem ? The failure was observed whenever printers were replaced while maintaining the same IP addressing in the network infrastructure.
Where did the problem happen? The problem was located in the data persistence module, specifically in the routine responsible for validating and recording the accounting values in the counter control file.
What was done to fix it? he monitoring logic was improved. The system no longer only observed the linear growth of the counter and began to detect any variation or discrepancy in the reported values. With this new validation, the software is able to identify context changes and ensure that the count for each device is treated in its entirety, regardless of the IP used.
NDD Print MF Epson - 5.9.1
Released in 28 January 2026
Fix
NDD Client Epson authentication failure
How did the problem happen? When attempting to log in to the printer interface to release jobs or access device functions, the user received an authentication error message, preventing access.
When did the problem ? The failure occurred specifically at the time of login. The embedded module made a call to the NDD Print Host, which returned an exception (system error), interrupting the authentication process.
Where did the problem happen? In the embedded client module of Epson devices.
What was done to fix it? An internal component of the code responsible for processing responses from NDD Print Host was optimised. This improvement ensures that communication between the equipment and the server occurs without exceptions, restoring the normal login flow.
NDD Print n-MF Ricoh - 4.10.0
Released on 28 January 2026
Improvement
Accounting for scans independently of prints and copies
What is the objective? To enable the generation of accounting logs even when there are only scan jobs on the printer.
What has been done? A new validation has been added to job processing. Now, all jobs are obtained via request, a hash is generated, and a comparison is made with the previous hash (stored in the registry). When the hash is different, the system identifies that there is a new scan job.
What will be affected? The accounting of scans no longer depends on copies or prints being made in order to be processed.
What is the impact on the environment? There is no impact on the environment. Only the module needs to be updated.
NDD Print Portal 360 – 5.79.0
Released on 24 January 2026
Fixes
Correction
Failure to change the default quota rule
How did the problem happen? The system interface crashed (froze) when attempting to modify the default rule, caused by timeouts due to the long processing time required by the task. This resulted in the new rule not being applied
When did the problem ? The failure was triggered during interactions related to quota management, such as: activation, type change, control unit definition, or standard rule modification. All of these configurations generate long processing times during execution.
Where did the problem happen? Instability occurred in internal processing; when performing the aforementioned actions, the system initiated long processes involving a large amount of data. The system screen remained waiting for processing to finish, generating timeouts.
What was done to fix it? Two different execution modes were implemented for quota settings: immediate and background (requiring the execution type to be configured in each company's database). This allows long, high-volume data processing to be performed asynchronously. This ensures greater interface stability, better performance, and scalability for the solution.
NOTE: The implementations were made for the following configurations: Quota activation/behaviour, Quota type, Control unit, and Default rule.
Failure to generate the user quota report
How did the problem happen? The system interface crashed (froze) when attempting to generate the user quota report, causing the process to fail.
When did the problem ? The failure occurred during the generation of the user quota report with high data volumes, such as credits, debits, expirations, users, among others.
Where did the problem happen? The instability occurred in internal processing when executing the data query for report generation.
What was done to fix it? Two different execution modes were implemented for generating the user quota report: immediate and background (requiring configuration of the execution type in each company's database). This allows user quota reports with high data volumes to be generated asynchronously, preventing crashes.
Microsoft Entra ID domain synchronisation failure
How did the problem happen? When synchronising data with the Microsoft Entra ID domain, some users were not returned in the query, causing these accounts to not be synchronised or updated correctly in NDD Print Portal 360.
When did the problem ? The problem occurred during the data synchronisation process with the Microsoft Entra ID domain.
Where did the problem happen? In the user search routine in Microsoft Azure (Entra ID).
What was done to fix it? The way the application searches for data in Microsoft Azure was reworked, ensuring the correct synchronisation of users with NDD Print Portal 360.
Failure to filter by applications in the job report
How did the problem happen? When using the Applications filter in job reports, the list of options displayed numerical values instead of the names of the applications. As a result, it was not possible to correctly identify which applications were available for filtering.
When did the problem ? The problem occurred when using the Applications filter in the job report.
Where did the problem happen? In NDD Print Portal 360 > Reports > Jobs
What was done to fix it? Internal adjustments were made so that the filter now correctly displays the names of the applications, replacing the numerical values previously displayed.
NDD Print MF Sharp – 5.4.2
Released on 23 January 2026
Fixes
Permission failure when scanning
How did the problem happen? When logging in and attempting to access the scan function, the printer panel displayed the message: ‘You do not have authentication to use this function. Consult your administrator.’
When did the problem ? When the user attempted to start a scan job immediately after authentication.
Where did the problem happen? Directly on the printer interface (screen).
What was done to fix it? The parameter sent to the equipment was adjusted to ensure the transmission of the correct information, and a check was implemented to validate whether the authenticated user has a registered email address.
NDD Print Digital Shift Epson – 5.0.8
Released on 23 January 2026
Fixes
DNS error displayed on the printer screen
How did the problem happen? When attempting to send a scanned document by email, the device interrupted the process and displayed the alert ‘DNS error’.
When did the problem ? During the execution of any scanning job via email.
Where did the problem happen? In the NDD Digital Shift processing flow.
What was done to fix it? We added a systemic validation: now, when the printer is configured via Hostname, the system resolves the network name and communicates directly via IP, eliminating the name resolution failure.
NDD Print MF Brother – 5.12.0
Released on 20 January 2026
Fixes
Adjustment to Print Accounting
How did the problem happen? When making multiple copies of the same document, the CSV file generated by SPLN recorded each copy as an individual entry, maintaining identical metadata (same title, date and time). Due to this duplication of information, the MF Brother system validated only the first record and discarded the others, resulting in a page count lower than the actual number.
When did the problem ? During the process of reading, processing, and accounting for the print jobs contained in the printer's CSV file.
Where did the problem happen? In the integration module responsible for interpreting the print logs (CSV) from Brother machines.
What was done to fix it? The Brother MF processing logic was refactored. Now, the system identifies sequential records that have the same title, date and time as part of a single printing event.
Instead of treating identical entries as duplicates to be discarded, the system now performs the incremental sum of the pages to the first identified job, ensuring that the total volume is counted correctly.
Help Center
Released on 15 January
Updates
Change to the NDD Print Help Center URL
We would like to inform you that the NDD Print Help Center URL has been changed to helpcenter.nddprint.com.
To ensure a smooth transition, automatic redirection from the previous URL will remain active until June 30, 2026.
We recommend that you update your bookmarks and saved links to the new URL.
NDD Print MF Epson 5.9.0
Released on 15 January
New features
Integration with Azure AD / Microsoft Entra ID domains
What is the new feature? This is the native integration between Microsoft Entra ID domains and the NDD Print suite of solutions for Epson devices. This update allows users to log in to Epson devices embedded with NDD Print Client using their Azure AD corporate credentials.
What is the benefit of the new feature? The integration modernises identity management, offering more secure, simplified and fluid authentication. By unifying login with the Microsoft ecosystem, password complexity is reduced and aligned with cloud security best practices.
How does the new feature work? Authentication takes place directly on the printer panel, following this flow:
-
Access Methods: The user can identify themselves using a PIN or Card.
-
Practical Association via QR Code: If the credentials are not yet linked, the panel will display a QR Code. The user scans it with their mobile device to quickly associate their PIN or Card with their Microsoft Entra ID account.
Observations?
-
Centralised Configuration: All integration with cloud domains is now performed through the NDD Print Portal 360 module, replacing the need for NDD Print Host for this specific scenario.
-
On-Premises Domains: For environments that use local domains (traditional Active Directory), the configuration procedures via NDD Print Host remain unchanged.
NDD Print MF HP - 5.31.2
Released on 08 January 2026
Fixes
Accounting loss causing reported data discrepancies
How did the problem happen? On new or recently reset printers, the application started searching for jobs via OXPD before the Statistics service (required for accounting) was properly registered and accessible. This caused errors in the process and data discrepancies.
When did the problem ? When configuring new equipment in NDD Print MF HP or after a Hard Reset, before the statistics service stabilised.
Where did the problem happen? In the accounting service
What was done to fix it? The initialisation order was adjusted to ensure that the Statistics service is responding and fully operational before the system attempts to search for any print jobs.
NDD Print MF HP does not generate .NPL files
How did the problem happen? During the ‘Pending Addition’ process, the system performs a preventive backup of the printer settings. If the addition failed or the service was restarted, the backup was used, but it did not contain the MacAddress information, generating incomplete data.
When did the problem ? When generating NPL files.
Where did the problem happen? In the accounting service, specifically when the system attempted to process printers that had been restored via backup without the physical address (MAC).
What was done to fix it? The backup routine was adjusted to ensure that the MacAddress is included and preserved throughout the printer's security cycle.