veeam agent backup failed error code 5

TL;DR

Error code 5 in Veeam Agent is the Windows access denied code surfacing through the agent. The service account cannot read a source volume or cannot write the destination share or disk. Check the exact path in the job log, test it with the same account, fix NTFS and share permissions together, and rerun.

veeam agent backup failed error code 5

Use this when

• Veeam Agent for Windows job fails with error code 5.
• The log names a volume, folder or share right before the code 5 line.
• The job worked until permissions, group policy or the destination changed.

Not for this skill when

• Network share access denied for a server backup job without an agent. The fix overlaps but account context differs.
• The destination is full. Space failures give different codes and messages.

Steps

1. Open the agent job log and copy the exact path or volume named with the error code 5. Verify: the denied resource is identified precisely
2. Confirm which account the Veeam Agent service and the job run as, noting any recent account or group policy change. Verify: the effective account is known
3. Test access to the named path interactively as that account, checking both share permissions and NTFS permissions on the destination. Verify: the failing permission layer is found
4. Grant the minimum read right on sources and write right on the destination, including the Veeam transport folders if a local cache path is named. Verify: the manual access test now succeeds
5. Rerun the job and confirm it passes the previously denied path. Verify: the job completes or moves past the code 5 step

Variant phrasings

veeam agent error code 5 access denied

The access-denied wording of the same code.

veeam agent backup failed 5 destination

The destination-focused variant.

windows error 5 veeam agent

The operating system code phrasing.

Compatibility: Veeam Agent for Microsoft Windows 6 on Windows 10, 11 and Windows Server 2019 and 2022, standalone and managed by Veeam Backup and Replication 12.

Why it happens

Windows returns error 5 whenever a handle request is denied, and Veeam Agent surfaces it without translating it. The denial usually follows a tightened share, a service account removed from local administrators or backup operators, endpoint protection blocking the agent binaries, or a destination that now requires signing or a different protocol version.

Edge cases / pitfalls

• Share and NTFS rights are separate gates. Passing one and failing the other still yields code 5.
• A destination USB disk formatted or swapped recently may carry permissions from another machine.
• If the named path is a volume root, check the agent can open the volume for VSS, not just browse files.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-ike3PFoHthSrROP5hAR4Q