Veeam Hyper-V backups and Windows Server 2012 R2 Update KB 2919355

Veeam Backup & Replication
Last Modified:


Installing the KB2919355 update (April 2014 rollup) on Hyper-V 2012R2 introduces two separate issues:

First issue impacts backup of VMs with Windows OS versions supporting Auto Recovery functionality (Windows 2008R2 and later only) from updated Hyper-V 2012 R2 hosts. Backup of such VMs fails with the following error message:

Processing VMNAME Error: Client error: The system cannot find the file specified.
Failed to open file [\\?\Volume … AutoRecovery.avhdx] in read only mode.

Second issue impacts the entire VM restore of VMs with Windows OS version not supporting Auto Recovery functionality (Windows 2008 and earlier only), if the backup was done from updated Hyper-V 2012 R2 host. Granular recovery options work fine, but the entire VM restore fails with the following error if the backup was done from the updated Hyper-V 2012R2 host:

Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_POST_RESTORE'


Issue 1: After installing the update, Hyper-V starts to return AutoRecovery.avhd(x) path without trailing backslash that is expected by our code.
Issue 2: Under the hood changes of snapshot file naming for guest OSes not supporting Auto Recovery functionality.


This issue is corrected in version Please apply Patch 4 to your Veeam Backup & Replication v7 installation to resolve this issue.

Rate the quality of this KB article: 
4.5 out of 5 based on 49 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: