Windows 8.1 VSS Snapshot of C: fails
I have spent weeks trouble shooting this but haven't found a solution. I'm only backing up C: and D: not the recovery partition as I was getting failures trying to back it up after the upgrade to Windows 8.1 It was working ok for a few weeks and then wouldn't delete old backups, would run the cleanup for 20 hours or so and it still wasn't successful. I blew away all old backups, deleted the backup job and started from scratch. VSS errors again. Anyway, here are the errors and the Snapapi logs if anybody has any thoughts:
--------------------
Log Entry Details
--------------------
Type: Warning
Date and time: 2014-02-12 7:12:25 PM
Backup plan: PCM Full Backup
Task: Incremental backup
Code: 1,098,823(0x10C447)
Module: 16
Owner: James@Main
Message:
Failed to create a snapshot of volume 'C: (\Device\HarddiskVolume4)'.
Additional info:
--------------------
Error code: 50247
Module: 16
LineInfo: 14181c22ef45b0cc
Fields: $module : disk_bundle_vs_38350
Message: Failed to create a snapshot of volume 'C: (\Device\HarddiskVolume4)'.
--------------------
Error code: 9
Module: 0
LineInfo: 2aacb7b2ab852ac
Fields: code : 50, $module : disk_bundle_vs_38350
Message: Unknown status.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8e0
Fields: code : 2147942450, $module : disk_bundle_vs_38350
Message: The request is not supported
--------------------
--------------------
--------------------
Log Entry Details
--------------------
Type: Warning
Date and time: 2014-02-12 7:12:26 PM
Backup plan: PCM Full Backup
Task: Incremental backup
Code: 4,195,020(0x4002CC)
Module: 64
Owner: James@Main
Message:
Failed to take a VSS snapshot.
Additional info:
--------------------
Error code: 716
Module: 64
LineInfo: fdc1cbdf2c233430
Fields: $module : disk_bundle_vs_38350
Message: Failed to take a VSS snapshot.
--------------------
--------------------
Attachment | Size |
---|---|
snapapilogs.zip | 7.55 KB |


- Log in to post comments

No I have not tried that. I was under the impression that I wouldn't get a recoverable image if I didn't use VSS.
- Log in to post comments

No I have not tried that. I was under the impression that I wouldn't get a recoverable image if I didn't use VSS.
- Log in to post comments

Disabling VSS works. The backup will use Acronis' snapshot manager called snapman.sys.
I had to do this on my machine because there was not enough free space on the system partition. I was getting a not enough space to create a VSS snapshot error. Apparently, a lot of free space is needed.
- Log in to post comments

Thanks, I will try that. I don't have a space issue on my system partition though, 50GB of 118GB are free.
- Log in to post comments

I am getting similar VSS errors on Windows 8.1 on a Surface Pro 3:
"Failed to create a snapshot of volume" Error code: 50247
"Failed to take a VSS snapshot" Error code: 716 same
- No errors on the disk
- free space is not the issue
- Log in to post comments

- Log in to post comments

Thank you for your suggestion.
I have tried using the default Provider (Software - System provider) and the Acronis Provider (Software - Acronis VSS Provider).
Both produce the same two errors:
1. "Failed to create a snapshot of volume (C:)" Error code: 50247
2. "Failed to take a VSS snapshot" Error code: 716
I can successfully make a backup when VSS is disabled.
- the AMMS service is running under administrator
- there are no errors on the disk
- shadow copy space is 20% and empty
- I am using AB11.5.38774
- Windows 8.1 Pro 64 bit on a Surface Pro 3 tablet with a GPT/UEFI disk, Bitlocker is turned off on all volumes
I do not have any processes/services/transactions running like SQL Server or Exchange, etc.
It is just a PC. The only thing running would be virus scans, outlook PST compaction, Media Library maintenance...
Any other ideas?
Can I just disable VSS?
Is there something unique to the Surface Pro 3?
I hope I don't have to use boot media for each backup!
HELP!
Attachment | Size |
---|---|
187154-114460.log | 6.07 KB |
- Log in to post comments

Does this warning appear only if "Windows RE tools" partition is included in the backup? In the attached log there are no warnings related to C: partition, only 'Windows RE Tools' one . If the warning is only about RE Tools partition, I guess it can be ignored.
- Log in to post comments

No, now that you mention it, I have seen this two error signature (it is always these two 50247/716 errors) on two partitions, "Windows RE tools" and "C". Attached is the "C" partition errorlog.
Attachment | Size |
---|---|
187370-114466.log | 6.06 KB |
- Log in to post comments

So the first log I sent "win8sur3-002_windows_fulldisk_wd300gb_vssacronis_fail_backuplog.log" documents a failure on the "Windows RE tools" partition using the AconisVSS provider.
And the second log I sent "win8sur3-001_windows_fulldisk_wd300gb_vssmsdefault_fail_backuplog.xml_.log" documents a failure on the "C" partition using the default VSS provider setting.
Until the most recent test, all of my testing has been using the default VSS provider setting, and using this setting I have seen this 50247/716 error signature alternate between these two partitions.
Is there a specific test I can run?
- Log in to post comments

The backup fails because of error 2147746132 - "Class not registered" . It's mentioned a lot in the internet, you can check if any of solutions (in contetof creating VSS snapshot) fits your environment. It doesn't seem to be Acronis- specific. You can try to run build-it Windows backup to check if it works.
- Log in to post comments