CapaInstaller 6.7.109 has been released, and it should not be treated as a regular maintenance release.
Most IT departments collect maintenance releases and apply them in the next scheduled window. That is a sensible routine, and it holds in most cases. This one is an exception — not because operations are at risk, but because the waiting time is the one variable you control.
Why CapaInstaller 6.7.109 Should Not Wait for the Next Window
The release addresses identified security issues that, under certain circumstances, could increase the risk of unauthorized access to or misuse of the system.
This is not a critical operational situation. Nor is it a regular maintenance release, and the two should not be handled the same way.
Our recommendation is therefore specific: carry out the update earlier than you normally would.
How We Work With Security
At CapaSystems, security is an integrated part of product development.
We prioritize fast handling of identified security issues in order to deliver a stable and secure product to our customers. When a release should be installed sooner than usual, we say so directly rather than letting it pass unnoticed in a list of fixes.
Better Windows Deployment
Beyond the security fixes, CapaInstaller now follows Microsoft’s recommended setup when Windows is deployed to UEFI-based devices.
This results in more robust installations, better support for Secure Boot and BitLocker, and a setup prepared for future Windows updates.
The release also fixes an issue with how package status was displayed.
How to Update
The full changelog is available in the documentation.
If you have questions about the update in your environment, you are welcome to write to support.