Host: W2K12R2 fully patched (Hyper-V Role)

After adding a third IDE-disk to a running W2K8R2 (NTDS role) Guest Backups are failing (during backup for each disk there's a scsi disk mounted, vss-snapshot, that cannot be recognized, question to format this disk).

To narrow it I installed windows backup onto the guest trying to backup systemstate. After cleaning all vss isues, e.g. restarting the server all writers are stable.

Then doing the systemstate backup:
Errorcode 2155347997

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" /><EventID>5</EventID><Version>2</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x4000000000000000</Keywords><TimeCreated SystemTime="2014-08-20T15:53:37.620830700Z" /><EventRecordID>34</EventRecordID><Correlation /><Execution ProcessID="5836" ThreadID="5448" /><Channel>Microsoft-Windows-Backup</Channel><Computer>EPHDB01.eph.lokal</Computer><Security UserID="S-1-5-18" /></System>
- <EventData><Data Name="BackupTemplateID">{282BD563-28CE-4300-9491-8486A49A4018}</Data><Data Name="HRESULT">2155347997</Data><Data Name="BackupState">12</Data><Data Name="BackupTarget">\\eph-server\eph-backup\ephdb01</Data><Data Name="NumOfVolumes">3</Data><Data Name="BackupTime">2014-08-20T15:53:16.428587900Z</Data><Data Name="HRESULT2">2155347997</Data><Data Name="VolumesInfo"><VolumeInfo><VolumeInfoItem Name="Z:" OriginalAccessPath="Z:" State="7" HResult="-2139619299" DetailedHResult="0" PreviousState="15" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="1" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="550" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="F:" OriginalAccessPath="F:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="548" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1572" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo></Data><Data Name="DetailedHRESULT">3225026565</Data><Data Name="SourceSnapStartTime">2014-08-20T15:53:16.397337900Z</Data><Data Name="SourceSnapEndTime">2014-08-20T15:53:32.666187700Z</Data><Data Name="PrepareBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="PrepareBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="BackupWriteStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="BackupWriteEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="DVDFormatStartTime"><TimesList></TimesList></Data><Data Name="DVDFormatEndTime"><TimesList></TimesList></Data><Data Name="MediaVerifyStartTime"><TimesList></TimesList></Data><Data Name="MediaVerifyEndTime"><TimesList></TimesList></Data><Data Name="BackupPreviousState">16</Data><Data Name="ComponentStatus"><ComponentStatus></ComponentStatus></Data><Data Name="SSBEnumerateStartTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SSBEnumerateEndTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SSBVhdCreationStartTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SSBVhdCreationEndTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SSBBackupStartTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SSBBackupEndTime">1601-01-01T00:00:00.000000000Z</Data><Data Name="SystemStateBackup"><SystemState IsPresent="1" HResult="-2139619299" DetailedHResult="-1069940731" /></Data><Data Name="BMR">false</Data><Data Name="VssFullBackup">true</Data><Data Name="UserInputBMR">false</Data><Data Name="UserInputSSB">true</Data><Data Name="BackupSuccessLogPath" /><Data Name="BackupFailureLogPath" /><Data Name="EnumerateBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="EnumerateBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="PruneBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data><Data Name="PruneBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data></EventData></Event>

thx for any reply,

Ralf

I have a fresh server with Windows Server 2008 R2 x64 installed. Right after I installed the OS, I installed Windows Server Backup and ran one back up successfully. Since then, I've promoted the server to an Active Directory Domain controller. I'm no longer able to run Windows Server Backup successfully. 

• I've installed all available "Update for Windows Server 2008 R2 x64" updates (not any of the security ones)
• In device manager all the attached hardware have drivers set up successfully
• The secondary hard drive where I am trying to store the backup has 580 GB free space. The server's entire primary partition is only 460 GB.
• The server's system partition status (where the OS is installed) is showing "System, Boot, Page File, Active, Crash Dump, Primary Partition"
• I've uninstalled and re-installed Windows Server Backup
• I have rebooted the server, and restarted the VSS service multiple times
• When running Windows Server Backup, I choose only "Bare Metal Recovery"
• I've tried both "VSS full backup" and "VSS copy backup" with no success
• When I try to backup a single 1kb file, that fails with the same error

In the Windows Application logs I see the following errors when I attempt to do a backup:

• lsass (508) Unable to read the header of logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\Windows\NTDS\edb.log. Error -546.
• lsass (508) Unable to read the header of logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\Windows\NTDS\edb.log. Error -546.

• A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
  the error is likely to reoccur.
  . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
  
  Operation:
     PostSnapshot Event
  
  Context:
     Execution Context: Writer
     Writer Class Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
     Writer Name: NTDS
     Writer Instance ID: {87905f79-f053-4e86-be8f-3de48ca8c45a}
     Command Line: C:\Windows\system32\lsass.exe
     Process ID: 508

• Ran out of time while deleting files. 
  
  Operation:
     OnPostSnapshot event
     PostSnapshot Event
  
  Context:
     Execution Context: Shadow Copy Optimization Writer
     Execution Context: Writer
     Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
     Writer Name: Shadow Copy Optimization Writer
     Writer Instance ID: {74ae0f52-b772-41ab-8c76-a1b6e88d2ea2}

• The backup operation that started at '‎2014‎-‎08‎-‎22T03:02:33.924000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

When I go to command prompt (as Administrator) and run "vssadmin list writers" I get the following:

• C:\Windows\system32>vssadmin list writers
  vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
  (C) Copyright 2001-2005 Microsoft Corp.
  
  Writer name: 'Task Scheduler Writer'
     Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
     Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'VSS Metadata Store Writer'
     Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
     Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'Performance Counters Writer'
     Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
     Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'System Writer'
     Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
     Writer Instance Id: {2d3499e5-9673-4180-87f7-acc961121da9}
     State: [5] Waiting for completion
     Last error: No error
  
  Writer name: 'ASR Writer'
     Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
     Writer Instance Id: {dbc3ada5-4daa-4d35-8657-8048d2685d94}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'COM+ REGDB Writer'
     Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
     Writer Instance Id: {0eda058c-e7bf-4671-8b41-0fe4b9ff4f81}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'Registry Writer'
     Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
     Writer Instance Id: {f9d3c5dd-4cb3-44fd-bdc1-21677e22020b}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'Shadow Copy Optimization Writer'
     Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
     Writer Instance Id: {8fa5f71f-53d7-48d0-b69d-17e3c8427063}
     State: [1] Stable
     Last error: No error
  
  Writer name: 'WMI Writer'
     Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
     Writer Instance Id: {1d745cdc-7de1-47f9-84d7-38369e695fe2}
     State: [5] Waiting for completion
     Last error: No error
  
  Writer name: 'DFS Replication service writer'
     Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
     Writer Instance Id: {29bbb620-1922-4f68-9ed5-6b7005f0f3b3}
     State: [5] Waiting for completion
     Last error: No error
  
  Writer name: 'NTDS'
     Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
     Writer Instance Id: {87905f79-f053-4e86-be8f-3de48ca8c45a}
     State: [11] Failed
     Last error: Non-retryable error

Server information:

• Processor: i5-3570k
• RAM: 16 GB
• System type: 64-bit
• Active Directory Domain Services role installed
• DNS Server role installed

Hi folks,

We are running into issues when attempting to configure a Windows Backup schedule through either running the Backup Schedule wizard or through using the wbadmin utility. While I have previously posted this issue on a separate forum (with no luck) I’ve restructured this description based on the responses received and am also hoping that this a more suitable forum for the problem we are experiencing.

On running the backup wizard the backup configuration screen shows the backup size to be 0KB for the Full Server option or if I choose ‘Custom’ and go to ‘select backup items’ the volume list is empty. However the later ‘select destination disk’ screen of the wizard lists all of the disks attached to the server along with the associated volume letters (via clicking the ‘Show All Available Disks’ option).

On the backup wizard reaching the summary stage it then proceeds to format the destination disk. On completion of this format the wizard status then changes to ‘Creating backup schedule’ at which point it then fails with the message “The specified number of volumes is invalid”.

Equally running the following wbadmin command:

wbadmin ENABLE BACKUP -addtarget:{81737a1c-0000-0000-0000-000000000000} -schedule:21:00 -include:c:

Results in the following error:

“ERROR - One of the source volumes specified cannot be included: c: Please specify source as a volume drive letter or access path (if volume is mounted in a folder). Only volumes on locally attached disks can be backed up.”

The server is a Dell PowerEdge R620 running Windows server 2008SP2 and is operating as expected other than for this windows back issue. Everything appears as normal when I view the disks within the Disk Management Console. Backups used to run on this server fine before it was migrated from old hardware to new hardware using Doubletake Move. Everything else is running fine since the migration apart from Windows backup so not why it would only be effecting Windows backup. I have also ran the wbadmin ‘delete catalog’ command to remove reference to the previous backups that were taken.

Is there any other tests that I can run to determine why Windows backup is having trouble seeing the available volumes at the 'Select Backup items' stage but not at the Select Destination' stage? Any help or pointers in the right direction would be very much appreciated.

Thanks,

Niall

I have a new Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system state wasn't getting backed up.
 
Then I would run "vssadmin list writers" from CMD and system writer would be timing out....
 
Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6}
    State: [7] Failed
    Last error: Timed out
 
