TRIPLE-Bugreport: V13 web console presents out-of-date console for download, wipes out V12 install, fails to update

[mikeely]

Summary: when you browse to the V13 Veeam Software Appliance web console you get this potentially-useful message:
"Download Windows-based backup console for full experience"

So, if you need it, you download the console. Then you install it, which takes a long time and upgrades your V12 console whether you want it to or not, which is a pain in the backside when you're testing a V13 deployment and now you have to reinstall the V12 console. Add a "upgrade or install separately" option please. That's Bug #1

Anyhow now you've force-upgraded your V12 console to V13, or installed V13 fresh, and after launching you point your freshly-installed V13 console at the server you downloaded it from. OH HAHA JUST KIDDING: "In order to connect to this server, backup console must be updated. 13.0.1.180 -> 13.0.1.1071" (as of today anyhow). That's Bug #2

So you once again enter admin creds to allow the software updater to run, and then you watch the little spinner run for a while, getting no work done (unless you count filing multibug reports on the Veeam forums as "work" which I guess it is, although not work benefiting our employers). Anyhow, just as you've decided to go ahead and fix some more coffee/tea/martinis/etc. and let the "I'm doing something, promise!" spinner do its thing, you learn the spinner had failed to keep its promise and instead you have: "Failed to update the backup console: Failed to deliver update specification to backup server." You guessed it, that's Bug #3

The solution is to uninstall all the Veeam stuff from your Windows computer, then download the 1.5G (good thing we all have fast internet!) installer for the Veeam console from my.veeam and install that.

I know and am thankful that Veeam is moving away from this bloaty .NET console mess, but during this period of transition I encourage Veeam to remember how Apple handled a similar situation when they introduced OS X. Despite the fact that virtualization wasn't very mature back then, they still managed to present a nearly-seamless integration of their "Classic" apps. The amount of friction I've just run into with the console is... really rough.

[mikeely]

Actually, I spoke too soon. The download on my.veeam.com is ALSO out of date, it's presenting 13.0.1.180 just like the VSA is. Great. A sysadmin has no console.

[hwextreme]

well you are further ahead then me

Installed the console from my VBR which is also newer than the console or from the site, I receive "This computer does not meet system requirements"
Windows 10 21H2 19044.6937 (Windows 10 Enterprise LTSC)

logs just show
[19.02.2026 16:52:28][INFO] There are some reasons that prevent wizard from starting.

I guess I will wait for the new console

[mikeely]

So I looked around on my.veeam and realized the full 18G ISO with VBR installers on it has the same version number as the VSA, so I downloaded that (I really do have fast internet, much faster than the Veeam download site as it happens). I installed the B&R console from there and... NO!

"In order to connect to this server, backup console must be updated. Maintenance update Download size: 218.4 MB"

So, different from the version change off the file I downloaded from the VSA web console, but still no joy: "Failed to update the backup console. Failed to deliver update specification to the backup server."

Think I'm going to shell into the VSA and start just downloading all the windows executables off of it. Good grief.

[mikeely]

Solution: Veeam console has to be run as administrator for the updates to complete. EVEN THOUGH the installer requests privilege escalation (what we call "sudo" in the world of real computers), this fails to apply the escalated privileges to everything that needs them.

tl;dr: if you're in this situation, right click the console launcher icon and run as admin

[hwextreme]

Great minds think alike

I tried the same approach..I copied the installer from my Windows V13 server (13.0.1.1071) and also attempted to connect to the appliance (Product Build: 13.0.1.1071) from the V13 Windows VBR However, it still reports that the versions are different and will not proceed with an update because this console is already installed on the same server as the VBR.

I’m currently spinning up a separate VM to install the console, as it appears my Windows 10 version may not be on the approved support list. The installer fails almost immediately, which suggests it isn’t failing on a prerequisite check but rather rejecting the OS version outright.
I checked out the RPM packages in the VSA ISO and couldn't identify which was the update, only the .180 console

[B.F.]

tl;dr: if you're in this situation, right click the console launcher icon and run as admin

I too am stuck with the 13.0.1.180 --> 13.0.1.1071 update fails. We use our "normal" account on our PC and as the need arises, use our privileged (admin) account. We login to VBR with our admin account while logged into our PC with the normal account. When I right click and launch it with my admin account, this is what I get

"We couldn't create the data directory
C:\Users\<MyAdminAccount>\AppData\Local\Veeam\Backup\ConsoleLauncher_Elevated\EBWebview"

[B.F.]

Got it to work. I had to log out of Windows and login with my admin account. Then it went through the motions without issue. Not the handiest

[mikeely]

Gotta love Windows... not.

[Mildur]

Hi @mikeely,

Thanks for your topic.

We need to differentiate between a bug, expected behavior and a missing feature:

• Bug: An issue that must be confirmed by our Customer Support team as a technical defect. Not everything a customer dislikes is a bug. If confirmed as a bug, Support will provide a workaround or ask RnD to create a private fix.
• Expected behavior: The product was designed to behave this way. If a customer does like it to behave differently, a feature request can be submitted in our forum.
• Missing feature: A feature is not available today. A customer can submit a request for it to be added.

With that in mind, allow me to comment on your "bug" report:

Bug #1:
This is expected behavior. It has never been possible to deploy multiple versions of the backup console on the same machine. Longer term, this will be addressed by the new Web UI introduced in v13. A single webbrowser can open Web UIs from different backup server versions. And V13.1 will already add additional workload support and smaller enhancements in the Web UI.

Bug #2:
This is also expected behavior. We plan to update the standalone backup console binaries in the download center and Web UI only for minor versions (for example, v13.1, v13.2, v13.3, ...). Long term, this will also be addressed by simply using the Web UI.

Bug #3:
This may be a bug, but it must be confirmed by Customer Support. A support case (with logs) is the correct approach here rather than "filing multiple bug reports via forum posts". As explained in our forum policies, this forum is not "technical support". "Forum posts with bugs" and no case number may be deleted by a moderator.

Thank you,
Fabian