Skip to main content

The REST API service is not starting after upgrading Windows VBR to 13.0.1 P2

  • March 25, 2026
  • 4 comments
  • 289 views

victorwu
Forum|alt.badge.img+8

Issue: The REST API service times out during initial startup because the default timeout is too short.

 

Fix: Increase the Windows service startup timeout using PowerShell (run as Administrator):

powershell


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


Then reboot the server.

Note: The default timeout was set to 30 seconds in some builds. A repackaged ISO (13.0.1.180_20251130) was released to address this by allowing more time for the REST API service to start.

 

 

4 comments

Chris.Childerhose
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • March 25, 2026

Yeah seen some issues like this with others posting.  Nice that a quick registry update fixes it.


coolsport00
Forum|alt.badge.img+23
  • Veeam Legend
  • March 25, 2026

Thank you for sharing the RegKey fix Victor. Glad you’re up and working again 👍🏻


  • New Here
  • August 24, 2026

I updated to version 13.1.1.18, but afterward I got the same error: the service wouldn't start.

I opened Windows Services and started them manually, then clicked "Retry," and it worked.

Now I found this post. I couldn't test it, but thanks anyway ​@victorwu 


coolsport00
Forum|alt.badge.img+23
  • Veeam Legend
  • August 24, 2026

Well, at least now you’re aware of this fix now ​@LuisR0 😉

Glad you sorted your issue out.

Best.