Veeam 13 issues after upgrade

[0000Backup0000]

Same issue since 14/03/2026 auto update from 13.0.1.180 → 13.0.1.2067.

Veeam Support - Case # 08023178, opened on the 14.03.2026 and on going.

[GreenEnvy]

Support ticket: 08030155
Also not sure if it is related, but I was unable to generate logs. When I go to 'export logs for this job', the select box that appears is empty, no jobs visible.

[renatorichina]

Just as an information. While our own VBR still have the issue (we have a Nutanix Enviroment), I noticed that maybee it's less common on Hyper-V enviroments: I have upgraded around a dozen of customer installations the past 3 days (all have Hyper-V) from 12.x or 13.0.180 to 13.0.1.2067 and I discovered the guest processing issue only at one single of those customers, while all have at least a job with activated guest processing.

Another thing discovered, which I also find a little strange: I have left for all of the customers Hyper-V backupjobs the default setting for the Backup Proxy, meaning (Off-host backup) with the as well default setting for "failover to on-host backup mode if no suitable off-host proxies available"

However, I've discovered then, that the "Guest Interaction Proxy" was NOT installed on any of the hyper-v hosts after the installation/update to 13.0.1.2067. When I gone through the Properties wizard under "Backup Infrastructre" - "Managed Servers" - "Microsoft Hyper-V", all had the Status "not installed" under the GIP and it has been installed then when I processed the dialog.

Not sure, if this is by design, or this might be a glitch, that the GIP is not installed by default on the host when doing the update/upgrade to 13.0.1.2067.

#08022476 (our own Nutanix GIP issue) now escalated to next tier support and under investigation by RnD team according to the newest status of today

[david.domask]

Hi Renato,

Thank you for sharing the details, but for items not related to the topic, it's best for another topic so we can keep this one on topic; in your case since it's being investigated already, no need for a topic unless you have questions about the results of the case.

[magrichad]

Case: #08026088

I Would also like to provide some extra info on what I noticed on our Nutanix cluster. All our physical servers (agents) are working fine. All our AHV Windows 11's are working fine. All our Linux/etc VM's are working fine.

Almost all our AHV Windows Servers are not working with the exception of one! There is nothing special about the one that is working. It's on the same VLAN and uses the same credentials as the other Windows servers, it's also on the same domain. Very strange behaviour.

I also had to manually update the proxy worker as the patch did not do that, like the others have reported.

[TAnderson]

Adding my case if it will help Case # 08024663

Similar issues that sound identical
Nutanix backups worked fine until I applied the critical patch last Friday (3/13) then any Nutanix App Aware job started failing
Tech assigned is not addressing the elephant in the room that this patch is what triggered the issue. I have reverted my Veeam server to a backup from Thursday night and run the jobs, they work fine. I snapshot the Veeam Windows server then apply the patch. App Aware backups fail. Revert the snapshot, backups work.

Based on the comments here I manually copied over the deployment kit, no change in behavior. Getting errors like
Failed to prepare guest for hot backup. Error: Failed to connect to the guest OS.
Failed to install guest processing components for <COMPUTER> Error: Failed to connect to the guest OS.

Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [<COMPUTER>]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error:The service did not respond to the start or control request in a timely fashion. Code: 1053
Failed to install guest processing components for <COMPUTER> Error: Cannot start service. Machine: [<COMPUTER>]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error:The service did not respond to the start or control request in a timely fashion. Code: 1053

Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [<COMPUTER>]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error:The service did not respond to the start or control request in a timely fashion. Code: 1053
Failed to install guest processing components for <COMPUTER> Error: Cannot start service. Machine: [<COMPUTER>]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error:The service did not respond to the start or control request in a timely fashion. Code: 1053

Technician assigned suggested I change app aware to Ignore Failures so I would get crash consistent backups and now we get

