Release Notes

Introduction 

This release notes offer brief, high-level descriptions of the new features of HaloSHARE GenNXT. We recommend reviewing these release notes before installing HaloSHARE GenNXT to understand any current limitations or bugs affecting this version of the software. 

Product Description

HaloSHARE GenNXT secures internal and external business workflows by providing centralized bulk file protection, including classification, sensitivity labeling, encryption, password-based access control, digital signing, Controlled Unclassified Information (CUI) marking, and watermarking.

HaloSHARE GenNXT extends Microsoft Purview Information Protection (MPIP) to CAD, Microsoft Office, and non-Office file formats, including text and PDF files stored in shared folders. It protects sensitive data by applying customizable sensitivity labels that support tracking, revocation, and expiration.

System Requirements

The following table of system requirements specifies the minimum and recommended technical specifications, including software and network resources, required to run the product.

Requirements

Recommended URLs, Addresses, and Ports for MPIP

MIP SDK does not support the use of authenticated proxies. So, make sure you set the Microsoft 365 service endpoints to bypass the proxy. View a list of endpoints in the Microsoft Online Documentation. However, Microsoft recommends the following:

Recommended endpoints

Sovereign cloud: For Microsoft 365 U.S. Government GCC High and DoD environments, configure the required Microsoft service endpoints. For endpoint details, see Microsoft 365 U.S. Government GCC High endpoints.

Secude License Manager

To communicate with Secude License Manager, the following URL and port must be whitelisted in the customer's proxy:

Recommended license manager endpoint

Code Quality and Security

Secude focuses on software quality and security. This is accomplished by adhering to and exceeding best practices in development, testing, and quality control. Secude has chosen SonarQube as the first building block for building and implementing a robust continuous code quality assurance (QA). SonarQube is a platform for static code analysis for continuous inspection of code quality. It performs automatic reviews of code to detect bugs, code smells, unit test coverage, and security issues in 29 programming languages.

SonarQube is utilized throughout the development process at Secude, and only the highest marks are accepted for a product to be released. It helps to regulate code quality from the beginning of development, find and repair issues promptly, and improve overall software stability.

Each build report can be found under its relevant version heading in this release notes.

Reliability Rating 

1. A = 0 Bugs

2. B = at least 1 Minor Bug

3. C = at least 1 Major Bug

4. D = at least 1 Critical Bug

5. E = at least 1 Blocker Bug

Security Rating

1. A = 0 Vulnerabilities

2. B = at least 1 Minor Vulnerability

3. C = at least 1 Major Vulnerability

4. D = at least 1 Critical Vulnerability

5. E = at least 1 Blocker Vulnerability

Security Review Rating 

The Security Review Rating is a letter grade based on the percentage of Reviewed (Fixed or Safe) Security Hotspots.

1. A = >= 80%

2. B = >= 70% and <80%

3. C = >= 50% and <70%

4. D = >= 30% and <50%

5. E = < 30%

Maintainability Rating 

A=0-0.05, B=0.06-0.1, C=0.11-0.20, D=0.21-0.5, E=0.51-1

The Maintainability Rating scale can be alternatively stated by saying that if the outstanding remediation cost is:

1. <=5% of the time that has already gone into the application, the rating is A

2. Between 6 to 10%, the rating is a B

3. Between 11 to 20%, the rating is a C

4. Between 21 to 50%, the rating is a D

5. Anything over 50% is an E

Build 1.1

This chapter provides an overview of the updates and quality insights included in this release. It covers the fixed issues, improvements, limitations, new features, and known issues, along with a summary of SonarQube’s key parameters to highlight code quality metrics and analysis results.

New Features

There are no new features to highlight in this release.

Improvements

This section lists improvements added to the current release.

1. Added backward compatibility support for active HaloSHARE GenNXT users to ensure that configuration files from previous versions are supported. HSHAREGNXT-4

2. Improved watermarking failure handling to prevent repeated LicenseSpring API calls for unsupported or failed files. Failed files are now tracked using file hashes and skipped from watermarking if previously identified as failed. This enhancement currently applies to Office and PDF files and can be extended to additional file types in future releases. HSHAREGNXT-102

3. Placed an eye icon in the Password, Client ID, and Client Secret fields to allow users to view the entered characters. HSHAREGNXT-105

4. Added support for password protection for PDF files. HSHAREGNXT-107

5. Added functionality to automatically delete files from the configured Autodesk Forma source folder after processing when the "Delete file(s) from Autodesk Forma source folder after processing" option is enabled. HSHAREGNXT-112

6. Enhanced Microsoft Excel watermarking to support configurable watermark display modes by using registry settings. Users can now display watermarks in either the worksheet header or background, allowing worksheet content to remain editable.

   • header – Displays the watermark in the worksheet header. The watermark is visible only in Page Layout view and on printed pages.

   • bkground – Displays the watermark as the worksheet background. The watermark is visible throughout the worksheet while allowing users to edit worksheet content. By design, Excel worksheet background watermarks are not included when printing. HSHAREGNXT-119

7. Added support for the EDRW file type. HSHAREGNXT-142

8. Updated the installer to support Revit 2027 watermarking. HSHAREGNXT-143, HSHAREGNXT-145

Limitations

This section lists the limitations of the current release.

1. A digitally signed PDF cannot be encrypted. This is due to a limitation: the MIP SDK does not support signed PDF encryption. Thus, HaloSHARE applies watermark visuals to a file when it is no longer eligible for encryption via the MIP SDK.