I would also get Event ID 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} - 0000000000000140,0x0053c020,00000000003BDFD0,0,00000000003BBFA0,4096,[0]).  hr = 0x80070057, The parameter is incorrect.
 
I would also get Event ID 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
 
Also event ID 22 for volsnap The shadow copy storage volume specified for shadow copies on volume\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} could not be added.
 
Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies.

PLEASE HELP!

Błąd podczas zapisu przy tworzeniu kopii zapasowej pliku F:\System Volume Information\SRM\quota.md: błąd [0x80070020] Proces nie może uzyskać dostępu do pliku, ponieważ jest on używany przez inny proces.
Błąd podczas zapisu przy tworzeniu kopii zapasowej pliku G:\System Volume Information\SRM\quota.md: błąd [0x80070020] Proces nie może uzyskać dostępu do pliku, ponieważ jest on używany przez inny proces.
Błąd podczas zapisu przy tworzeniu kopii zapasowej pliku E:\System Volume Information\SRM\datascrn.md: błąd [0x80070020] Proces nie może uzyskać dostępu do pliku, ponieważ jest on używany przez inny proces.
Błąd podczas zapisu przy tworzeniu kopii zapasowej pliku E:\System Volume Information\SRM\quota.md: błąd [0x80070020] Proces nie może uzyskać dostępu do pliku, ponieważ jest on używany przez inny proces.

