- Veeam Support Knowledge Base
- Veeam Recovery Media creating fails with "This access control list is not in canonical form and therefore cannot be modified" error
Veeam Recovery Media creating fails with "This access control list is not in canonical form and therefore cannot be modified" error
| KB ID: | 3026 |
| Product: |
Veeam Backup & Replication Veeam Agent for Microsoft Windows |
| Published: | 2019-10-18 |
| Last Modified: | 2022-03-08 |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
During a Veeam Agent for Microsoft Windows backup job the following warning occurs:
Collecting recovery media files Details: This access control list is not in canonical form and therefore cannot be modified.
The warning may appear in the following cases:
- Veeam Recovery Media is created as an independent process (the process will fail with an error)..
- Veeam Recovery Media is created as a part of the server backup performed using the Veeam Agent backup job managed by agent.
Cause
During the creation of Veeam Recovery Media a temporary subfolder is created under C:\Windows\Temp. In some cases, the Access Control List (ACL) on that folder may affect Veeam operations.
Solution
Use the following registry setting on the machine being backed up by Veeam Agent for Microsoft Windows to change where the Recovery Media Temp folder should be created.
- Create this Registry Value on the machine where Veeam Agent for Microsoft Windows is running.
Key Location: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup
Value Name: RecoveryImageTempPath
Value Type: String Value
Value Data: <path to unpack WinRE>
For the Value Data, specify a path where Veeam Agent for Microsoft Windows can temporarily unpack the WinRE (e.g., C:\Temp). The registry value changes the temporary path for the WinRE image unpacking. This registry value does not affect any OS variables or settings. - Restart the Veeam Agent for Microsoft Windows service.
- Rerun the job.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.