The Storage Team Blog about file services and storage features in Windows and Windows Server.
This is an update to the solutions table posted previously on this blog.
Vista Backup team has been working with customers to troubleshoot common problems, but sometimes it’s a hard job – some error codes belong to other system components and are reflected in Backup tool functionality. Even so, the team brings you a few more step-by-step solutions.
We hope this updated table can help:
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.
(3) Disk incompatible with Windows Vista causes residual information of the disk to leave behind even though the disk is disconnected. The Workaround is to use Device Manager to disable the “phantom” disk (submitted by a customer)
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.
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.
Complete PC Backup
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: http://support.intel.com/support/chipsets/imsm/sb/CS-023616.htm
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.
There is not enough disk space to save the back up files.
Free up disk space or change your back up settings
This error occurs when your backup destination disk runs out of space. You can delete a backup by following these steps:
For example, if you backed up your files to an external hard disk labeled "E," connect the external hard disk to your computer, and then open drive E.
The system cannot find the file specified. (0x80070002)
This problem is due to one or more profiles under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList with missing ProfileImagePath.
To check whether you have missing profiles:
1. Open regedit, navigate to the above registry key. (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList). Expand the list
2. Click on each of the profiles listed. The first 3 profiles should have ProfileImagePath value of
3. Starting from the 4th profile, the ProfileImagePath should contain path to the user profiles on your machine, such as C:\users\Christine
4. If one or more of the profile has no profile image, then you have missing profiles.
To work around this, delete the profile in question (Caution: The registry contains critical settings that are necessary for your system to function properly. Take extra caution while making changes)
1. First, export the ProfileList key for safekeeping. (Right click on the key, choose “Export”, and save it to the desktop.)
2. Right click on the profile in question, choose delete.
3. Try backup again.
Transient error (0x800423F3)
When a transient error occurs, this usually indicates that one or more VSS writer(s) has returned an error. To diagnose the problem, type the following command from an elevated command prompt:
vssadmin list writers
This should provide information on which writer returned the error. More details about the error should also be logged by that writer in the Event Log.
The solution to The parameter is incorrect (0x80070057) error in file backup does not work. I get the error as soon as I start the File Backup Wizard and also when I try to start any of the restore options.
Your suggestion for File Backup Error 0x80070002 doesn't work for me as I have no surplus profile names.
Do you have any further meanings for this error code when backing up?
Suggestion for File Backup Error 0x80070002 appears to be useless in this case, too. All 3 system profiles have correct paths; ditto all 3 user profiles on this machine. Dell XPS m1330, Windows Vista Ultimate, backup attempts all failed both immediately before and immediately after installation of Vista SP1.
As of right now, we only have a step-by-step solution for error 0x80070002 as described in the table. We will research the case of one profile only.
Sorry for the problem you are experiencing!
I'm very pleased to report that (having unsuccesssfully tried everything that has been suggested on this topic in several forums) the second attempt to Repair Install Vista from the Medion Recovery Disc worked fine (critically, I had NOT installed SP1) AND I have now successfully run a backup! For information, the second time, having finally managed to delete (from the FileRepository in C:\Windows\System32\DriverStore) the newer nVidia graphics drivers that always crash my PC, I ran it with UAC active, Windows Features turned off along with Virus & Spyware protection. It took about 2 hours (without Windows Updates - I have that pleasure to come!), and so far, everything except the Media Centre (and its remote control) seems to be working as expected. However, I still have no idea what was the corrupted file that caused the problem!
I have a Dell with Vista Home Premium. After a crash and lost of my data, i decided to start doing backup. My new backup from "Backup and Restore Center" failed at the end with error 0x81000004.
The backup was set to save to a local USB disk with plenty of disk space. I search the web and found a report of identical error at
but the issue seemed not resolved.
Please help! Thanks!
Thanks for sharing your solution!
Could you email us with a more detailed description of your problem using he EMAIL link at the top of this page? Please include both the error code and the error message. We'll contact you for further information.
Thanks for your prompt response. The information you asked for has been sent to you. Thanks!
solution for 0x80070002 I believe is incomplete. I have no missing image path but same error. My experience so far with Vista is that things that were in 1 place in XP now are in several places and you have to find them all... also curious whther the asp.net account for my virus software and default hidden accounts could be affecting the logic. Net is MS should provide patch that allows backup to log "bad profile" and backup what it can find.
A customer sent us a contribution to the Vista Backup and Restore Errors and Solutions table . Christine
I found these errors in an ASR log wrt the backup error 0x81000004 i reported earlier:
[ERROR] 0x1258 - mtmgrlib.cpp#439 [0x57]: Fail to query mount point
[FUNCT] 0x1258 - EXIT - MtMgrGetMountPoints [0x57]
[ERROR] 0x1258 - asrbkup.cpp#500 [0x57]
[FUNCT] 0x1258 - EXIT - AsrpGetMorePartitionInfo [0x57]
Anyone knows what the messages mean?
Also, i suspected that my backup failed in my music directory. Is there a way to exclude a directory (and its subdirs) from a backup?
OK, it had nothing to do with any particular file. After i excluded music files from backup, it now failed at different place.
However, when it failed, the last zip file was always #30 or #31 in my more than 10 times of trial. Anybody has any clue?
Some customers had good results with the tips from this newsgroup:
Let us know what happens.