Warning : Failed to prepare guest for hot backup. Details: Failed to connect to the guest OS.
3/20/2026 12:10:34 PM Warning : Skipping guest VM freeze...
3/20/2026 12:10:40 PM Warning : Skipping guest VM unfreeze...
But we are getting some sort of backup, doesn't help with my recovery of SQL and confidence with recovering AD but it is what it is.

Unfortunately I cannot tell if it's limited to Nutanix backups because coincident with upgrading to Veeam 13 my Hyper-V repository decided to go on a bender and not backup because it is out of sync. This is a separate issue in my opinion.

Veeam server non-domain joined Windows 2016 fully patched
16GB RAM
8 vCPU's
Not migrating to appliance until all these issues are addressed

[homerjs]

any news?
i have the same problem

[homerjs]

Case #08023462

Application-aware processing fails for all backup jobs on Windows Server 2025.
March 15, 2026 8:43:12 PM Failed: Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [xxxx]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error: The service did not respond in time to the start or control request. Code: 1053
Everything was still working in version 13.0.1.1071

[Henrik.Grevelund]

Hi There,

Same issue. Case # 08022140

Really hope this gets fixed soon.

[cdlansys]

Hello,

add also my case to this: Case #03716419

[david.domask]

A small update, we're still actively reviewing the behavior with Veeam RND and working on a resolution for this -- please continue to open Support Cases to track the issue, Veeam Support has guidance on identifying the issue and will inform of the current status. Regrettably no workarounds have been identified, but no further isolation testing should be required at this point, we are awaiting further results on the research.

[DerOest]

On our Windows based v13, after the latest update to 13.0.1.2067, we encounter these problems as well.

I just noticed that our PVE Plugin was not updated to the current 13.3.1.7 (March 12, 2026) as mentioned by someone else here in this thread!
Our Plugin Version was/is 13.3.0.237

-> proxmox-ve-f79/pve-backup-recovery-t97076.html
Currently downloading...


The same problem also happenes in the Linux based Software Appliance Test-Installation we have running in parallel - so i have no high hopes, that updating the Plugin on the windows-based install will actually help.
Thank god our main production setup is still on 12.3

[claudiohipolito]

Hello everyone,

Support Case:08030407

I would like to check if anyone has any updates or possible workarounds for this issue. I am experiencing the same problem after applying patch 13.0.1.2067.

In my environment, this is related to a Nutanix job for SQL Server with Application-Aware Processing enabled.

Error Details.

23/03/2026 15:34:22 Failed : VM Server : Failed to perform backup: Failed to install guest processing components for VM Server Unable to install guest processing components. (0:01:13)

So far, I have already tried the following actions without success:

Removed the guest agent/proxy components
Performed a rescan from the console to reinstall and update the components
Verified that the server firewall and antivirus are disabled
Tested connectivity via telnet — all required ports are reachable

Despite these steps, the issue still persists.

Has anyone faced the same behavior or found any solution/workaround?

Thanks.

Cláudio Hipólito

[Dima P.]

The QA team is currently investigating the reported issues. We will update this thread with the findings once available. Thank you for sharing your support cases!

[ronnmartin61]

A private hotfix should be available any second now for customers with open cases. Once its proven effective for mitigating this issue we'll create a public KB for hotfix download...

[DarrenH]

Case Number - 08021647
Case logged 13/3/26
Veeam B&R version before update - 13.0.1.180
Veeam B&R version after update - 13.0.1.2067
Proxmox plug-in version before update - 13.3.0.237
Proxmox plug-in version after update - 13.3.0.237
Proxmox version 9.1.6

Most of our customers are SMB local government and some private customers.
We keep our configs fairly vanilla.

When we logged our case, we mentioned that the Proxmox plug-in had not had a version change.
We found out about the new Proxmox plug-in via this thread, thanks guys.
We've installed it (13.3.17) however we still get the same error.

Our VMWare sites all upgraded ok.
All Proxmox sites that were upgraded had the same error.
Our local government sites get advisories about Veeam security updates and ask us to apply the updates quickly.

