Restore issue on Server 2025

Jonathan 380 Reputation points
2026-08-29T07:09:41.1366667+00:00

Hi,

How to resolve the issue below? Which is the best way to restore the backup of OS on server 2025?

User's image

Windows for business | Windows Server | Performance | Application technologies and compatibility

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 1,385 Reputation points Microsoft External Staff Moderator
    2026-08-31T05:17:13.49+00:00

    Welcome to Microsoft Q&A!

    Thank you for providing the screenshot and detailed information.

    Based on the error message shown, this behavior is expected when using Volume Recovery to restore a volume that contains operating system components:

    "You cannot perform a volume recovery because all destination volumes contain operating system components..."

    This occurs because Windows Server Backup detects that the destination volume contains the currently installed operating system and prevents the restore operation from overwriting active OS files. For operating system recovery scenarios, this is a recommendation using System State Recovery or Bare Metal Recovery (BMR) instead.

    1. If you only need to restore Windows configuration components

    Use System State Recovery:

    wbadmin start systemstaterecovery

    System State Recovery restores operating system configuration components such as the registry, boot files, Active Directory (if applicable), and other system state data.

    2. If you need to restore the entire operating system

    Use Bare Metal Recovery (BMR) from the Windows Recovery Environment (WinRE) or by booting from Windows Server 2025 installation media.

    • Boot into WinRE or start from the Windows Server installation media.
    • Select Repair your computer.
    • Choose System Image Recovery.
    • Restore the server using the available backup image.

    Bare Metal Recovery is the recommended approach when recovering a failed operating system or restoring the entire server to a previous state.

    3. Why the restore fails

    The Recovery Wizard is currently attempting a Volume Recovery operation while all available destination volumes contain operating system components. Windows Server Backup does not allow an online restore that would overwrite the active system volume.

    Instead, you should:

    • Use Files and Folders Recovery if only data files need to be restored.
    • Use System State Recovery for operating system configuration recovery.
    • Use Bare Metal Recovery (BMR) from WinRE for a full operating system restore.

    For additional information, please refer to the following Microsoft documentation:

    Restore System State to a Windows Server - Azure Backup | Microsoft Learn

    Add-WBBareMetalRecovery (WindowsServerBackup) | Microsoft Learn

    System state and bare-metal recovery protection for Azure Backup - Azure Backup | Microsoft Learn

    Back up system state and bare metal | Microsoft Learn

    Windows Server Backup Feature Overview | Microsoft Learn

    If the answer is helpful, please click Accept Answer.

    Thank you for using Microsoft Q&A.

    Was this answer helpful?

  2. AI answer

    2026-08-29T07:10:02.94+00:00

    For Windows Server 2025, the supported restore path depends on what was backed up:

    • For System State restore, use Windows Server Backup and point it to the folder that contains the backup.
    • For full OS / bare metal recovery, use system image recovery from Windows Recovery and restore from a network share if needed.

    For the error shown:

    ERROR - The specified backup was not found.

    the command must use the exact backup target and version identifier returned by wbadmin get versions.

    Use this sequence:

    1. On the server to recover, open an elevated Command Prompt.
    2. Run: 
         wbadmin get versions -backuptarget:\\<servername>\<sharename>
    3. Copy the version identifier exactly as returned.
    4. Start the System State recovery with that exact version and backup target: 
         wbadmin start systemstaterecovery -version:<versionidentifier> -backuptarget:\\<servername>\<sharename>
    5. Confirm the recovery, let it complete, and then restart the server.

    If the backup is being restored through the Windows Server Backup UI instead of command line:

    1. Open Windows Server Backup.
    2. Select Local Backup.
    3. In Actions, select Recover.
    4. Select A backup stored in another location.
    5. If the backup is on another server, select Remote shared folder. If local, select Local drives.
    6. Point to the WindowsImageBackup directory.
      • Remote example: \\MyFileServer\MyFolder\WindowsImageBackup
      • Local example: D:\WindowsImageBackup
    7. Continue the wizard and choose the recovery type.

    Important checks for the “backup not found” error:

    • The share path must be the correct backup target.
    • The version identifier must exactly match the output of wbadmin get versions.
    • For Windows Server Backup discovery, the backup files must be under the WindowsImageBackup folder.
    • If using a local drive, the WindowsImageBackup folder must be at the root of a non-critical volume.

    If the goal is to restore the entire OS rather than only System State, use system image recovery:

    1. Boot into System Recovery Options.
    2. Select Restore your computer using a system image that you created earlier.
    3. Select Select a system image > Advanced > Search for a system image on the network.
    4. Enter the share path and credentials.
    5. Select the recovery point.
    6. Select Format and repartition disks.
    7. Select Finish to begin restore. A restart is required.

    For Exchange or SQL Server scenarios with OS damage, the documented supported option is System State or BMR restore, while lost application data requires the application-aware backup path instead of System State alone.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.