invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive Support Assistant

Release Note - Installer

Invantive Support Assistant 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.92 09-11-2026 latest build of release 27.0 at the time of writing

The older state is the first build of release 26.0, not its last: later builds of 26.0 received ports of changes made for 27.0, so those changes are part of this step. The 27.0 line also contains the beta builds 26.1.x.

  • 26 enhancements
  • 14 bug fixes
  • 0 things to check before upgrading

Before You Upgrade

Nothing to check is recorded for this step.

Top 25 Changes

  1. Settings files move from XML to JSON
    • Enhancement
    • A settings file in XML is converted to JSON when it is read. The user and installation settings, the cached list of databases and the databases of the user are also written in JSON, through an atomic write, and a damaged XML file is recovered where possible. From 27.0 the JSON file takes precedence; the XML file is still written for older releases on the same workstation and is planned to disappear.
  2. Invantive License Service: clearer messages, grace period and new modules
    • Enhancement
    • A licence key of the wrong type is explained, a licence service that is unavailable gets a specific message, and a licence that was valid stays in force for a grace period when the service cannot be reached. The check that prolongs a licence runs hourly. New licence modules exist for the Support Assistant, OEM use and subscription software, the built-in trial and open data keys use the new format, and text-mode products show tips about the licence in use.
  3. Data containers and credentials from Invantive Credentials Server
    • Enhancement
    • A database definition can point to Invantive Credentials Server, which supplies the data containers and sign-in credentials. The log-on window and the partition menu show these containers with their own icon, errors of the server are shown with their details, and a retrieval is repeated after a time-out.
  4. Licence keys can be supplied through environment variables
    • Enhancement
    • A licence key can be given in the environment variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY, also with surrounding text or line breaks. This helps with unattended starts, for example in scripts and containers.
  5. Sensitive values are masked in traces, error data and OAuth logs
    • Enhancement
    • Passwords, secrets, tokens, API keys, cookies, authorisation headers and one-time codes are no longer written in clear text in traces, exception data and the log text of OAuth calls.
  6. The keychain and settings files are written safely
    • Enhancement
    • The keychain and settings files hold either the old or the new contents, also after a crash or a full disk, are guarded with a file lock when two programs use them, are written less often and open faster.
  7. File names longer than 260 characters work on Windows
    • Enhancement
    • Where Windows allows it, file and folder paths up to 32,767 characters are accepted. The setup program declares support for long paths and the trace shows whether they work.
  8. Links to documentation, forums and support use the invantive.eu address
    • Enhancement
    • Help links, the splash screen, the default address of Customer Service and the links of data sources point to the invantive.eu domain.
  9. Close Support Assistant faster after its window has closed
    • Enhancement
    • Support Assistant no longer waits up to 35 seconds after the window has closed for messages to Invantive Customer Service to be sent. The messages are queued and sent during the exit, within one fixed time limit.
  10. Remove a configuration section that .NET 10 rejects from Support Assistant
    • Bug Fix
    • The application settings contained a section that only the .NET Framework knows. On .NET 10 it made the configuration system fail with an unrecognised section the first time a setting was read. The section is now disabled.
  11. UTF-8 files are written without a byte order mark by default
    • Enhancement
    • Exports, trace files, plug-in files and the input and output of operating system commands are written as UTF-8 without a byte order mark unless one is asked for.
  12. XML from outside is no longer allowed to load external entities
    • Bug Fix
    • Processing XML from external services, XSLT transformations and the XML of an RSA key no longer resolves DTDs or external entities.
  13. Zstandard compression for trace files, caches and SQL functions
    • Enhancement
    • Trace files, persistent caches, saved result sets and the disk cache of web answers are compressed with Zstandard, which is faster than gzip at a similar size. Two SQL functions compress and decompress with Zstandard, and a text file with gzip or Zstandard content is read as plain text.
  14. More diagnostics: message codes, trace detail and monitoring
    • Enhancement
    • More failures have their own message code, trace records carry a severity name, spans with standard trace identifiers and an OpenAPI description, the trace shows memory and processors including container limits, and a failure to load an assembly is explained. A trace level below debug can be switched on separately.
  15. Show the usage when Support Assistant is started with a help option
    • Enhancement
    • Support Assistant now shows a short description of its command line when it is started with a help option, instead of starting the analysis window. It also accepts an option to run in the context of an AI agent. The usage text is translated.
  16. Statistics show memory and CPU time per statement
    • Enhancement
    • The statistics of a statement include the heap allocations and the CPU time of its threads.
  17. Separate folders for environment files, the keychain, databases and traces
    • Enhancement
    • The folders for environment files and for the Invantive Keychain can be set through environment variables, database definitions live in a sub-folder of the configuration folder, and traces go to a Trace folder there by default; the folder is created when missing.
  18. Open the current online documentation, forums and release notes from Support Assistant
    • Enhancement
    • The help, forums and release notes buttons of Support Assistant open the current sites of Invantive. Help no longer opens the documentation of release 2017 R2, and the forums and release notes moved to the .eu domain.
  19. Sample configuration files are written with documentation of every setting
    • Enhancement
    • The product can write sample configuration files that list every setting with its description, default and example. The folder can be chosen with an environment variable.
  20. Access to the local file system can be blocked in shared environments
    • Enhancement
    • On shared multi-user environments, statements that read or write local files are refused with a clear error, and a file name from outside cannot leave its folder. A single workstation, such as Query Tool, is not affected.
  21. Configuration errors point to the documentation of the setting
    • Enhancement
    • An error about an invalid configuration value now includes a hint that comes from the documentation of the setting.
  22. Store databases and trace files in sub-folders of the configuration folder
    • Enhancement
    • Support Assistant now keeps its settings files in a Databases sub-folder and its trace files in a Trace sub-folder of the configuration folder. Before, settings were in the folder of the profile itself and trace files in the temporary folder of Windows.
  23. A stack overflow while logging at start-up is prevented
    • Bug Fix
    • Asking for information about the process while that information was being collected could repeat itself until the program stopped. The collection is now protected against re-entry.
  24. Email addresses are accepted when the validation service does not answer
    • Enhancement
    • When Customer Service cannot validate an email address, because it fails or does not answer, the address is accepted as entered and the situation is traced. An invalid address reported by the service is still refused.
  25. Fix a null initialisation error at start-up in the dependency helpers
    • Bug Fix
    • Internal helpers could be used before their global state had been created, which gave a null error during start-up. The state is now created on first use.