We logged our case as a Sev1 however because we'd already worked out to turn off application aware processing it was downgraded to Sev2.
We asked for it to be put back to Sev1 as there was no practical workaround and it was affecting multiple sites however it's still Sev2.

Because we get the Veeam R&D weekly email we found this thread.
We'll add it to our support case.

The VeeamGuestHelper does not install but you can't get dump logs because the C:\Windows\VeeamVssSupport folder disappears when the install fails.
Below is what the VeeamGuestHelper.log shows.

Module name: [VeeamGuestHelper.exe].
Module path: [C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe].
Build edition: [standard].
Module version: [13.0.1.2067].
domainname.local\servername$
Command line: C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe -rpcPort -1
Writing dump. Dump path: C:\Windows\VeeamVssSupport\VSS_crash_0.mdmp.
Executing crash handlers.
Crash handlers were successfully executed.

[DarrenH]

Case Number - 08021647
I just got the private hotfix from support.
It was an update to the Veeam Plugin for Proxmox.
VeeamPluginPVE_13.3.1.7

It still failed with the same issue.
I tried again after a backup server reboot and still got the same error.
Support has been advised.

[newmrac]

Received private hotfix Fix_1308804_35dbf0a14f.
Fixed our issue with PVE guest backups

[david.domask]

Thanks for sharing newmrac,

Support should be aware of the fix at this stage and looks like it's being pushed out on cases that have been opened. For those who think they may be affected but do not have a case open yet, please still open a Support Case and be sure to share logs for one of the affected jobs. Support will review the situation and advise accordingly. You can mention internal support KB KB0060468, but please note that Support will still need to review the logs to confirm the behavior matches the issue.

[magrichad]

Case: #08026088

Private fix on our Nutanix 7.3 cluster is looking promising. A job that was failing is now run succesfully. Will report back tomorrow after all jobs have run overnight.

[malwinstar]

Case #08017433
We’ve encountered the same issue with Nutanix AHV Guest Processing as well. Looking forward to the fix.

[david.domask]

Hi malwinstar, welcome to the forums.

Thanks for sharing the case number, but at this stage as we have a fix available through support, I don't believe we need any additional cases added to the list. See my previous post on how to handle a Support Case if you believe you're affected by the issue.

For future readers / viewers, we do not need additional cases posted at this time as there is a fix available through support. The issue primarily affects Nutanix and Proxmox (PVE) backups using Guest Processing, but steps were taken to address concerns reported on VMware and Hyper-V backups as well. The issue specifically follows the pattern:

- Previously on 13.0.1.x
- Updated to 13.0.1.2067 (Patch 2, P2)
- Guest Processing stopped working with errors noted on first page of thread

If your symptoms match this, proceed to open a Support Case and be sure to share logs for one of the affected jobs. Support will review the situation and advise accordingly. You can mention internal support KB KB0060468, but please note that Support will still need to review the logs to confirm the behavior matches the issue.

For other issues, proceed with a Support Case directly, we will not be able to troubleshoot over the forums, and forum post / topics for technical issues that do not already have a Support Case will be removed.

[daniel.lindner]

Hello together,

the support provided me with a Private Fix 1303041 that solved the problem.
I had to take the following steps:

1. Install Private Fix 1303041
2. Delete broken service registrations on servers where the the job failed before and left them in an incosistent state via "sc delete VeeamGuestHelper" in the CMD inside the guest VM.
3. Restart the Guest VMs where the service has been deleted before.

Finally a big Thank you to the Support Team for the fast response and the provided fix. Good Job!

[claudiohipolito]

Case #08030407

We are currently awaiting the private hotfix to address the issue in the Nutanix environment with Application-Aware processing enabled.

Thanks.

[Schwendes]

Dear Support Team,
Is there already a scheduled release date for the public patch? I would prefer to avoid opening individual cases for all of our customers. Since we operate Veeam Data Protect via Wortmann AG (Terra Cloud), we would be able to roll out the patch globally to all systems, which would save us a significant amount of time and effort.
We have consistently observed this issue with customers using Proxmox; so far, we haven't encountered any problems regarding this with VMware or Hyper-V. However, as we will be migrating our customers from VMware to Proxmox over the coming days, it would be very helpful to have a fully functional Veeam solution to support the transition.

