Skip to main content
Question

Veeam V13 tries to synchronize update settings to delete server

  • October 30, 2025
  • 10 comments
  • 114 views

I get the error 

“30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'
                             b4634265-9228-4a5e-9d95-2c12313e89c6”

This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… 

How do I fix this?


 

10 comments

Mildur
Forum|alt.badge.img+12
  • Influencer
  • October 30, 2025

Hi Georg

 

I strongly recommend to contact our customer support team.

Database modification may be required if Veeam Updater still thinks that the managed server exists.

 

Thank you,

Fabian


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • October 30, 2025

Of course agree with Fabian here, especially cuz v13 isn’t fully GA yet either. Keep us posted what you find out ​@Georg Brunner 


waqasali
Forum|alt.badge.img+4
  • On the path to Greatness
  • October 30, 2025

I get the error 

“30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'
                             b4634265-9228-4a5e-9d95-2c12313e89c6”

This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… 

How do I fix this?


 

 

was it resolve or not yet? 


  • Author
  • New Here
  • November 10, 2025

Reply from Veeam Support:

(...) Please forgive the delay in getting back to you, I have checked this internally and unfortunately it seems to be a known issue with our V13, this has been reported to our R&D and they have an internal thread dedicated to solving this but regrettably no ETA for the fix at the moment.

 


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • November 10, 2025

Thanks for the update ​@Georg Brunner 


  • Author
  • New Here
  • December 1, 2025

Veeam Support closed the case although no solution or workaround was provided :(


waqasali
Forum|alt.badge.img+4
  • On the path to Greatness
  • December 1, 2025

Veeam Support closed the case although no solution or workaround was provided :(

 

I wanted to inform you that Veeam Support does not close cases immediately. Instead, they send automated follow up messages multiple times before closing the case. 


AndrePulia
Forum|alt.badge.img+9
  • Veeam Vanguard
  • December 3, 2025

I’m also want to know the status. 


Mildur
Forum|alt.badge.img+12
  • Influencer
  • December 3, 2025

Hi ​@Georg Brunner 

Unfortunately I cannot find the case number.
Can you please provide me with the case number in a private message here in the community hub? Then I can take a look in our RnD system.

 

Best,

Fabian


Mildur
Forum|alt.badge.img+12
  • Influencer
  • December 3, 2025

I found the case number.
The bug mentioned in your case has already been fixed in the GA release: v13.0.1.180.

Thank you,
Fabian