Obtaining older (minor) versions?

[lluttrell]

Hi,

Is there a way to obtain an older version of version 13 and/or the recovery media? I only have access to the latest version, which appears to be broken. I can't find any of the older versions on the download page.

Support case: 08128512
Reddit thread describing issue: https://www.reddit.com/r/Veeam/comments ... a_restore/

[david.domask]

HI lluttrell, welcome to the forums.

Thanks for sharing the case number, and sorry to hear about the challenges.

I see the case was opened as a Free case which receives "best-effort" support; I strongly recommend obtain an Evaluation License from my.veeam.com and re-open the case with an Evaluation license as that will receive Evaluation Support instead of best-effort.

Older versions can be obtained through Support, however, without a review of the debug logs I think it's a bit premature to call it a bug -- I see that others reported similar issues, but an authentication error is something that should be investigated to understand the actual root cause. Not saying it's not an issue on recovery media, more saying "not enough information" at the moment.

I repeat the recommendation to obtain an Evaluation license for your evaluation period and reopen the case with Evaluation Support.

[lluttrell]

Thanks for the response. Is an evaluation license the same as a trial license?

Edit: I see in the license file it's called "evaluation".

[Andreas Neufert]

yes

[lluttrell]

Thank you for your advice. I worked through this with support (case 08133492).

I don't know if this is the appropriate place to ask, but I just want to confirm what I've been told:

There's no way to create a working recovery image on any Windows 11 since version 24H2 26100.3194 (Feb 2025)? I find this somewhat hard to believe, since the referenced KB4726 says the issue was fixed.

Please let me know if this is a different and more recent bug. I don't think I'm going to be able to convince management to shell out for a product that has had core functionality broken for over a year, and that requires installing windows 10 in a VM as the workaround. My gut says it's a new bug and just bad timing on my part!

[david.domask]

Hi lluttrell,

I would advise please continue with the Support Engineer; there are a few issues discussed on the latest update and I'm not quite following every statement in full, but I see the Engineer told they are inquiring internally for further details on your questions.

If the solution from KB4726 is not working, I would advise ask in the case why it's not working directly, and if there appear to be challenges with how the case is being handled, use the Talk to a Manager button from the case portal to reach out to Support Management; they will review the case and allocate additional resources as needed.