Hi! 

I have a following error while doing scheduled backups: "Failure while compacting the virtual disk on the backup location"OS is Server 2012 R2 Essential 

I use a dedicated HDD for backups. Its a WD GREEN 3TB. 

Any suggestions? 

LOGS:

• EROOR: The backup operation that started at '‎2014‎-‎06‎-‎27T00:57:25.744931200Z' has failed with following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
• WARNING: The backup operation that started at '‎2014‎-‎06‎-‎26T16:30:31.944377600Z' has completed with errors. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

I am working with a client who is attempting to backup to a NAS device 
The device is a linksys NSS6000 (Cisco device).

It’s a dual 1Gbit LAN device that supports CIFS / FTP and NFS transfers. It has only 1Gbit lan connected.
The device has 4 *  500 gb sata drives in raid 1  attached.
Cables go from cat 5 to fiber back to cat5. (The NAS  is located at a neighboring office) The switches are 1gbit.

Server is a win2k8r1 fully up to date.

When backing up to the NAS device, the following error occurs:

Running backup of volume Local Disk(D:), copied (86%).
Running backup of volume Local Disk(D:), copied (90%).
Running backup of volume Local Disk(D:), copied (94%).
Running backup of volume Local Disk(D:), copied (98%).
Backup of volume Local Disk(D:) completed successfully.

Backup stopped before completing.

Summary of backup:
------------------

I'm getting the following error:

Log Name:   Microsoft-Windows-Kernel-EventTracing/Admin
Source:    Microsoft-Windows-Kernel-EventTracing
Date:     5/17/2010 11:04:48 AM
Event ID:   2
Task Category: Session
Level:     Error
Keywords:   Session
User:     ****
Computer:   ****
Description:
Session "WbadminInBuiltTracing" failed to start with the following error: 0xC0000035
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" /><EventID>2</EventID><Version>0</Version><Level>2</Level><Task>2</Task><Opcode>12</Opcode><Keywords>0x8000000000000010</Keywords><TimeCreated SystemTime="2010-05-17T18:04:48.898886000Z" /><EventRecordID>45</EventRecordID><Correlation /><Execution ProcessID="4816" ThreadID="2800" /><Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel><Computer>****</Computer><Security UserID="****" /></System><EventData><Data Name="SessionName">WbadminInBuiltTracing</Data><Data Name="FileName"></Data><Data Name="ErrorCode">3221225525</Data><Data Name="LoggingMode">2</Data></EventData></Event>