Best regards,
Andreas Schwendemann

[magrichad]

Case: #08026088

Private fix on our Nutanix 7.3 cluster is looking promising. A job that was failing is now run succesfully. Will report back tomorrow after all jobs have run overnight.

Coming back to report that all our overnight backups were run succesfully with the private fix.

[david.domask]

Dear Support Team,
Is there already a scheduled release date for the public patch? I would prefer to avoid opening individual cases for all of our customers. Since we operate Veeam Data Protect via Wortmann AG (Terra Cloud), we would be able to roll out the patch globally to all systems, which would save us a significant amount of time and effort.
We have consistently observed this issue with customers using Proxmox; so far, we haven't encountered any problems regarding this with VMware or Hyper-V. However, as we will be migrating our customers from VMware to Proxmox over the coming days, it would be very helpful to have a fully functional Veeam solution to support the transition.

Best regards,
Andreas Schwendemann

Hi Andreas,

All fixes must come through Veeam Support as noted in my post above. Please open a Support Case as noted in my previous post and Support will provide you with the fix once they confirm the behavior.

The fix will naturally be included in a future release without the need for a private fix.

[renatorichina]

Case #08022476 : I got the private fix yesterday and installed it today and guest processing with the persistent agent ( Nutanix) is now again working.

However there seems still to be an issue/bug, that if the persistent guest agent from Veeam VBR Version 13.0.1.2067 is already installed on guest vm's, the update to the new guest agent version is not working automatically, because the installation fails to update the Veeam Installer Service from 13.0.1.1071 to 13.0.1.2067, here is the error in the installation log:

MSI (s) (94:80) [09:10:27:876]: Product: Veeam Installer Service -- Configuration failed.

MSI (s) (94:80) [09:10:27:876]: Windows Installer reconfigured the product. Product Name: Veeam Installer Service. Product Version: 13.0.1.2067. Product Language: 1033. Manufacturer: Veeam Software Group GmbH. Reconfiguration success or error status: 1638.

MSI (s) (94:80) [09:10:27:876]: MainEngineThread is returning 1638
MSI (s) (94:44) [09:10:27:876]: No System Restore sequence number for this installation.
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

So I had to remove manually the old Veeam Installer Service 13.0.1.2067 on all the guest vm's first. After that, installing the Veeam Deployment Kit has worked and also the application aware backup jobs run successfully afterwards.

[DarrenH]

Case Number - 08021647
We worked out why our private update did not work.
When we ran it, it said it had finished OK.
However later we checked the versions and found Veeam Backup & Replication was still on 13.1.0.2067
We ran it again and this time it updated to 13.0.1.2174.
We also ran the sc delete VeeamGuestHelper to remove the rement service on some servers.
The Veeam Plug-In for Proxmox Virtual Environment was updated manually to 13.3.1.7

Our jobs then worked ok.
Note they also worked ok with the older version of the Proxmox Plug-in as long as the private hotfix (13.0.1.2174) had installed OK.

[TAnderson]

Adding my case if it will help Case # 08024663

Similar issues that sound identical
Nutanix backups worked fine until I applied the critical patch last Friday (3/13) then any Nutanix App Aware job started failing
Tech assigned is not addressing the elephant in the room that this patch is what triggered the issue. I have reverted my Veeam server to a backup from Thursday night and run the jobs, they work fine. I snapshot the Veeam Windows server then apply the patch. App Aware backups fail. Revert the snapshot, backups work.

Received a private fix from support. It took care of about 90% of the failing Nutanix backups. The remaining 10% I had to install the deployment kit on each of the servers. All the servers in question were 2022 Domain Controllers in a single site. Other DC's in remote sites were fine. Hopefully this fix is released to the general install soon.