All Enhancements

Changes to behaviour, platforms, drivers and settings, grouped by area.

Installation and platform

Settings files move from XML to JSON

A settings file in XML is converted to JSON when it is read. The user and installation settings, the cached list of databases and the databases of the user are also written in JSON, through an atomic write, and a damaged XML file is recovered where possible. From 27.0 the JSON file takes precedence; the XML file is still written for older releases on the same workstation and is planned to disappear.

  • importance 5
File names longer than 260 characters work on Windows

Where Windows allows it, file and folder paths up to 32,767 characters are accepted. The setup program declares support for long paths and the trace shows whether they work.

  • importance 3
The keychain and settings files are written safely

The keychain and settings files hold either the old or the new contents, also after a crash or a full disk, are guarded with a file lock when two programs use them, are written less often and open faster.

  • importance 3
Configuration errors point to the documentation of the setting

An error about an invalid configuration value now includes a hint that comes from the documentation of the setting.

  • importance 2
Sample configuration files are written with documentation of every setting

The product can write sample configuration files that list every setting with its description, default and example. The folder can be chosen with an environment variable.

  • importance 2
Separate folders for environment files, the keychain, databases and traces

The folders for environment files and for the Invantive Keychain can be set through environment variables, database definitions live in a sub-folder of the configuration folder, and traces go to a Trace folder there by default; the folder is created when missing.

  • importance 2
Show the usage when Support Assistant is started with a help option

Support Assistant now shows a short description of its command line when it is started with a help option, instead of starting the analysis window. It also accepts an option to run in the context of an AI agent. The usage text is translated.

  • importance 2
Store databases and trace files in sub-folders of the configuration folder

Support Assistant now keeps its settings files in a Databases sub-folder and its trace files in a Trace sub-folder of the configuration folder. Before, settings were in the folder of the profile itself and trace files in the temporary folder of Windows.

  • importance 2
Support file names longer than 260 characters in Support Assistant

Support Assistant declares support for long file names on Windows, so paths of more than 260 characters can be used where Windows allows it.

  • importance 2

Licensing and sign-in

Data containers and credentials from Invantive Credentials Server

A database definition can point to Invantive Credentials Server, which supplies the data containers and sign-in credentials. The log-on window and the partition menu show these containers with their own icon, errors of the server are shown with their details, and a retrieval is repeated after a time-out.

  • importance 4

Invantive Credentials Server, Concept of Invantive Credentials Server

Invantive License Service: clearer messages, grace period and new modules

