Skip to main content

Veeam Console Connection & Permission Errors

Audience: T1 / T2
Version: 1.0
Last Updated: April 2026
Applies To: Veeam Backup & Replication (all versions)

Overview

This guide addresses connection errors when opening the Veeam Backup & Replication console, specifically permission denied errors related to the Veeam updates folder.

Common symptoms:

  • "Access to the path 'C:\windows\TEMP\Veeam$VeeamUpdates' is denied"
  • Console fails to connect to localhost:9392
  • Error appears when launching Veeam console with valid credentials
  • May occur after Windows updates or system maintenance

Error Details

Full error message:

Access to the path 'C:\windows\TEMP\Veeam\$VeeamUpdates' is denied.

When it occurs:

  • Opening Veeam Backup & Replication console
  • After Windows updates or reboots
  • After antivirus scans or system cleanup
  • When TEMP folder permissions change

Root cause: The Veeam console process cannot access or create the updates folder in the Windows TEMP directory due to incorrect permissions or folder corruption.

Resolution

T1 - Quick Fix (Run as Administrator)

Fastest resolution: Run Veeam console as administrator to bypass permission restrictions.

  1. Close any open Veeam console windows
  2. Navigate to: C:\Program Files\Veeam\Backup and Replication\Console
  3. Right-click Veeam.Backup.Shell.exe → Run as administrator
  4. Console should open successfully

If this works: This is a temporary workaround. Proceed to T2 for permanent fix.

T2 - Permanent Fix (Reset Folder Permissions)

Option 1: Recreate the Veeam TEMP folder with proper permissions

Run these commands in PowerShell as Administrator on the BDR:

# Stop Veeam services
Stop-Service VeeamBackupSvc -Force
Stop-Service VeeamCatalogSvc -Force

# Remove the corrupted Veeam TEMP folder
Remove-Item -Path "C:\Windows\TEMP\Veeam" -Recurse -Force -ErrorAction SilentlyContinue

# Create fresh Veeam TEMP folder
New-Item -Path "C:\Windows\TEMP\Veeam" -ItemType Directory -Force

# Grant permissions to the folder (Users group gets modify rights)
$acl = Get-Acl "C:\Windows\TEMP\Veeam"
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Users","Modify","ContainerInherit,ObjectInherit","None","Allow")
$acl.SetAccessRule($rule)
Set-Acl "C:\Windows\TEMP\Veeam" $acl

# Start Veeam services
Start-Service VeeamBackupSvc
Start-Service VeeamCatalogSvc

# Verify services are running
Get-Service Veeam* | Select Name, Status

Expected output:

Name                    Status
----                    ------
VeeamBackupSvc         Running
VeeamCatalogSvc        Running
VeeamDeploymentSvc     Running

Option 2: Grant permissions without recreating folder

If you don't want to delete the folder, just fix permissions:

# Grant Users group modify permissions to existing folder
$path = "C:\Windows\TEMP\Veeam"
$acl = Get-Acl $path
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Users","Modify","ContainerInherit,ObjectInherit","None","Allow")
$acl.SetAccessRule($rule)
Set-Acl $path $acl

# Verify permissions
(Get-Acl $path).Access | Where-Object {$_.IdentityReference -like "*Users*"}

Expected output:

FileSystemRights  : Modify, Synchronize
AccessControlType : Allow
IdentityReference : BUILTIN\Users

T2 - Alternative Fix (Clean TEMP Folder)

If the above doesn't work, the issue may be broader TEMP folder corruption:

# Stop Veeam services
Stop-Service Veeam* -Force

# Clean entire TEMP folder (caution: removes all temp files)
Remove-Item -Path "C:\Windows\TEMP\*" -Recurse -Force -ErrorAction SilentlyContinue

# Restart Veeam services (will recreate Veeam folder automatically)
Start-Service VeeamBackupSvc
Start-Service VeeamCatalogSvc

⚠️ Warning: This deletes ALL temporary files. Only use if Option 1 and 2 fail.

Verification

After applying the fix:

  1. Test console connection:

    • Open Veeam Backup & Replication console normally (not as admin)
    • Should connect without error

  2. Verify folder exists:

    Test-Path "C:\Windows\TEMP\Veeam\$VeeamUpdates"

    Should return True

  3. Check permissions:

    (Get-Acl "C:\Windows\TEMP\Veeam").Access | Format-Table IdentityReference, FileSystemRights, AccessControlType

    Should show Users with Modify rights

Prevention

To prevent this issue from recurring:

  1. Exclude from antivirus: Add C:\Windows\TEMP\Veeam to antivirus exclusions
  2. Exclude from disk cleanup: Configure Disk Cleanup to skip Veeam temp folders
  3. Document in client notes: If this recurs, note in IT Glue for future reference

Troubleshooting

Console still won't connect after fix

Check Veeam services:

Get-Service Veeam* | Select Name, Status, StartType

All services should show:

  • Status: Running
  • StartType: Automatic

If services won't start:

# Check event logs for errors
Get-EventLog -LogName Application -Source "Veeam*" -Newest 20 | Format-List

Restart all Veeam services:

Get-Service Veeam* | Restart-Service -Force

Error persists on specific user account

The issue may be user-profile specific:

# Check user's TEMP folder
$env:TEMP
# Typically: C:\Users\[username]\AppData\Local\Temp

# Create Veeam folder in user TEMP if missing
New-Item -Path "$env:TEMP\Veeam" -ItemType Directory -Force

"Access Denied" on other Veeam folders

If the error references different paths (e.g., C:\ProgramData\Veeam):

# Grant permissions to common Veeam folders
$paths = @(
    "C:\Windows\TEMP\Veeam",
    "C:\ProgramData\Veeam",
    "C:\Program Files\Veeam"
)

foreach ($path in $paths) {
    if (Test-Path $path) {
        $acl = Get-Acl $path
        $rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Users","Modify","ContainerInherit,ObjectInherit","None","Allow")
        $acl.SetAccessRule($rule)
        Set-Acl $path $acl
        Write-Host "Fixed permissions on: $path"
    }
}

Quick Reference

Fastest fix:

Remove-Item "C:\Windows\TEMP\Veeam" -Recurse -Force -ErrorAction SilentlyContinue
New-Item "C:\Windows\TEMP\Veeam" -ItemType Directory -Force
Restart-Service VeeamBackupSvc, VeeamCatalogSvc

Check if fixed:

# Console should connect without error
# Or verify folder permissions:
Test-Path "C:\Windows\TEMP\Veeam\$VeeamUpdates"

Time to resolution: 2-5 minutes (T1/T2)

  • "Failed to connect to localhost:9392" - May indicate Veeam Backup Service not running (check services)
  • "RPC server unavailable" - Check Windows Firewall and Veeam service status
  • Console crashes on startup - Try running as administrator first, then apply permanent fix

Document History

Version Date Author Changes
1.0 April 2026 Scott Leister Initial creation. Documents "Access to path denied" error for C:\windows\TEMP\Veeam$VeeamUpdates with PowerShell resolution commands.

Confidential — Internal Use Only

Back to top