Bare Metal Recovery Fails With "The requested security package does not exist."
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Oops! Something went wrong.
Please, try again later.
Article Applicability
The issue documented in this article occurs with Server 2022 deployments created using a Server 2022 ISO created before September 2023. This issue was fixed in the Server 2022 ISO released by Microsoft after September 2023.
Challenge
Bare Metal Restore from Veeam Recovery Media created using Server 2022 fails with the error:
Restored failed: The requested security package does not exist
Cause
The issue is caused by one of the modules in WinRe.wim, which is used for Veeam Recovery Media creation.
Solution
Please use one of the following workarounds:
Option 1: Use Recovery Media created using a newer deployment of Server 2022.
- The new Recovery Media must be from a machine that has Windows Server 2022 installed using ISO that was dated September 2023 or later.
- Visual Studio Subscriptions - Downloads & Keys (under version, select "updated Sep 2023" or later)
Option 2: Use Recovery Media created using a machine running Server 2019.
- [Critical!] During the Bare Metal Restore, on the 'Backup Location' tab, click "Load Driver" and uncheck the option "Inject these drivers into operating system while performing bare metal recovery."
More Information
OS-Level Workaround
Although the workarounds provided in the Solution section of this article are valid and functioning, we understand that some customers may prefer to address the OS-level issue that prevents the recovery media from being generated correctly. With that in mind, we offer the following workaround as a courtesy to ensure our solutions are comprehensive. This workaround has been tested and confirmed to be functional. However, please note that because it involves OS-level modifications, it falls outside the scope of Veeam Support, and we are unable to assist with its implementation.
Advanced Workaround: Update WinRE.wim on Original Machine and Recreate Recovery Media
This workaround is very advanced and involves modifications to the partition layout. It also requires access to the original Server 2022 machine. If that machine is no longer available, use one of the other two options.
- Delete the Recovery Partition
- Recreate the Recovery Partition following instructions in "Scenario 2: Create a New Recovery Partition" on KB2685.
- Download Windows Update package KB5031364 for 21H2 from https://www.catalog.update.microsoft.com/Search.aspx?q=KB5031364
- Apply the update to WinRE as per https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#apply-the-update-to-a-running-pc
- Recreate Veeam Recovery Media
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.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.