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