Does anyone know what this is or how to prevent it from occurring?

I'm running Windows Server 2008 R2.

Thanks much,
James

We're doing nightly BMR backups of a small 2012 R2 Hyper-V host via wbadmin to 2TB USB disks, via
  wbadmin start backup -backupTarget:z: -quiet -noverify -vssFull -include:e:,c: -allCritical
(where E: contains the sole VM).

We are using the same backup system on other similar Hyper-V hosts running 2008 R2 and 2012, with no problems. However, with this 2012 R2 host, after a few months of no problems the backups started failing with:
  There is not enough free space on the backup storage location to back up the data.

This made no sense, and continues to make no sense:

• The 2TB backup disks are only half full (>1TB free), with 600GB of unallocated shadowstorage.
• There should be room for many more backups on these disks. Each currently contains 11 to 13 backups, with the initial full backup having required about 600GB and each subsequent backup only requiring another 20GB to 40GB.
• There is over 40GB free on the C: drive and 300GB free on the E: drive; free space on the host volumes is not an issue.
• Increasing the shadowstorage limit on the backup disks to unbounded doesn't resolve the issue.
• This is not a problem of a RECOVERY partition that's too small, and SystemState backups always complete successfully.

The first workaround we found was to temporarily reduce (not increase) the shadowstorage allocation on the E: drive (containing the VM) and then increase it back (with the end result of deleting old shadow copies).

This worked reliably, but looking for a root cause led us to uninstall the Windows Updates installed mid-September (in particular the Aug 2014 and Sep 2014 roll-ups), which preceded the start of this problem. But instead of resolving the problem the uninstalls made it worse, in that our workaround stopped working.

We reinstalled the Windows Updates, and then tried setting backup performance to normal, in case the problem was related to VSS on the host volumes, but the errors continued.

At this point the only way we've found to work around the error is to delete 1 or 2 of the oldest backups on the destination disk, via
  wbadmin delete backup -backupTarget:z: -deleteOldest
after which the new backup will succeed.

But, again, this makes no sense, as the destination disks are only half full, and even if space was an issue wbadmin should delete old backups as required. And this same system is working fine on 2008 R2 and 2012.

Any suggestions?

Thanks,

John

Host Server, 2012 R2 Data Center (latest updates)

Virtual Machine, 2012 R2 Essentials (latest updates)

Problem occurs when attempting to do (either in WSB GUI or PowerShell) "child VM snapshot" backup and fails with Backup Event ID 521, "A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information.  Detailed error: The operation ended before completion."

JobType          : Backup
StartTime        : 11/24/2014 10:52 PM
EndTime          : 11/24/2014 10:52 PM
JobState         : Completed
CurrentOperation :
HResult          : 807800A1
DetailedHResult  : 8078001D

Integration Services are... integrated and the VM has the necessary components.  However, it just does not make the VSS snapshot, it sits for a few seconds and terminates with the above error and the following event logged:

- System
  - Provider
   [ Name]  Microsoft-Windows-Backup
   [ Guid]  {1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}

   EventID 521
   Version 2
   Level 2
   Task 0
   Opcode 0
   Keywords 0x8000000000000000

  - TimeCreated
   [ SystemTime]  2014-11-25T04:52:40.567308700Z
   EventRecordID 4850
   Correlation

  - Execution
   [ ProcessID]  4848
   [ ThreadID]  5016
   Channel Application
   Computer thehostcomputername
  - Security
   [ UserID]  S-1-5-18
  - EventData

  BackupTime 2014-11-25T04:52:35.410000000Z
  ErrorCode 0x807800a1
  ErrorMessage %%2155348129

The following is the script I use to build the backup job:

# Windows Server Backup - PowerShell
#
# FileSpec for VM
#$VMFile = New-WBFileSpec -FileSpec 'F:\HyperVMs\VM\VM-001\vm001.vhdx'

#get VM Host Components
$VMHostComponent = Get-WBVirtualMachine | ?{$_.VMName -eq 'Host Component'}

#get VM object for backup
$VMTarget = Get-WBVirtualMachine | ?{$_.VMName -eq 'VM-001'}

