Fixes and Improvements
Terminals, User Interfaces
On Sharp devices running OSA 5.5 or newer, signed-in users were able to open the printer's Web UI authentication settings and disable the SafeQ authentication app. Access to these settings is now correctly restricted to administrators, while behavior on older Sharp devices remains unchanged. (SBT-5252)
Fixed inconsistent behavior of the "Install" button in the management interface, which did not always trigger an installation action depending on context. (SBT-5481)
Installation and Administration
Switched the bundled Java package from JRE back to a full JDK. This restores jconsole and other diagnostic tooling on Spooler Controllers. (SBT-5352)
Resolved an issue where terminal installations could remain stuck in the Scheduled state on servers using timezones such as Europe/Kyiv. (SBT-5430)
The silent installer now performs a backup by default during updates, providing automatic rollback safety without requiring additional parameters. (SQC-8771)
Silent installer can now perform a restore operation, allowing administrators to recover a server from a previously created backup in unattended scenarios. (SQC-8775)
Updated the bundled ObjectDB license; the new license is valid through April/May 2027. (SQC-8774)
Printing
Fixed an issue where the print spooler could hang when multiple versions of Ghostscript were installed on the same system. Printing now proceeds reliably regardless of how many Ghostscript versions are present. (SBT-5125)
Resolved a problem introduced in Build 112 where OCR scanning could fail after a server update. Scan-to-OCR workflows now work reliably again. (SBT-5399)
Fixed an issue where print jobs containing special characters (such as &) in the document name — most commonly seen when printing from Chrome — could fail to print. These jobs are now handled correctly. (SBT-5484)
Payment system
Fixed an issue introduced in Build 116 where payment gateway plug-ins (such as PayPal) could not be connected, and gateway creation failed with the error "Plug-in for payment gateway could not be reached." Payment gateway plug-ins now connect and operate as expected. (SBT-5379)
Resolved an issue where return links generated by the payment system used http:// instead of https://, which could cause the return step of an electronic payment to fail in customer environments that enforce HTTPS. Return links now correctly preserve the secure connection used by the original request. (SBT-5401)
Security Mitigation and Enhancements
Security improvements and fixes (SBT-4999, SBT-5410, SBT-5422, SBT-5426, SBT-5459, SBT-5491)
Product extensions (or customizations)
Customers who use YSoft SafeQ extensions or customizations should contact their Y Soft RSM or Customer Support Services for compatibility verification with the new Build. We recommend testing all extensions before applying a Build update into a production environment.You can find additional information on Partner Portal: https://portal.ysoft.com/products/ysoft-safeq/extension-store/print-job-extension