Agent on Ubuntu 25.10 not working

[Novell2]

Hello everyone, I had installed Veeam Agent V6.3 with Ubuntu 25.04 on a laptop, which worked well.
Without thinking too much about it, I updated the system, which means that the Ubuntu system is now on version 25.10. But now the Veeam agent no longer works. My Linux skills aren't that great, so what commands do I need to run? Do I need to uninstall and reinstall Veeam Agent? Does Veeam Agent version 6.3 work with Ubuntu 25.10? Or do I need to use VBR12 and install the agent in that console?
Thanks a lot for your help!
Cheers
Novell2

[rovshan.pashayev]

Hello Zeller,

Veeam Agent for Linux version 6.3.2.1207 does not support Ubuntu 25.10.

If you need any technical assistance, please submit a Support Case and our support engineers will help you. We're unable to provide support over forum posts.

Don't forget sharing case number here.

[eMKi]

Hi @rovshan.pashayev

is there an ETA, when Ubuntu 25.10 will be supported?
I know it always takes a while but I am just wondering if there is an estimate when the update will be available.

Best regards!

[rovshan.pashayev]

Hello,

Starting with Veeam Agent for Linux v13, the agent supports only Ubuntu LTS releases. Please refer to the Release Notes here.

For any other technical assistance, please submit a support case.

[eMKi]

Hi,

thanks.
Is this also true for
Veeam Agent for Linux FREE
https://www.veeam.com/products/free/linux.html

[rovshan.pashayev]

Hello,

Yes.

[eMKi]

Thank you for your quick response and all the information.
Sorry to hear about this decision. I liked the fact that I could always use Veeam Agent for Linux FREE (after it was updated) when updating Ubuntu to a non-LTS release.

Best regards!

[veritech]

I have run into remote auth errors with other services to Ubuntu 25.10 recently. This looks like it stems from the new code/config under 25.10 with Rust Coreutils. Rust rewrote how sudo works and the new way is set to default and seems to not support --askpass flag. I just recent installed Veeam B&R and ran into the error you are seeing. I just tested out setting the old way for sudo and all warnings on my 25.10 VMs went away (I enabled guest aware processing with accounts per VM). By running the following command elevated: update-alternatives --set sudo /usr/bin/sudo.ws
This apparently sets the default (until it is removed) to the non-rust sudo implementation. Full credit for this find goes to user tomasmatus on the Cockpit Project issues forum here: github.com/cockpit-project/cockpit/issues/22523

Veritech