2. HaloSHARE GenNXT does not support watermarking for password-protected or MPIP-protected file types. For example, an XLSX workbook with a protected sheet, or a PDF, is password-protected.

3. If already protected files are placed in the source folder for watermark-only tasks, processing fails. The failed files (.docx,.xlsx, .pdf, .pptx) are cached and are not moved to the destination folder.

4. By default, HaloSHARE GenNXT-watermarked text appears diagonally on a file; however, the Revit application does not support diagonal watermarking, so the watermark is displayed horizontally.

5. HaloSHARE GenNXT supports watermarking in CAD applications; however, because CAD applications do not have a built-in watermark feature, the watermark text is visible only when a CAD add-on like HaloCAD is used. In this case, we recommend installing the HaloCAD Add-on on a separate system that is not running HaloSHARE GenNXT.

6. Many enterprises enforce a Group Policy Objects (GPO) that requires all outbound internet traffic routed through a proxy server. These proxy settings must be used by both the MIP SDK and the MSAL library for MPIP authentication and functionality. To use proxy settings for the MSAL library, we need to set the msal_proxy_address in HKEY_LOCAL_MACHINE\SOFTWARE\Secude\HaloSHARE.
   If the above does not work for service-running users, in such cases, set the registry keys ProxyServer and ProxyEnable in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings. For more information, refer to the Proxy Configuration section of the Installation and Configuration Manual.

7. CUI marking behavior: Currently, CUI marking is updated in the file only when the CUI marking feature is enabled in the license. However, CUI marking values may still appear in the file’s custom properties even if the feature is not enabled. This is the current behavior and will be addressed in the next release.

8. In existing Default and Background modes: If the Excel worksheet already contains a background image, watermarking is skipped to avoid replacing the existing background.

9. In existing Header mode: If the Excel worksheet already contains a header or footer, watermarking is skipped to avoid modifying the existing header or footer.

10. Silent installation is not supported in this release.

Fixed Issues

This section provides a list of the fixed issues in the current release.

1. Fixed an issue where the calendar pop-up remained open when clicking outside the date picker in the HaloSHARE GenNXT Configuration UI. HSHAREGNXT-46

2. Fixed an issue where the CUI marking text was displayed in the center of the slide instead of in the corner. HSHAREGNXT-95

3. Fixed an issue where files uploaded into Autodesk Forma with protection became corrupted, or their content was inaccessible after upload. HSHAREGNXT-109

4. Fixed an issue where the incorrect error message, "Installation failed.", was displayed when HaloSHARE GenNXT Setup.exe was clicked multiple times. HSHAREGNXT-114

5. Fixed an issue where files were intermittently not moved to the configured destination folder when HaloSHARE GenNXT was configured with Autodesk Forma. HSHAREGNXT-115

6. Fixed an issue where configured file types were not filtered correctly when searching in the File Extensions field. HSHAREGNXT-116

7. Fixed an issue where Autodesk Forma values were not updated after modifying the Client ID and Client secret values in the HaloSHARE GenNXT Configuration window. HSHAREGNXT-124

8. Fixed an issue where the hsmetadataMessageProcessor.exe file was missing from the Secude common folder after AutoCAD 2027 was installed. HSHAREGNXT-125

9. Fixed an issue where the workflow was saved successfully even when the same path was specified for both the source and destination folders. HSHAREGNXT-128

10. Fixed an issue where the HaloSHARE GenNXT pop-up appeared multiple times after entering an invalid value in the Folder Path field when a supplier was already configured. HSHAREGNXT-132

11. Fixed an issue where the Delete files from source folder checkbox was enabled by default even when the Source Folder checkbox was not selected. HSHAREGNXT-141

12. Fixed an issue where a file was moved to the destination folder even when relabeling or decryption failed because the current user was neither the file author nor a super user. The file now remains in the source folder when permission is denied. If no author is specified, the service acts as the author and relabeling or decryption succeeds. HSHAREGNXT-137

13. Fixed an issue where DWG files were not moved to the destination folder when the file name contained the special character = (equal sign) and only watermarking was configured. HSHAREGNXT-140

14. Fixed an issue where the Delete files from source folder checkbox was enabled by default even when the Source Folder checkbox was not selected. HSHAREGNXT-141

15. Fixed an issue where the getvaultWM command did not display certificate details. HSHAREGNXT-144

16. Fixed an issue where files configured with LabelOnly (Without Destination Replication) were relabeled after being successfully labeled for the first time, resulting in redundant relabeling attempts and an MPIP error. HSHAREGNXT-146

17. Fixed an issue where logs were not updated correctly for file names in other languages, and failed files were not cached to prevent repeated license consumption. HSHAREGNXT-148

Known Issues

This section provides a list of the fixed issues in the current release.

A password-protected PDF file protected by HaloSHARE cannot be opened in Microsoft Edge, even when the correct password is entered. Since HaloSHARE applies only the Owner Password, Edge's built-in PDF viewer does not support this protection behavior as expected. Edge prompts for a password when opening the file rather than only when attempting to edit it. This is the default behavior of Microsoft Edge and cannot be changed by HaloSHARE. HSHAREGNXT-126

Quality Gate Report

Please see the table below for a list of SonarQube's key parameters for this version. Refer to the "Code Quality and Security" section for more information on rating definitions.

Quality Gate report

Last updated: October 26, 2026