#Set Backup Disk
$WBDisk = Get-WBDisk | ?{$_.DiskNumber -eq '4'}

#create backup target
$BackupTarget = New-WBBackupTarget -Disk $WBDisk -PreserveExistingBackups $true

#Create a policy
$WBPolicy = New-WBPolicy

#Set Schedule
Set-WBSchedule -Policy $WBPolicy -Schedule 06:00 #6am

#add backup target to policy
Add-WBBackupTarget -Policy $WBPolicy -Target $BackupTarget -Force

#add vms to policy
Add-WBVirtualMachine -Policy $WBPolicy -VirtualMachine $VMTarget
Add-WBVirtualMachine -Policy $WBPolicy -VirtualMachine $VMHostComponent

#adjust policy for VSS FullBackup
Set-WBVssBackupOptions -Policy $WBPolicy -VssFullBackup

#add filespec to policy
#Add-WBFileSpec -Policy $WBPolicy $VMFile

#set policy
Set-WBPolicy -Policy $WBPolicy

#start backup
Start-WBBackup -Policy $WBPolicy

I've remarked using FileSpec from the above script, which oddly enough actually works when enabled and commenting out the actual virtual machine addition to the policy.. which I thought was suppose to do the 'hot backup' or child vm snapshot.

Just a couple notes, the virtual disk is a differencing disk placed in a separate volume from the parenting vhd.  Is this a problem?  It doesn't seem to be one when I use FileSpec and grab the VM without the use of integration services.  I can actually watch the host build the temporary snapshot of the volume which retains the differencing VHD and when the backup is complete it is removed.

It is just trying to get integration services to make the hot backup causing problems.  Am I missing something from the policy or is there something obscure in the VM that needs to be checked?  I looked at the volumes within the virtual machine, and there is plenty of space available for VSS and the hosting volume does too...

I have a brand new 2008R2 SP1 server (Domain Controller) where I try to make SystemState backup. Backup seems to work fine, but I can not delete oldest.
I'm uncertain if I do have a valid SS backup.

I take backup with this command:

C:\>wbadmin start systemstatebackup -backuptarget:D:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Starting to back up the system state [04-08-2011 08:45]...
Retrieving volume information...
This will back up the system state from volume(s) Local Disk(EFI System Partitio
n) (200.00 MB),C-OS(C:) to D:.
Do you want to start the backup operation?
[Y] Yes [N] No y

Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Windows Server Backup is updating the backup for deleted items.
This might take a few minutes.
Found (96) files.
Found (13207) files.
Found (29482) files.
Found (39566) files.
Found (78588) files.
Found (79088) files.
The search for system state files is complete.
Starting to back up files...
The backup of files reported by 'Task Scheduler Writer' is complete.
The backup of files reported by 'VSS Metadata Store Writer' is complete.
The backup of files reported by 'Performance Counters Writer' is complete.
Overall progress: 1%.
Currently backing up files reported by 'System Writer'...
 - continuing to 100% -

Summary of the backup operation:
------------------

The backup of the system state successfully completed [04-08-2011 08:59].
Log of files successfully backed up:

--------------------------------------------------------------------------------------------

If I check the backup with "Get Versions", I get this:

--------------------------------------------------------------------------------------------

C:\>wbadmin get versions
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Backup time: 30-07-2011 21:00
Backup target: Fixed Disk labeled D:
Version identifier: 07/30/2011-19:00
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {6f4f38c8-3d3c-4e9f-87fb-d7cdb9c13c59}
 - several other backups-

Backup time: 04-08-2011 08:45
Backup target: Fixed Disk labeled D:
Version identifier: 08/04/2011-06:45
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {ae749899-447f-4c6d-b2d3-06c2f1816541}

--------------------------------------------------------------------------------------------

So far everything seems ok.
But when I try to delete the oldest backup, things look weired:

--------------------------------------------------------------------------------------------

C:\wbadmin delete systemstatebackup -deleteOldest
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

--------------------------------------------------------------------------------------------

If I try with -keepversions, I get same result:

--------------------------------------------------------------------------------------------

C:\>wbadmin delete systemstatebackup -keepversions:1
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

-------------------------------------------------------------------------------------------- 

So do I have a valid Systemstate backup ?
And can I trust I can use it to recover if needed, since it says "No system state backups were found" ?
And why can't I delete the oldest backup ?

- Duelund

I'm having trouble backing up one of our servers.

