Upgrade to VeeamBR 12.3.2.4165_20251006 failing

[AlexLeadingEdge]

I've mounted the ISO as normal, it asks me if I want to Modify, I say yes, then it throws up this error message:



I'm also seeing the same with the latest Veeam Agent (VeeamAgentWindows_6.3.2.1302):



Why is it not upgrading? Am I missing something???

//edit: I forgot to mention I'm upgrading from VeeamBR 12.3.2.3617

[SAFA_IT]

I had the same issue with the full iso. Using the much smaller patch iso worked.
https://www.veeam.com/kb4696

[Gostev]

We should change that error to "Failed to read documentation"

[AlexLeadingEdge]

I'm not alone, because I just got this sent to me asking me how they're supposed to click on the link since it is outside of the window.



LALALALA ???

[AlexLeadingEdge]

And another...

[AlexLeadingEdge]

We should change that error to "Failed to read documentation"

Ok, I'll give you that, I assumed that since it has always worked that way it would work again this time, but you know what they say about people who assume...

[Gostev]

I'm not alone, because I just got this sent to me asking me how they're supposed to click on the link since it is outside of the window.
LALALALA ???

Looks like the web team has erroneously published a template file instead of the actual prod file. This should have been removed by now.

And another...

That's expected, you can't do an in-place upgrade of standalone/free agents with this security patch. This has been already discussed in the corresponding forum.

Ok, I'll give you that, I assumed that since it has always worked that way it would work again this time, but you know what they say about people who assume...

Fair, we will try to make it work in future so that full ISO can patch the same release version. The MSI framework doesn't support that (the error you get is a standard Windows error) but perhaps we could detect this situation and run patch EXE instead.

[AlexLeadingEdge]

Thanks Anton.

[FCU_JE]

We should change that error to "Failed to read documentation"

I take issue with the flippant attitude behind this comment specifically as it pertains to the VA4W. Customers/users need to dig for the relevant KB where this is documented. In no other context would I expect as a user of any other well-published software to need to install a specific patch rather than being able to simply do an in-place upgrade/update to the latest build.

These patch instructions for existing users is also not noted in the KB that was shared with customers in the security bulletin.

I received this link in the security bulletin: https://www.veeam.com/kb4771

That KB provides two "paths" to the VA4W software updates - https://www.veeam.com/kb4696 and https://www.veeam.com/kb2683

The former KB isn't really relevant to the VA4W issue (for standalone/pre-installed agents), but is otherwise well-written. The latter is simply a link to the build history for the VA4W and ultimately leads users down a path for the full installer and *not* the private fix/patch or the instructions in https://www.veeam.com/kb4778

Please do better. I want Veeam to continue to be a great company but this dismissive attitude - even if meant in jest - sends the wrong message.