Skip to main content
Question

Veeam 13 install failing and support can't figure it out for two weeks

  • January 8, 2026
  • 7 comments
  • 98 views
S

Sorry to rant, but I have nowhere else to turn, and it's beginning to impact our clients.

 

Veeam 13 has been absolutely horrible to install on all our backup servers. The upgrades are breaking the installs on current backup servers. It is straight up failing to install and start the Veeam service on a brand new server, and Veeam support has been unable to figure it out for two weeks. I've put escalation requests in and I'm getting nowhere.

 

has anybody seen behaviour like this? The people on the Veeam subreddit agree that Veeam 13 has been horrible to roll out.

    7 comments

    Chris.Childerhose
    Forum|alt.badge.img+21

    You are going to need to continue with support as the community is not support and we don't know the details.  Sorry to say this but community is just that and not technical support.  They will get things sorted and if needed go to your account team.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    S
    • SkycompJoe
    • Author
    • New Here
    • January 8, 2026

    Exactly. This is the COMMUNITY. I'm trying to ask the COMMUNITY about their experiences with Veeam 13.

     

    Where do you recommend I go to speak with the COMMUNITY

    Chris.Childerhose
    Forum|alt.badge.img+21

    Well I am not saying don't ask here just that your particular issue we won't be able to help.  There were issues reported about services starting properly during the update to v13 and I even had that but they are specific use cases most times.  I know they repacked the ISO to try and address the issue but it was still happening.  I am not sure if the new update released this week fixes it but something to try.

    Also being a community member using caps and getting your back up will not have anyone chiming in.  I get the frustration.  You can also try searching the  Veeam forums too for the issue.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    coolsport00
    Forum|alt.badge.img+21
    • coolsport00
    • Veeam Legend
    • January 8, 2026

    Hey ​@SkycompJoe -

    Yeah..sorry about the issues. v13 is so new..not sure anyone will have much to share here. Because you do have a case open, might be best to see what the PMs say over on the Forums. They do tend to ask you provide a case# as well. Maybe they have an idea of what’s going on in your particular use-case?

    Keep us posted (if nobody here has any helpful info to benefit you).

    Best.

    Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
    MicoolPaul
    Forum|alt.badge.img+23

    Hi ​@SkycompJoe 

     

    I’ve not seen any installation errors first hand from any customer I’ve spoken to. Sadly the optics of a subreddit will always be worse as people will post much more likely if something has gone wrong vs right.

     

    Thats not to invalidate your experience however.

    If this is happening across multiple servers, this suggests a commonality that is breaking this.

     

    Are you a VCSP hosting all the servers yourself? Or are you providing some form of MSP with individual servers within different customer environments?

     

    This could indicate a common installed application that isn’t compatible.

     

    Can you also share the error output when trying to start the service?

    Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
      CarySun
      Forum|alt.badge.img+7
      • CarySun
      • Veeam Vanguard
      • January 8, 2026

      ​@SkycompJoe I would recommend you share the specific issues and error messages in the community.

      I believe everyone in this community will be happy to share our experiences if we have the same issues. 

      Veeam Vanguard | VMCE 2024 | Microsoft MVP | Cisco Insider Champion | CISCO CCIE #4531 | Web Site - carysun.com | Blog Site - gooddealmart.com | Blog Site - checkyourlogs.net | X: @SifuSun | LinkedIn: https://www.linkedin.com/in/sifusun/ | Amazon Author: https://Amazon.com/author/carysun
        K
        Forum|alt.badge.img+2
        • kevin.boddy
        • New Here
        • January 9, 2026

        Hi,

         

        We didn’t have an issue installing v13 but running it has been problematic.

         

        Increase your service start-up time to 5 minutes with this command.

        Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control" -Name ServicesPipeTimeout -Value 300000 -Type DWord

         

        This was the only way we can get the Veeam services to start. They appear to be built on a newer .NET and are either not optimised yet or newer .NET versions are just extremely slow.

         

        We also had to basically double our memory capacity on all backup servers.

          Terms & ConditionsAccessibility statement