I've tried to take a manual shadow copy, but that fails too.

This is the output from the diskshadow:

DISKSHADOW> set context persistent

DISKSHADOW> set verbose on
istent
DISKSHADOW> add volume C:

istent
DISKSHADOW> add volume \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\

DISKSHADOW> create
me \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.

* Including writer "Task Scheduler Writer":+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":+ Adding component: \PerformanceCounters

* Including writer "SqlServerWriter":+ Adding component: \ASTAREG-APP01\ASTAREG\master
--removed several lines to keep it readable. (approx 1400 lines)+ Adding component: \ASTAREG-APP01\ASTAREG\unit_450

* Including writer "System Writer":+ Adding component: \System Files

* Including writer "ASR Writer":+ Adding component: \ASR\ASR+ Adding component: \Volumes\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}+ Adding component: \Volumes\Volume{21d0911f-a727-11e2-8124-806e6f6e6963}+ Adding component: \Disks\harddisk0+ Adding component: \BCD\BCD

* Including writer "Registry Writer":+ Adding component: \Registry

* Including writer "COM+ REGDB Writer":+ Adding component: \COM+ REGDB

* Including writer "WMI Writer":+ Adding component: \WMI

The last operation failed.
	- Returned HRESULT: 80042302
	- Error text: VSS_E_UNEXPECTED

Output from vssadmin list writers:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.LOCAL>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {1642a445-03f7-47aa-8c2a-026970ffe2a5}
   State: [11] Failed
   Last error: Retryable error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {c7f14ce1-862d-469c-a0f6-4d04f40a6154}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8b7f6ee8-caec-426f-9bb8-a4604676be94}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {31e7e45c-a2d2-444a-9658-08f51e1223c5}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {03f58120-3f0f-4388-8d79-b18780dac432}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {33d15e4b-bf9e-4fd5-a85c-491b55cda09e}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {b048fc99-96a3-4c76-8077-a5e85f34c768}
   State: [1] Stable
   Last error: No error

Hey community,

i`m reading these topics since years. All issues could be resolved so far. But since yesterday i`m really afraid. I think i can`t solve this issue without you specialists.

I´m running a Hyper V (Server 2012 R2 Core) with currently three VM`s on it.
I like to initiate a host based backup with "wbadmin".

The used command ist: wbadmin start backup -backupTarget:B:\ -hyperv:"VMS030"

The VM has three disks: Fast Storage 400gb, Slow Storage 500 GB, Paging on SSD`s 15 gb.
I assigned 30.720 megabytes of RAM to this VM.

The other VM`s are much smaller. The Backup is working on these VM`s without any errors.
Now... what`s special about this VM? The VM is a SBS2011 with Exchange, SQL Server and AD on it.

The wbadmin command fails with

Detaillierter Fehler: FEHLER - Vorgangsfehler im Volumeschattenkopie-Dienst (0x8
00423f4)
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der
Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

I´m looking for a workaround or a fix since hours on different error-ids. But cannot resolve it.
There WindowsServerBackup-Log tells me this:

Fehler des Writers
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
Instanz-ID: "{02FFB0A1-6658-4EBF-A79E-ACD7C00038BB}"
Name des Writers: "Microsoft Hyper-V VSS Writer"
Status des Writers: "8"
Fehlerergebnis: "800423F4"
Anwendungsergebnis: "80004005"
Anwendungsmeldung: "(null)"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Logischer Pfad: "(null)"
   Komponentenergebnis: "800423F4"
   Komponentenmeldung: (null)
       Dateiangabe: "A:\Virtual Machines\\1415E5AA-E823-4586-A84D-CF3DB849E8B4.xml", rekursiv: "0"
       Dateiangabe: "A:\\vms030.vhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin.vhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources.vhdx", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D.xml", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D\*", rekursiv: "0"
       Dateiangabe: "A:\\vms030_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
*-----------------------------*


Anwendungssicherung
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Beschreibung     : Offline\VMS030
   Logischer Pfad: ""
   Fehler           : 80780175
   Fehlermeldung   : Eine Komponente wurde bei der Schattenkopie des Volumes übersprungen.

   Detaillierter Fehler  : 800423F4
   Detaillierte Fehlermeldung : Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

This is the output of Backup Logs in Event Viewer

Die Beschreibung für die Ereignis-ID "5" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

