|
Feature |
Error or Symptom |
Cause/Solution |
|
System Restore
|
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)
|
|
System Restore
|
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.
|
|
System Restore
|
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
|
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
|
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
|
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 Backup
|
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
|
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.
|
|
File Backup
|
There is not enough disk space to save the back up files.
Free up disk space or change your back up settings
(0x81000005)
|
This error occurs when your backup destination disk runs out of space. You can delete a backup by following these steps:
- Open the location where the backup is saved.
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.
- Right-click the folder containing the backup you want to delete, and then click Delete.
Notes
- Backups are saved in this format: <backup location>\<computer name>\Backup Set <year-month-day> <time>. For example, if your computer name is Computer, your backup location is E, and you backed up on April 2, 2006 at 16:32:00, that backup would be located in E:\Computer\Backup Set 2006-02-04 163200. You would right-click the folder named Backup Set 2006-02-04 163200 to delete that backup.
- When you make a full backup, a backup folder is created and labeled with the date for that day. As you add updates, that date stays the same, but your backup is not out of date. The next time you make a full backup, a new backup folder is created and labeled with the date for that day, and any updates are then added to that new folder. You should not delete the current backup folder.
- You should always delete your backup at the backup set level, and not the individual incremental backups within the backup set.
|
|
File Backup
|
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
%SystemRoot%\System32\Config\SystemProfile,
%SystemRoot%\ServiceProfiles\LocalService, and
%SystemRoot%\ServiceProfiles\NetworkService
respectively.
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.
|
|
ALL
|
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.
|
