8 Krypton

VSS Backups not working after Windows 10 creators update 1709

Jump to solution

Hello everyone,

just wondering whether anyone else has experienced problems with Avamar VSS Backups of Windows 10 clients since the creators update (1709) was rolled out.

I have a relatively new Win10 Client. Backups of Filesystem and VSS were working fine until the creators update was installed a couple of weeks ago. Now the VSS backups fail after 30 seconds. This is happening on all Windows 10 clients (Professional) with this update.

Error code is 10007

Filesystem backups are still working fine. But the System State backups are no longer working.

In the logfiles I see this:

2017-11-28 20:00:25 avvss Info <16480>: EFI system detected. ASR BCD will not be included in shadow copy

2017-11-28 20:00:25 avvss Info <19014>: Determining best VSS provider for volume 'c:\'

2017-11-28 20:00:25 avvss Info <40027>: Volume c:\ will be frozen by 'Microsoft Software Shadow Copy provider 1.0' in Snapshot {a38bcfd5-e1d9-4341-aedb-e9f403391672}

2017-11-28 20:00:25 avvss Info <8776>: Freezing volumes now...

2017-11-28 20:00:25 avvss Info <8780>: Creating the shadow copy set (DoSnapshotSet) ...

2017-11-28 20:00:28 avvss Error <10975>: ERROR: Selected writer 'ASR Writer' is in failed state!

   - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

   - Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

   - Writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   - Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <10976>: ERROR: Selected writer 'ASR Writer' reported an error!

   - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

   - Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

   - Writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   - Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <12077>: VSS returned an error message exiting HR = 0x8000ffff

2017-11-28 20:00:28 avvss Info <0000>: Finished with backup. Performing cleanup.

The text in German above translates to:

The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer

Avamar Version 7.3.1-125 (Server & Client)

I've already tried rebooting the clients.

Just after the backup fails, I ran vssadmin list writers. It showed the ASR Writer in a failed state. But after a while the writer returns to a stable state.

Any ideas?

Thanks and regards,

Stephen

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

Looks like Microsoft fixed the problem.

KB4058258 was released on Jan 31. Since this was installed on my laptop VSS Backups are working again.

Check the Build Version of Windows. 16299.214 ist the latest version.

I had build 16299.192 on my laptop before Windows Update ran this morning.

I just confirmed this on a colleague's laptop. Half an hour ago I ran a backup, the VSS backup failed as usual. Then Windows Update was run, this KB patch was installed and the laptop rebooted. Started the backup just now and it's running fine.

0 Kudos
5 Replies
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

The error message that corresponds with code 0x800423f0 is:

The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer.

(see Troubleshoot VSS issues that occur with Windows Server Backup (WBADMIN) in Windows Server 2008 and W...

This suonds like a software bug on one side or the other. Does this client have more than one volume or is it only the C drive?

However, I have to ask why you're performing System State backups of client systems. This seems like something that would provide incredibly poor return on investment time-wise. If a client blows up, most shops just re-image the OS and perform a filesystem restore.

0 Kudos
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

Thanks for answering, Ian.

There is only drive C: involved here.

System State Backups were implemented before I got here, we've even used them for an occasional full restore.

I'm also considering upgrading Avamar AVE to 7.4 (maybe even 7.5).

Also found this thread with similar problems:

https://social.technet.microsoft.com/Forums/en-US/9713fde2-e4ea-451c-864b-cc2c441c2c91/asr-writer-er...

Thanks,

Stephen

0 Kudos
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

According to the compatibility guide, Windows 10 BMR is supported in Avamar 7.3. If you feel that this is worth troubleshooting further, I'd recommend opening a service request.

Upgrading the Server software on the AVE will not change the behaviour of the client but you could always install the 7.4.1 or 7.5.0 plugin catalog and try upgrading the client software on one of the affected systems to see if that resolves the problem.

0 Kudos
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

In the meantime there is a KB about this:

515720 : Avamar VSS backups fail with a ASR writer error after upgrading Windows 10 to build 1709 (Fall Creators Update)

https://support.emc.com/kb/515720


Avamar Engineering are aware of this issue and have confirmed that the new build 1709 "Fall Creators Update" will be reviewed via Bug 293042

0 Kudos
8 Krypton

Re: VSS Backups not working after Windows 10 creators update 1709

Jump to solution

Looks like Microsoft fixed the problem.

KB4058258 was released on Jan 31. Since this was installed on my laptop VSS Backups are working again.

Check the Build Version of Windows. 16299.214 ist the latest version.

I had build 16299.192 on my laptop before Windows Update ran this morning.

I just confirmed this on a colleague's laptop. Half an hour ago I ran a backup, the VSS backup failed as usual. Then Windows Update was run, this KB patch was installed and the laptop rebooted. Started the backup just now and it's running fine.

0 Kudos