File-level restore is disabled for a Windows VM restore point in Veeam

Issue/Introduction

Source and classification

• Source: Veeam integration support cases and internal reproduction.
• Classification: VM metadata configuration; some older API Proxy batch-backup scenarios might also have a compatibility issue.
• Confirmation basis: When the platform OS type was only generic Windows, Veeam did not recognize new restore points for Windows file-level restore. Selecting the actual version, such as Windows Server 2019, and creating a new backup enabled it.
• Internal tracking: No related Jira.

Issue metadata

• Issue ID: None.
• Component/product: ZSphere, Cloud, Veeam API Proxy, and Veeam Backup & Replication.
• Status: Main scenario has a resolution.
• Priority/severity: General.
• Confirmed environment: Cloud 5.4.8, Veeam 12, and API Proxy 1.0.x; check the same OS-type metadata for ZSphere integration.
• First fixed version: OS metadata needs no code fix. A later 1.0.3 followed up the older batch-backup compatibility issue; use its release notes for support scope.
• Confirmation date: July 6, 2026.
• Last updated: September 1, 2026.

Problem description

After backing up a Windows VM on ZSphere or Cloud, Veeam might disable file-level restore for its restore point even though the source actually runs Windows.

The main confirmed cause is a generic Windows OS type, or missing/inaccurate version metadata after migration. Veeam uses platform metadata to classify the guest when creating the restore point. Backup can succeed while file-level restore remains unavailable.

Changing platform OS type affects only future restore points. Existing guest-classification data does not update, so create a new backup after correction.

An older API Proxy with Veeam 12 also showed a multi-VM batch-backup compatibility issue. If OS type is correct, inspect version and backup mode.

Symptoms

• Windows VM backup succeeds, but file-level restore is disabled.
• Multiple Windows VMs from one batch cannot use it.
• Veeam does not classify the restore point as Windows or offers only whole-VM/disk recovery.
• The source runs Windows, but the platform says only Windows rather than Windows Server 2019, for example.
• Migrated VMs more often retain generic, absent, or inaccurate types.
• After selecting the actual Windows version and backing up again, a new restore point enables file-level restore.

Site screenshot

Impact

• Individual files/folders cannot be restored through Veeam.
• Whole-VM, disk, or other recovery might be required, increasing time and impact.
• A disabled action does not mean backup failure or damaged data.
• Changing the VM operating system type does not repair existing restore points; a new backup is required for verification.
• Guest network/credentials can affect later writeback but are a different stage from action enablement.

Environment

• Products: ZSphere, ZStack Cloud, and Veeam Backup & Replication.
• Product line: ZVF and Cloud-related Veeam integration.
• Components: VM OS metadata, Veeam API Proxy, and Veeam file-level restore.
• Confirmed environment: Cloud 5.4.8, Veeam 12, API Proxy 1.0.x.
• Trigger: Generic, missing, or inaccurate Windows OS type; some older API Proxy multi-VM batch scenarios might also trigger it.