Patch 13.1.1.18 on VBR 13.1.0411 (Windows) required multiple reboots, anyone else?

[DatatoSecure]

Hello,

Last Friday we applied patch 13.1.1.18 to VBR 13.1.0411 on Windows Server 2016. The install was much harder than usual and took several reboots before it completed.

One of our clients hit the same thing on the same day. He was also running VBR 13.1.0411 on Windows Server 2016. After installing the patch, he could not make his VBR server work. So he then built a new Windows Server 2025 machine and restored the configuration backup, and VBR ran fine. But the patch failed again on the new server. What finally worked was disabling the Veeam Backup service, rebooting, and reapplying the patch.

Has anyone else seen this? I'm sharing the workaround in case it helps.

Regards,
François

[Mildur]

Hello,

That sounds like a technical issue. We cannot investigate why the backup service couldn’t be stopped through a forum topic.
Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

Also multiple reboots is unusual. One reboot yes, but not multiple.
Our colleagues from customer support team are the ones who can tell you why this may have happened after investigating the log files.

Best regards,
Fabian

PS: support can only help if you upload logs https://www.veeam.com/kb1832

[DatatoSecure]

Hi Fabian,

Since I was able to fix the issue, I don't intend to open a support case.

My post was just to start some statistics; three systems having the same issue raised a bell with me. "Twice is a coincidence three times is a pattern"
Even with pushing the update to the third server via the Veeam Service Provider Console was a no go.


Regards,
François