Comprehensive data protection for all workloads
Post Reply
satyaibm007
Service Provider
Posts: 5
Liked: never
Joined: Feb 27, 2025 12:29 pm
Full Name: Satyabrata Roy
Contact:

[False "Component Update" Prompt on First Console Launch After VBR 12.3.2 Newly Deployed] Case #08023789

Post by satyaibm007 »

Subject: False "Component Upgrade" Prompt on First Console Launch After VBR 12.3.2 Newly Deployed

Hi everyone,
We are currently experiencing an unexpected behavior when upgrading Veeam Backup & Replication within the 12.3.2 branch.

The Issue:
Immediately following a successful VBR upgrade, launching the Veeam console for the first time triggers a "Component Upgrade" wizard. However, the components it is asking to upgrade have already been processed during the main installation.

This behavior consistently occurs across two different upgrade paths we have tested:

12.3.2.3617 -> 12.3.2.4165
12.3.2.4165 -> 12.3.2.4465

Media Used:
VeeamBackup&Replication_12.3.2.4165_20251014.iso
VeeamBackup&Replication_12.3.2.4465_20260307.iso

(Note: Supporting screenshots of the component upgrade are added in Case #08023789).
satyaibm007
Service Provider
Posts: 5
Liked: never
Joined: Feb 27, 2025 12:29 pm
Full Name: Satyabrata Roy
Contact:

Re: [Issue while new Deployment 12.3.2.4465] Case #08023789

Post by satyaibm007 »

FYI,

Subject should be "False "Component Update" Prompt on First Console Launch After VBR 12.3.2 Newly Deployed"
david.domask
Product Manager
Posts: 3618
Liked: 876 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: [Issue while new Deployment 12.3.2.4465] Case #08023789

Post by david.domask »

Hi satyaibm007,

I tested and saw the same in my lab, allow me some time to check on this, I don't recall that this is expected, but allow me time to check this internally.
David Domask | Product Management: Principal Analyst
david.domask
Product Manager
Posts: 3618
Liked: 876 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: [False "Component Update" Prompt on First Console Launch After VBR 12.3.2 Newly Deployed] Case #08023789

Post by david.domask »

Discussed internally, for this patch it's expected, there is a nuance on how the patch is applied which resulted in the update wizard being prompted, but it was indeed a "false" prompt, and clicking through the update wizard resolved the nuance.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Semrush [Bot] and 476 guests