Azure Agent cannot restore file from a backup
When attempting to restore a file via File and Folders from a restore point with Azure Agent, it takes a long time to mount the disk. However, once it is mounted, I am unable to access it. When I browse, it keeps loading until it gives an invalid parameters error, and I am unable to access the disk. I have already updated the Azure agent to the latest version.
Azure Backup
-
Suchitra Suregaunkar • 1,880 Reputation points • Microsoft External Staff • Moderator
2025-10-14T18:27:21.3833333+00:00 Hello Focagem Soluções de Gestão,
Thank you for posting your query on Microsoft Q&A platform.
Could you please share us the details asked via private message and screenshot of the exact error message.
Thanks,
Suchitra.
-
Suchitra Suregaunkar • 1,880 Reputation points • Microsoft External Staff • Moderator
2025-10-15T00:34:42.7066667+00:00 Hello Focagem Soluções de Gestão,
While attempting to restore files via Azure Backup (File and Folders) using the Azure Recovery Services (MARS) Agent you are experiencing below issues:
- The restore disk took a long time to mount.
- Once mounted, couldn’t access it.
- Browsing the disk resulted in an “invalid parameters” error.
- You have already updated the Azure Agent to the latest version.
I would suggest you to try again below few of the workarounds that has worked and helped others facing the same issue.
- Install MARS Agent Version 9415 or Later
- Download the latest version directly from Microsoft: https://aka.ms/azurebackup_agent
- Or follow the official guide: Install MARS Agent via PowerShell
- Re-register the Server with Fresh Vault Credentials
- Go to your Recovery Services vault.
- Download a new vault credentials file.
- Open the Azure Backup Agent console and re-register the server using the new credentials.
- Verify Scratch Folder Space
- Ensure the scratch folder has at least 5–10% free volume space.
- Lack of space can prevent proper disk mounting and access.
- Exclude Antivirus Interference
- Disable real-time antivirus scanning for:
-
cbengine.exe - Azure Backup folders
- Scratch folder location
- Enable TLS 1.2 and .NET Framework 4.5.2 or Later
- These are required for proper agent operation.
- Registry Fix (if restoring SQL or VM snapshots) Add the following registry key:
If this solution doesn’t resolve your issue, please reply with the following details to help investigate further:[HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BCDRAGENT] "USEVSSCOPYBACKUP"="TRUE"
- Are you restoring from a Recovery Services Vault or Azure Backup Server?
- Is the restore point online or offline?
- What is the exact version of the Azure Agent installed?
- Are you restoring files/folders, VMs, or SQL databases?
- Have you checked the scratch folder space and antivirus exclusions?
- Any event log entries or error codes beyond “invalid parameters”?
Thanks,
Suchitra.
-
Focagem Soluções de Gestão • 0 Reputation points
2025-10-15T10:46:48.0533333+00:00 -
Siva shunmugam Nadessin • 1,990 Reputation points • Microsoft External Staff • Moderator
2025-10-16T00:47:57.0933333+00:00 Hello Focagem Soluções de Gestão
This indicates a timeout during a recovery job. Here’s how you can troubleshoot and resolve it.
To increase the recovery timeout for Azure Backup (especially when restoring large files or volumes), you need to adjust the configuration on the machine running the Microsoft Azure Recovery Services (MARS) agent. By default, the recovery mount session times out after 6 hours, which can cause failures for large restores.
Steps to Increase Recovery Timeout
- Open Registry Editor
- Press Win + R, type regedit, and hit Enter.
- Navigate to the Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider3. Create or Modify the Value
Look for RecoveryJobTimeOut (Type: DWORD).
If it doesn’t exist, create a new DWORD value named
Set its value to the number of hours you want the recovery session to last (e.g., 12 for 12 hours).
Restart the Azure Backup Service
After updating the registry, restart the Microsoft Azure Recovery Services Agent service or reboot the machine.
If the restore still fails after increasing timeout, consider:
- Splitting the restore into smaller chunks.
- Using Instant Restore capability for faster recovery (retains snapshots locally for quick access).
Alternatively you can also try with powershell script which is mentioned below.
# Define registry path and value $RegPath = "HKLM:\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider" $ValueName = "RecoveryJobTimeOut" $NewTimeoutHours = 12 # Change this to desired timeout in hours # Check if the registry path exists if (-not (Test-Path $RegPath)) { Write-Host "Registry path does not exist. Creating..." New-Item -Path $RegPath -Force | Out-Null } # Set or create the DWORD value if (Get-ItemProperty -Path $RegPath -Name $ValueName -ErrorAction SilentlyContinue) { Write-Host "Updating existing RecoveryJobTimeOut value to $NewTimeoutHours hours..." Set-ItemProperty -Path $RegPath -Name $ValueName -Value $NewTimeoutHours } else { Write-Host "Creating RecoveryJobTimeOut value and setting it to $NewTimeoutHours hours..." New-ItemProperty -Path $RegPath -Name $ValueName -PropertyType DWORD -Value $NewTimeoutHours } # Restart Azure Backup Service Write-Host "Restarting Microsoft Azure Recovery Services Agent..." Restart-Service -Name "AzureBackupAgent" -Force Write-Host "Recovery timeout updated successfully to $NewTimeoutHours hours." ``Try and let us know if you have further questions!!
Thanks.
- Open Registry Editor
-
Suchitra Suregaunkar • 1,880 Reputation points • Microsoft External Staff • Moderator
2025-10-16T18:37:16.88+00:00 Hello Focagem Soluções de Gestão
Kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out.
Thanks,
Suchitra.
-
Focagem Soluções de Gestão • 0 Reputation points
2025-10-17T11:04:04.4166667+00:00 Splitting the restore into smaller chunks." how, it only allow me to chose partion V:\ nothing more
Still have the same probleme, Btw before the error occors, it first fail to open the mounted drive"Invalid parameters"
-
Suchitra Suregaunkar • 1,880 Reputation points • Microsoft External Staff • Moderator
2025-10-22T18:25:00.5933333+00:00 Hello Focagem Soluções de Gestão
Azure MARS “Invalid parameters” when browsing mounted ILR volume (V:) Long mount time, V: won’t open, “Invalid parameters” during browse.
As a workaround:
- Extend ILR session timeout\ Set the DWORD
RecoveryJobTimeOutto a higher value (e.g., 12 hours) and restart the Microsoft Azure Recovery Services Agent: HKEYLOCALMACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider Name: RecoveryJobTimeOut (DWORD) = 12 Or via PowerShell (run as admin): $p="HKLM:\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider"New-Item -Path $p -Force | Out-NullNew-ItemProperty -Path $p -Name "RecoveryJobTimeOut" -PropertyType DWORD -Value 12 -ForceRestart-Service AzureBackupAgent -Force. - Free up scratch space & exclude AV/EDR\ Ensure 5–10% free space on the scratch folder and exclude:
- Process:
cbengine.exe- MARS install & Scratch folder paths\ (Antivirus interference commonly breaks browse/IO on the iSCSI mount.)
- Bypass ACL issues when browsing: If access is denied inside V:, browse via the administrative share (applies admin context): \<machine-name>\V$ then copy out required files.
- If ILR still fails, use Volume‑level restore:
In Recover Data → Volume, restore the entire backed‑up volume to an alternate location, then copy needed items. Recommended for large restores or persistent ILR errors. - Agent & prerequisites sanity‑check
- Update MARS from https://aka.ms/azurebackup_agent
- Ensure TLS 1.2 and .NET 4.5.2+
- Re‑register with fresh vault credentials if registration is stale.
- ILR is designed for smaller restores, large copies should use Volume mode.
- The timeout change and AV exclusions directly address the “mount succeeds but browse fails/invalid parameters”
Thanks,
Suchitra.
- Extend ILR session timeout\ Set the DWORD
-
Suchitra Suregaunkar • 1,880 Reputation points • Microsoft External Staff • Moderator
2025-10-23T17:32:47.3533333+00:00 Hello Focagem Soluções de Gestão
Kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out.
Thanks,
Suchitra.
Sign in to comment