Related Vista Error Messages
  1. 0x80070724 - Incompatible version of the serializing package
  2. 0x80070005 - Create a manual restore point the following may be displayed - Access is Denied
  3. 0x8007007B - "the filename, directory name, or volume label syntax is incorrect. System Restore will now close"
  4. 0x80040154 - Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
  5. 0x8007000E - System Restore fails with error in the Windows Recovery Environment.
  6. 0x8007000E - File Backup fails with the following error code:
    Not enough storage is available to complete this operation
  7. 0x81000109 - 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.
  8. 0x800423F4 - 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.
  9. 0x80070057 - File Backup fails with the following error: The parameter is incorrect.
  10. 0xC00000EA - 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.
  11. 0x80071A91 - Transaction support within the specified file system resource manager is not started or was shutdown due to an error.

Error: 0x80070724 - Incompatible version of the serializing package New! 6/14/07

SYMPTOMS:

The above error message appears when the 'System Properties Dialogue Box' opens and it searches for drives

 

Or when System restore and System backup are launched.

 

Cause: This can be caused by Shadow Copy corruption.

 

RESOLUTION: Delete all existing Shadow Copies.

Warning: All but the most recent System Restore restore points, all Previous Versions, and all but the oldest Complete PC Backups will be deleted.

 

Method 1 - Warning: All but the most recent System Restore restore points, all Previous Versions, and all but the oldest Complete PC Backups will be deleted.

 

Use Disk Cleanup - More Options - System Restore and Shadow Copies - Cleanup option to remove all restore points and Shadow Copies.

 

Method 2 - Warning: All System Restore restore points, Previous Versions, and all but the oldest Complete PC Backups will be deleted.

 

Go to Start - All Programs - Accessories - right click on - Command Prompt and select Run as Administrator

Or press the WinKey on the keyboard, type CMD - right click on - Command Prompt and select Run as Administrator.

 

At the elevated command prompt type or paste the following command then press enter.

 

Vssadmin delete shadows /all

 

 Top of page

Error: 0x80070005 - When trying to create a manual restore point the following error message may be displayed - Access is Denied

1. This can be do to the System Volume Information Folder attributes being set to Read-only.

 

The System Volume Information Folder is where Vista holds restore points or shadow copies.

 

For Windows Vista using the NTFS File System.

  • Click Start then My Computer.
  • On the Tools menu Then Folder Options.
  • On the View tab, click “Show hidden files and folders”.
  • Clear the Hide protected operating system files (Recommended) check box. Click Yes when you are prompted to confirm the change.
  • Click OK.
  • Right-click the System Volume Information folder in the root folder, and then click Properties.
  • If the Read-only attibutes is checked, uncheck it and click, OK
  • Now try creating a restore point.

Warning: Remember to hide the hidden System Files when done.

 

2. 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.

 

 Top of page

Error: 0x8007007B - "the filename, directory name, or volume label syntax is incorrect.

 System Restore will now close"

Press the WinKey on the keyboard and type or paste SystemPropertiesProtection then press enter.

Deselect the "C: Missing" checkbox and select "Local Disk C:" to enable System Restore.

 

Cause: This error is caused by faulty imaging by the original equipment manufacturer (OEM) that results in the presence of an invalid volume.

 

How resolve the error 0x8007007B when I run System Restore in Microsoft Windows Vista?

 

 Top of page

Error: 0x80040154 - Volume Shadow Copy Service error: Unexpected error calling routine
CoCreateInstance.
New! 7/21/07

If the events occurred on a machine that was running in Safe Mode, these events are benign and you can ignore them - unfortunately they will always appear whenever you reboot the machine in Safe Mode. We plan to fix this bug for future versions of Windows (it is already fixed in Windows Server 2003).

 

Otherwise, see this MS TechNet Support Article

 

Reinstalling COM+ using MS KB Article 315296 may resolve the issue.

 

 Top of page

Error: 0x8007000E - System Restore fails with error 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.

 

 Top of page

Error: 0x8007000E - File Backup fails with the following error code:

Not enough storage is available to complete this operation.

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

 

 Top of page

Error: 0x81000109 - 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.

Here are a couple of possible causes for this error:

  1. A disconnected external drive was marked as Offline in Disk Management. Turning off the driver fixed the problem. Disconnecting the external drive should fix the problem also.
  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.

 Top of page

Error: 0x800423F4 - 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.

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

 

 Top of page

Error: 0x80070057 - File Backup fails with the following error:

The parameter is incorrect.

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.

 

 Top of page

Error: 0xC00000EA - 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.

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.

 

 Top of page

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

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

http://blogs.vertigo.com/personal/alexark/Blog/Lists/Posts/Post.aspx?ID=5

 

 Top of page

 Top  Home  Support

 

Search This Site

Site Last updated

Friday, October 23, 2009

 

Start Date 2/27/05


View My Stats

 

Copyright © 2005 - 2009 Bert Kinney