A licence key of the wrong type is explained, a licence service that is unavailable gets a specific message, and a licence that was valid stays in force for a grace period when the service cannot be reached. The check that prolongs a licence runs hourly. New licence modules exist for the Support Assistant, OEM use and subscription software, the built-in trial and open data keys use the new format, and text-mode products show tips about the licence in use.

  • importance 4

License Service

Licence keys can be supplied through environment variables

A licence key can be given in the environment variables INVANTIVE_LIC_KEY and INVANTIVE_LICX_KEY, also with surrounding text or line breaks. This helps with unattended starts, for example in scripts and containers.

  • importance 3

Environment variables

Email addresses are accepted when the validation service does not answer

When Customer Service cannot validate an email address, because it fails or does not answer, the address is accepted as entered and the situation is traced. An invalid address reported by the service is still refused.

  • importance 2

Security

Sensitive values are masked in traces, error data and OAuth logs

Passwords, secrets, tokens, API keys, cookies, authorisation headers and one-time codes are no longer written in clear text in traces, exception data and the log text of OAuth calls.

  • importance 3
Access to the local file system can be blocked in shared environments

On shared multi-user environments, statements that read or write local files are refused with a clear error, and a file name from outside cannot leave its folder. A single workstation, such as Query Tool, is not affected.

  • importance 2
IP address ranges in CIDR notation support IPv6

A range such as 192.168.0.0/16 or one with IPv6 addresses is now matched against IPv4 and IPv6 addresses in both notations. A range with an invalid address or prefix matches nothing.

  • importance 2
Mail domain proguidex.com is blocked

Email addresses at the domain proguidex.com are refused.

  • importance 1

Query Tool user interface

Replace the keychain icon and the splash screen

The keychain icon and the splash screen of Support Assistant have been replaced.

  • importance 1
Report unexpected errors in Windows Forms controls in a window of the product

An unexpected error in a Windows Forms control that Support Assistant uses through a library is now shown once in a window of the product. Before, .NET showed its untranslated dialog.

  • importance 1

Export and import

UTF-8 files are written without a byte order mark by default

Exports, trace files, plug-in files and the input and output of operating system commands are written as UTF-8 without a byte order mark unless one is asked for.

  • importance 3

Performance

Close Support Assistant faster after its window has closed

Support Assistant no longer waits up to 35 seconds after the window has closed for messages to Invantive Customer Service to be sent. The messages are queued and sent during the exit, within one fixed time limit.

  • importance 3
Zstandard compression for trace files, caches and SQL functions

Trace files, persistent caches, saved result sets and the disk cache of web answers are compressed with Zstandard, which is faster than gzip at a similar size. Two SQL functions compress and decompress with Zstandard, and a text file with gzip or Zstandard content is read as plain text.

  • importance 3

Logging and diagnostics

More diagnostics: message codes, trace detail and monitoring

More failures have their own message code, trace records carry a severity name, spans with standard trace identifiers and an OpenAPI description, the trace shows memory and processors including container limits, and a failure to load an assembly is explained. A trace level below debug can be switched on separately.

  • importance 2
Statistics show memory and CPU time per statement

The statistics of a statement include the heap allocations and the CPU time of its threads.

  • importance 2

Documentation

Help links, the splash screen, the default address of Customer Service and the links of data sources point to the invantive.eu domain.

  • importance 3
Open the current online documentation, forums and release notes from Support Assistant

The help, forums and release notes buttons of Support Assistant open the current sites of Invantive. Help no longer opens the documentation of release 2017 R2, and the forums and release notes moved to the .eu domain.

  • importance 2

All Bug Fixes

Defects of the older release that are repaired.

Installation and platform

Remove a configuration section that .NET 10 rejects from Support Assistant

The application settings contained a section that only the .NET Framework knows. On .NET 10 it made the configuration system fail with an unrecognised section the first time a setting was read. The section is now disabled.

  • importance 3
Fix a null initialisation error at start-up in the dependency helpers

Internal helpers could be used before their global state had been created, which gave a null error during start-up. The state is now created on first use.

  • importance 2
Make sure the process exits even when the exit registration fails

When registering the exit or the clean-up raised an error, the process did not always end. The process now always exits.

  • importance 2
Avoid a possible hang when reading the installation identifier on Linux and macOS

The command used to read the installation identifier could block when its output filled a buffer. Output and errors are now read at the same time.

  • importance 1

Licensing and sign-in

Fix licence keys that contain line endings of another platform

Line endings in a licence key were removed by looking for two specific characters. This is replaced by a platform-independent removal. Text meant for Windows is now generated with Windows line endings on every platform.

  • importance 1

Security

XML from outside is no longer allowed to load external entities

Processing XML from external services, XSLT transformations and the XML of an RSA key no longer resolves DTDs or external entities.

  • importance 3
Reject malformed encrypted data with a clear error

Decryption of damaged or incomplete encrypted data failed with a null-reference error or named the wrong block in its message. It now rejects the data with a correct error.

  • importance 2

Logging and diagnostics

A stack overflow while logging at start-up is prevented

Asking for information about the process while that information was being collected could repeat itself until the program stopped. The collection is now protected against re-entry.

  • importance 2
Fix a serialisation error in session logging with the dummy driver

Logging a session of the dummy driver failed with error code itgenclr003 because some properties could not be written as XML. These properties are now excluded and the address is written in a separate XML field.

  • importance 2
Trace files no longer fail when the trace folder name is long

A trace folder with a long name made the creation of the trace file fail with a path-too-long error. The folder part of the trace file mask is now determined without checking the full path length.

  • importance 2
Fix lost logging of exceptions raised at the same time on several threads

An exception raised on one thread could be left out of the trace while another thread was still writing a record about an exception. Each thread is now handled on its own.

  • importance 1
Forward the messages printed at the end of an Invantive Data Hub run

Messages produced while Invantive Data Hub was ending were reported as not forwarded. They are now written straight to the trace output once the final flush starts.

  • importance 1
Log a failed dependency injection of Support Assistant when it fails

Support Assistant logged the message that dependency injection failed when it succeeded, and nothing when it failed.

  • importance 1

Other

Release handles of processes after checking for TeamViewer and temporary files

Support Assistant kept operating system handles open when it looked for running processes and ran a helper program. The handles are now released.

  • importance 1

What It Builds On

Kind Name From To
invantive component Invantive Support Assistant 26.0.4 27.0.92
invantive component Invantive(R) Basics 26.0.4 27.0.92
build tool Invantive Deploy 26.0.4 27.0.92
build tool change Installing and upgrading a .NET 10 product no longer runs the NGEN tool per assembly
build tool change Installer shows an error when another installation is already running
build tool change Final installer window shows the version link
build tool change Progress bar of the installer follows the measured duration of the installation stages
build tool change Installer windows flicker less when moving to the next step
build tool change Installer no longer stalls on an unreachable Customer Service and cancels reliably
build tool change Installer explains in a window why installation settings cannot be downloaded
build tool change Maintenance window checks that the product is still installed
build tool change Installer shows unexpected errors in its own window
build tool change Repair Office add-in name, optional email check and installs run as SYSTEM
build tool change Installs run as SYSTEM are attributed to the end user, not to the SYSTEM account
build tool change Each product gets one .NET 10 installer; the .NET Framework installer is no longer built
build tool change Installer includes the files .NET needs to find native libraries such as WebView2
build tool change Installer carries native runtime folders and Catalan, Hungarian and Romanian resources
build tool change Installer no longer includes the crash dump tool
build tool change Supported Windows versions in release information follow mainstream support dates
build tool change Installer writes its trace to the Invantive Trace folder when trace to file is on
build tool change Installer texts for new messages are available in all supported languages
build tool change Installer email step rejects example and test domains
third party summary

More Information

How This Note Was Made

  • For all products together 28 items whose changed lines are 50 to 70 % in the first build of 26.0 and 23 items that a content check would have left out were read against that build; the items that apply to this product are kept or left out on that reading.
  • Range: commits of origin/release-27.0 that are not reachable from the first build of release 26.0 (stamp 26.0.4, per repository). Commits that were ported to later builds of 26.0 are therefore included.
  • For a product that does not offer SQL to its users, items of the shared libraries outside the areas installation, licensing, security and diagnostics, and items about one platform, are left out and counted as internal.
  • The commits are the ones of the range that touch a project of the product; each commit was classified once, for all products, and the items of a product are the items that contain such commits.
  • Version stamp commits of the build pipeline are left out.
  • A change whose changed lines are for 70 % or more already in the first 26.0 build is left out; items between 50 % and 70 % and all such exclusions were checked by reading the code of that build.
  • A bug fix whose repaired lines were written by another commit of the same range is merged into its feature or left out.
  • Texts were written from the commit messages and from the changes themselves; items carry a confidence.
  • 125 links between a change and a source commit are recorded.
  • 3 exclusions are recorded in the audit of the note.