VA4W 6.3.1 - What actually changed?

[FCU_JE]

I love running the latest software, but it's not clear to me what exactly improved in the latest agent version. The sticky thread links to https://helpcenter.veeam.com/rn/veeam_a ... notes.html but that page in the docs doesn't actually described what changed version to version.

I find it ... conspicuous ... that the same day an update for VBR was dropped (which had a high severity security component) that the VA4W (and I assume other) agents got a version update.

[Mildur]

Hello FCU_JE,

Each maintenance release includes fixes for bugs and issues reported through support cases or found in the ongoing internal testing, but we do not list minor fixes in the release notes because there are usually too many to document. Only important fixes are highlighted, such as those that resulted in a significant number of support cases.

For vulnerabilities, it's different and every fixed vulnerability is always documented in the Release Notes.

Backup agents are components of Veeam Backup & Replication and they are always rebuilt along in every new VBR build. In the release notes KB for Veeam Backup & Replication v12.3.1, we noted two changes related to VAW:

Resolved Issues - Agent Management
- Backup agents fail to perform retention processing for backups located on SOBR Capacity Tier extents after the backup chain has been evacuated from a Performance Tier extents running in a direct connection mode.
- Veeam Agent for Windows Recovery Media created from Microsoft Windows Server 2025 or Microsoft Windows 11 24H2 machines in certain configuration states, fails to boot.

Best,
Fabian

[Gostev]

Also you can always see the entire security updates history for VAW in this KB > https://www.veeam.com/kb3108

[FCU_JE]

Hi, Mildur and Gostev

Appreciate the responses. At present, neither of those links is discoverable given the fact that I had to ask here to get more insight.

I'd strongly recommend updating both this sub-forum's sticky + all references to release notes on download pages to include a link to KB3108 - it's such an ""older"" KB number that it's not discoverable to the casual admin.

I'll also point out that some users of VA4W are not integrated with VBR (running it standalone) so only documenting agent bugfixes in the VBR release notes again - is not discoverable.

Regarding the whole logic of not documenting bug fixes, I've been over this before - I forget whether on this forum or on the /r/veeam reddit, but suffice to say even giving us a number like "1337 bugs were fixed in this version" is fine. Just give us something so that when we file our change requests we can more accurately prioritize.

[Gostev]

Personally I'm always looking up this particular KB above by just Googling "veeam agent for windows vulnerabilities" and never even trying to find it any other way as it's been the fastest... so it IS in fact very easily discoverable for anyone looking for the information on "veeam agent for windows vulnerabilities"

Having said that, I think there's no reason not to additionally add it into the sticky @Dima P. ?

[FCU_JE]

Poor response IMO. All I'm saying is to make the official release notes cross reference one another better. If I have to resort to using a search engine to find release notes from something I got a security bulletin for - that's a failure.