Common causes and solutions to Backup, System Restore, and Complete PC Backup problems
Published Apr 10 2019 01:24 AM 287 Views
Iron Contributor
First published on TECHNET on Jun 22, 2007

The Vista Backup team has been helping troubleshoot backup-related problems reported in the public Windows Vista newsgroups. This has been a great learning experience for us, not only in working with customers but also understanding the real-world problems our customers face. Below is summary of the most commonly reported problems we’ve encountered.

Error or Symptom


System Restore fails with the following error:

The Restore point could not be created for the following reason:

Windows cannot create a shadow copy due to internal error in other system components. For more information view the event log. (0x81000109)

We’ve seen a couple causes for this error:

(1) A disconnected external SCSI disk was marked as Offline in Disk Management. Turning off the driver fixed the problem.

(2) System Restore was failing due to a buggy BIOS that changes the disk enumeration order based on the presence of a bootable DVD. One workaround is to explicitly set the BIOS boot disk priority order. Most likely, the second hard disk needs to become the first in the list. This will cause the disks to get enumerated in the same order, regardless of whether there is a DVD present.

System Restore fails with the following error:

There was an unexpected error.  The filename, directory name, or volume label syntax is incorrect (0x8007007B). System Restore will now close.

This error is caused by faulty imaging by the original equipment manufacturer (OEM) that results in the presence of an invalid volume. To see if this is the problem, go to System in Control Panel and open System Protection. There will be two volumes shown, one of which is selected and named “Missing.” Selecting C: and deselecting “Missing” solves the problem.

Complete PC Backup fails with the following error code:

The writer experienced a non-transient error.  If the backup process is retried,

the error is likely to reoccur. (0x800423F4)

This error is caused by a bug in the driver for Intel ICH5R chipset that results in critical disk 0 not being marked as fixed hard disk. There is no workaround because.  According to Intel, this version is not Windows Vista compatible:

File Backup fails with the following error:

The parameter is incorrect. (0x80070057)

This error is caused by a bug in File Backup where if you don't back up at least one file during the full backup, every backup after that fails. The workaround is to go through the Backup wizard again and choose a new full file backup at the very end.

File Backup fails with the following error code:

Not enough storage is available to complete this operation. (0x8007000E)

This error occurred on a computer running an incompatible version of G-Data Internet Security. Disabling this program solved the problem.

File Backup fails with the following  error:

An error occurred. The following information might help you resolve the error: If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lose, however, the filter correctly handles the exception. (0xC00000EA.)

This error occurred on computers running eTrust antivirus software. Excluding zip files from being scanned or disabling eTrust solves the problem. Contact CA, the antivirus vendor, for an updated version.

(A customer reported the same error using Kaspersky Internet Security 7 and he states that disabling this AV software also fixed the problem.)

File Back and Disk Defragmenter fail with the following error message:

Transaction support within the specified file system resource manager is not started or was shutdown due to an error. (0x80071A91)

This error is caused by a bug in the transactional file system (TxF). We’ve had customers report good results using the following blog post .

File Backup fails with the following error:

Access is denied. (0x80070005)

This error occurs because the recovery partition is enabled for File Backup or System Restore and is almost full. To work around this, do not select D: as a backup source. Also, go to System Protection in Control Panel and make sure that D: is not enabled for restore points.

System Restore fails with error 0x8007000E in the Windows Recovery Environment.

This error occurs on computers that have only 512 MB RAM and that have a lot of files. Upgrading to 1 GB of memory will solve the problem.

Version history
Last update:
‎Apr 10 2019 01:24 AM
Updated by: