invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive Optimizer

Release Note - Installer

Invantive Optimizer 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.

  • 2 enhancements
  • 2 bug fixes
  • 0 things to check before upgrading

Before You Upgrade

Nothing to check is recorded for this step.

Top 4 Changes

  1. Allow file names longer than 260 characters on Windows
    • Enhancement
    • On Windows devices that allow it, the Optimizer can now handle paths longer than 260 characters.
  2. Prevent the Optimizer from hanging while it waits for the output of the optimisation tool
    • Bug Fix
    • The Optimizer read the standard output of the optimisation tool to the end before it started reading the error output. When the tool wrote a lot to the error output, both programs waited for each other. Both outputs are now read at the same time.
  3. Report start-up failures and unhandled errors to the user
    • Bug Fix
    • Start-up failures, such as too little free space or an unknown command line option, only ended the program with exit code -1 and no message. Unexpected errors in the windows showed the untranslated standard dialog of .NET. Both are now reported in a message box and recorded in the trace.
  4. Send the usage event of the Optimizer to the .eu domain of Customer Service
    • Enhancement
    • The Optimizer now reports its usage event to the invantive.eu domain instead of invantive.com. Administrators who restrict outgoing traffic by domain may need to allow the new address.

All Enhancements

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

0 of 4 shown.

None.

All Bug Fixes

Defects of the older release that are repaired.

None.

What It Builds On

Kind Name From To
invantive component Invantive Optimizer 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.
  • 4 links between a change and a source commit are recorded.