Skip to main content
Solved

v13 Appliance daily update check fails but manual update checks work.

  • January 27, 2026
  • 12 comments
  • 164 views

Hello,

I noticed something very peculiar. We use the Infrastructure Appliance v13.0.1.1071 for VMware Proxies and hardened repositories. The Backup Server is a Windows box running same version.

Every night, we get an eMail saying that check for updates was successful for the Windows Backupserver but failed for all the appliances.

When we enable the WebGUI on the appliances and login to their WebGUI’s on port 10433, we go to “Updates” which will say that the last check failed. But when we click on “Check for updates” it works fine. Updates are found, downloaded and installed. All good.

So what’s the difference between the automatic daily checks and clicking on “check for updates” on each appliance? We never see the firewall dropping outbound traffic from the appliances around the time the automated daily update checks are done. And the Veeam backup Server (Windows) is the only one, every day, which has no problems checking for updates.

The fact that manual checks and patch installs work fine on all appliances indicates that DNS, routing and patch-server-on-the-internet-connectivity are all working correctly.

Best answer by Stefke72

@Stefke72  - just wanted to follow up to see if you got an answer to your inquiry?

 

Hello Chris,

Because this is a NFR license, which I generate/fetch from our partner/reseller’s Partner portal account, the correct product is not listed as a product we licensed. Thus it cannot be selected during case creation thus case-creation fails. Picking up the phone and call support is useless as the “iron lady” in the menu says one can only continue with an existing case number. Which we don’t have because we cannot create a case.

This NFR bug is apparently still present in the current 13.1.2067 build (Windows BR Server). I got a mail 2 days ago about all the VSA and VIA appliances saying:
Status: error , Sync: error, Updates: none (which is actually correct as there is no newer build. I updated the Windows BR Server using the Patch ISO which then updated all Appliances automatically.

To answer your question: I was never able to raise a case. Maybe this bug will get solved one day.

12 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 27, 2026

The Windows version when I have tested it does not seem to run the updates on the appliances for some reason.  I know my setup with the VSA for VBR in an HA Cluster does work with the auto updates for all appliances in my infrastructure.  I also change the update settings from the Console only and never set anything on each appliance.  So right now that might be by design and they will address it?  Not sure.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 27, 2026

Read over your post again and unsure why auto checks would fail but manual works.  You may need a support case to get to the bottom of the issue.

My other reply is therefore not related.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • January 27, 2026

Yeah...the fact manual works...routing is working. That sounds like a bug. Support will be your best bet ​@Stefke72 


lukas.k
Forum|alt.badge.img+13
  • Influencer
  • January 28, 2026

I currently experience the same issues in my lab. As already mentioned the best way would be to reach out to Veeam Support to let them investigate.

Hint: Please attach the logs at the time you create the ticket, that saves time.

 

Best

Lukas


  • Author
  • Not a newbie anymore
  • January 28, 2026

As this is our company’s Lab (we are a Veeam reseller/partner), I don’t think Support will be interested in a case from us. If at all, it will land on the bottom of the pile as paying customers have priority.

I therefore hope that, because multiple people are affected, Veeam notices this thread and add it to the “to fix” list.


mrizzi2
  • New Here
  • January 29, 2026

Same issue here as well.

I opened a support case yesterday and it looks like Veeam Support has acknowledged the issue:

Thanks for reaching out to Veeam Support. I'll be assisting with your case until an engineer is assigned.

Regarding the error messages about failed updates, we have had some reports of automatic updates failing intermittently while manual updates are successful. If the manual update process continues to succeed no further action is required, but please let us know if there are update issues or if you have questions.

I will need to follow-up with the engineer as unfortunatelynot an acceptable solution to just live with the automatic updates failing intermittently according to the reply above.

Massimiliano


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • January 29, 2026

I would definitely follow up with support on that answer.


Forum|alt.badge.img
  • Comes here often
  • February 21, 2026

We had the same issue. Support confirmed this as a bug when you are using an NFR license.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • February 21, 2026

We had the same issue. Support confirmed this as a bug when you are using an NFR license.

Glad Support got you sorted, and thank you for sharing what causes the issue.


Chris.Childerhose
Forum|alt.badge.img+21

@Stefke72  - just wanted to follow up to see if you got an answer to your inquiry?  If so, please mark the best answer that helped the most, even if your own.  Look forward to assisting further if needed.

 
 
 

  • Author
  • Not a newbie anymore
  • Answer
  • March 21, 2026

@Stefke72  - just wanted to follow up to see if you got an answer to your inquiry?

 

Hello Chris,

Because this is a NFR license, which I generate/fetch from our partner/reseller’s Partner portal account, the correct product is not listed as a product we licensed. Thus it cannot be selected during case creation thus case-creation fails. Picking up the phone and call support is useless as the “iron lady” in the menu says one can only continue with an existing case number. Which we don’t have because we cannot create a case.

This NFR bug is apparently still present in the current 13.1.2067 build (Windows BR Server). I got a mail 2 days ago about all the VSA and VIA appliances saying:
Status: error , Sync: error, Updates: none (which is actually correct as there is no newer build. I updated the Windows BR Server using the Patch ISO which then updated all Appliances automatically.

To answer your question: I was never able to raise a case. Maybe this bug will get solved one day.


Chris.Childerhose
Forum|alt.badge.img+21

Thanks for the update sorry you couldn't get further.  Hopefully this will be addressed at some point.