[V13 on Windows] Console notifies about missing updates of VBR, even though latest version is installed

[d.artzen]

Hello together,

I have a strange behavior in the Backup Console and wanted to ask, if anyone else is seeing this. In the Backup Console I get the notification, that the system is missing security updates for VBR13 on the VBR itself. The same is shown under "Backup Infrastructure" - "Managed Servers", where it insists the VBR server is missing a "Security Patch for Veeam Backup & Replication 13". This is a Windows VBR, not the appliance and we also don't have any VIA based components. The console and the webinterface both show version 13.0.1.1071 installed, so the latest available. The webinterface also does not show any update status under "Managed Servers", which is correct since there are no Appliances involved at all. Interestingly enough in the console the only button I can click in the "Missing Updates" Window is "Re-Check", which does not change the status. The automatically generated mailreport also says "no updates".
Since this seems to be a purely cosmetical issue, I have not raised a support case yet, just wanted to know if it is only our system showing this.

Best regards
Daniel

[HannesK]

Hello,
I cannot say whether it's only you (that's why we ask to contact support for technical issues) but I can say that my system does not have that issue.

Best regards
Hannes

[d.artzen]

Hello Hannes,

thanks for your response. I have now opened Case #07951887. Let's see what support finds.

[Gene-MN]

I am seeing the same issue as well.

[d.artzen]

Support is still investigating this in my case and they want to do a remote session, since the logs don't seem to show what they need. Have you also opened a case for this? If not, I would recommend you do so, if only to give them more info to work with.

[d.artzen]

Short update, I had the remote session with support today. The engineer could not find the root cause for this, since everything looks fine and he agrees that there should not be a missing update displayed. He assumes that there is something in the database causing this and he will escalate the case to the DB team.

[melo1983]

I have the same issue. Two days ago i opened a ticket!

[HannesK]

Hello,
can everyone please post ticket numbers so that we can bring them together?

Thanks,
Hannes

[melo1983]

My Case :#07955433

[Gene-MN]

Case #07957687

[d.artzen]

Seems the issue is more complicated to diagnose than I thought.
After I uploaded a database dump I was now asked to upload new logs with Log Level 6 (through a registry entry). @melo1983 and @Gene-MN: Just to satisfy my personal curiosity, how are your cases going? Did support find more in your installation than in mine?

[d.artzen]

I had another remote session with support today. It seems that for some reason the last update did not set a specific entry in the database, so the VBR still thought it was missing this update. Support used a SQL-Query to set this entry directly into the database, which solved the issue.
I just hope that this does not repeat with the next released update.

Best regards
Daniel

[HannesK]

Hello,
it should not come back as bug #1230000 was fixed in the next cumulative update / patch.

Best regards
Hannes

[J3thro]

I have been seeing the same issue on our fresh deployment. In my case we are version 13.0.1.1071 and there is a 13.0.1.2067 available; However, the manual update option is greyed out and Veeam has not installed this update itself after configuring auto updates.

I have currently downloaded the 13.0.1.2067 ISO

1. Mounted it
2. Disabled all of my current backup jobs
3. Running the Patch from the updates folder of the ISO
4. Success

Opened support case #08048929 on April 3rd, 2026 and have not received any communication as of now.

Here is another group trying to learn the process of updating as well veeam-backup-replication-f2/uprage-to-1 ... 02603.html All in all I have not come across information on how patching should be done. As others have mentioned not having the EXE patch in our my.veeam.com portal leading to most of us downloading a 20GB ISO vs 3GB exe is also a pain. Why is there an updates drop down and everything needed to install an update yet it does not work?

[d.artzen]

This is not the same as my issue. In my case the server was up to date and just showed that message, because something in the database was not set correctly by the installation, so VBR thought it was not on the latest version. Support fixed that in our database and it did not reoccur after the update to 13.0.1.2067
Your description does imply that you are not using the VSA, so what you describe is normal behavior, since on Windows the VBR cannot be updated automatically. The install buttons only exist to be used with the Linux appliances, since there Veeam controls the whole system.

Concerning the download and the method for patching: When a new version is released Veeam publishes a KB, which is linked in the Sticky Topic in this forum. There you can find the download links for the patch version and the full ISO, and it is explained from which version you use the patch and where the full ISO. But I agree, it would be better if the patches were also available directly in the download area of the account, like the full ISOs, so the users not active on the forum can easier see these and the instructions which to use. A link to the latest KB would suffice in my opinion.

[HannesK]

Hello,
and welcome to the forums.

I just checked case 08048929 and it's a licensing case and seems to be unrelated to this topic.

not installed this update itself after configuring auto updates.

these update settings apply only to Veeam Infrastructure Appliances that might be connected somehow to your backup server on Windows. Agree, that could be clearer in the settings and not only if one checks the user guide.

Yes, we also plan to make the Windows update experience better. Stay tuned!

Best regards
Hannes