EV_RenderedValue_0,00
2155348041
0
%%2155348041
12
06.12.2014 09:58:00
B:
0
<VolumeInfo></VolumeInfo>
06.12.2014 09:58:00
06.12.2014 09:58:28<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
01.01.1601 00:00:00
01.01.1601 00:00:00<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
19<ComponentStatus><ComponentStatusItem Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppId="HyperV" WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" ConsistencyCheckResult="-2139618955" ConsistencyCheckResultDetailed="-2147212300"/></ComponentStatus><ComponentInfo><ComponentInfoItem WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppName="HyperV" hResult="-2139618955" hDetailedResult="-2147212300" IsFullBackup="1" FullBackupReason="0" Size="0" DataTransferred="0" TotalNoOfFiles="0" /></ComponentInfo>
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00<SystemState IsPresent="0" HResult="0" DetailedHResult="0" /><BMR IsPresent="0" HResult="0" DetailedHResult="0" />
False
False
False
C:\Windows\Logs\WindowsServerBackup\Backup-06-12-2014_09-58-00.log
C:\Windows\Logs\WindowsServerBackup\Backup_Error-06-12-2014_09-58-00.log<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
5<ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="1" SucceededComponents="0" />

Das Handle ist ungültig

And finally the Apps Errorlog from Eventviewer:

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8224" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:


Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "16387" aus der Quelle "SPP" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

Microsoft Hyper-V VSS Writer
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird, tritt der Fehler höchstwahrscheinlich erneut auf. (0x800423F4)
Unbekannter Fehler (0x80004005)

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8229" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0x800423f4, Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.



Vorgang:
   PrepareForSnapshot-Ereignis

Kontext:
   Ausführungskontext: Writer
   Generatorklassen-ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Generatorname: Microsoft Hyper-V VSS Writer
   Generatorinstanz-ID: {02ffb0a1-6658-4ebf-a79e-acd7c00038bb}
   Befehlszeile: C:\Windows\system32\vmms.exe
   Prozess-ID: 1852

Das Handle ist ungültig

Do you guy`s have any clue how i can resolve this?

As i said ... i can backup a few smaller VM`s. Only the "Big one" fails.
I already thought about a disk space issue ... But there is at least 30 % of free space on each disk.

Thank you all!

Hi,

i've setup Windows server Backup on a Windows server 2012 standard (which is a Domain Controler) to do a complete backup on a external hard drive.

During the backup, all go well until system state backup. It fail with the following error in the event log (event id 517) : 0x80070001 (invalid function)

after some research, i found that log :

Version=1
EventType=Windows Server Backup Error
EventTime=130475424208827903
Consent=1
ReportIdentifier=3d8a7e6a-f6a8-11e3-941f-d6db6bcd8e80
Response.type=4
Sig[0].Name=Backup Target Type
Sig[0].Value=3
Sig[1].Name=Operation Type
Sig[1].Value=1
Sig[2].Name=Overall hr
Sig[2].Value=0x80070001
Sig[3].Name=Overall Detailed hr
Sig[3].Value=0x00000000
Sig[4].Name=BMR hr
Sig[4].Value=0x00000000
Sig[5].Name=SSB hr
Sig[5].Value=0x8078001d
Sig[6].Name=Volume Backup hr
Sig[6].Value=0x00000000
Sig[7].Name=Application Backup hr
Sig[7].Value=0x00000000
DynamicSig[1].Name=Version du système
DynamicSig[1].Value=6.2.9200.2.0.0.272.7
DynamicSig[2].Name=Identificateur de paramètres régionaux
DynamicSig[2].Value=3084
FriendlyEventName=Windows Server Backup Error
ConsentKey=Windows Server Backup Error
AppName=Exécutable du service de moteur de sauvegarde en mode bloc Microsoft®
AppPath=C:\Windows\System32\wbengine.exe
ReportDescription=Windows Server Backup Error Report

System State Backup return error 0x8078001d. 

I've google a lot about these errors but nothing concerning Windows Server 2012.

VSS Writers does not show any errors (using vssadmi nlist writers)

No disk error anywhere in the event viewer.

I've also check the "JUNCTION" issue (mostly known in Win 7 and Win server 2008 r2) but none of them are "mounted drive" so ...

I'm really runing out of idea ...

EDIT : 

No updates are applyed to the machine.

will try with updates ...

EDIT :

even with the last Windows updates, i keep get the same error