Feature Request: Enhanced Installer Diagnostics and Dependency Transparency for VBR Upgrades

[Marcin4385794]

am writing to submit a formal feature request regarding the Veeam Backup & Replication installer logic, specifically concerning the upgrade process (e.g., from v12 to v13).

Currently, the installer often fails with cryptic, non-actionable errors such as: "This product is only valid for the installed product." This message provides zero clinical value to the administrator. Even after remote sessions with two Veeam technicians, we were unable to identify the root cause because the software does not explicitly state what it is looking for.

Requested Improvements:

Detailed Dependency Logging: If the installer detects a version mismatch or a missing component (e.g., a specific plugin version), the logs must explicitly state the name and expected version of that component.

Actionable Error Dialogs: Instead of terminating the installation with an unidentified error, the installer should provide a "Browse" option. If a file or MSI is missing from the local package cache, the user should be able to point the installer to the original ISO or a specific path to resolve the dependency manually.

Pre-Upgrade Validation Tool: Implement a more robust pre-install check that generates a clear report of "Ready," "Missing," or "Corrupt" components before the actual upgrade process begins.

The Current Issue:
The "clean install" or "reinstall Windows" recommendation is not an acceptable solution for enterprise environments where root cause analysis is required. We need the software to communicate its requirements clearly—if a file is missing, tell us which one; if a plugin is incompatible, name it.

I hope to see these transparency improvements in future builds to reduce downtime and the burden on both customers and your support teams.

[david.domask]

Hi Marcin4385794, welcome to the forums.

Very sorry to hear about the challenges with the upgrade process, and sure we can consider some of these requests. The initial error you mentioned is a Windows error ("This product is only valid for the installed product"), and it's typically not about dependencies so much as difficulties with the installed application. Unfortunately I cannot be more specific than this as the error can be triggered in many situations.

Can you please share your case numbers you mentioned? It will help us to understand the nature of the issues you faced and we can try smooth out these rough edges a bit.

[Marcin4385794]

sure, Support ID: #08051035

[Moderator: Replaced Support Id with Case Id]

[Marcin4385794]

well, if you self can't fix it I want to see in logs all this triggered malfunction. Error with info: doesn't work because doesnt' work is very unprofesionel.

[david.domask]

Thank you for sharing the case number; from the case notes, it looks like an issue with the backup server operating system was identified.

We will discuss internally on what can be done to make these errors more meaningful / provide better guidance on such issues especially when the operating system errors that appear are less than useful.