locked
Cannot create a Restore Point or Restore to a previous one. RRS feed

  • Question

  • From System Properties, using the "Create" , to create a Restore Point, brings up "The restore point could not be created for the following reason: The volume change journal is being deleted. (0x8007049A)  Please try again." If I go to System Restore The same occurs. In the display there are shown maybe 2 or more System Checkpoints but again if I try to restore back to one of these I still get the same result. All System Protection settings are normal and Windows Firewall is on. Any suggestions?
    Monday, June 2, 2008 12:15 AM

Answers

  •  

    Hi,

     

    First, let’s check what is "volume change journal":

     

    -----------------

    How NTFS Works

    http://technet2.microsoft.com/windowsserver/en/library/8cc5891d-bf8e-4164-862d-dac5418c59481033.mspx?mfr=true

     

    As files, folders, and other NTFS objects are added, deleted, and modified, NTFS enters change journal records in streams, one for each volume on the computer.

     

    The change journal conveys significant scalability benefits to applications that might otherwise need to scan an entire volume for changes. File system indexing, replication managers, virus scanners, and incremental backup applications can benefit from using the change journal.

    -----------------

     

    FRS also depends on NTFS change journal for DFS replication. So, we can check the following:

     

    1. If possible, delete the current restore points and then try run system restore again. In this way, I think NTFS change journal should not be used.

    2. Check whether there are applications which may damage change journal, such as third party backup tool, indexing tool, antivirus tool, third party folder replication/synchronization tool, and so on.

     

    In addition, any of the following also could contribute to this issue:

     

    1. You have an application that is interfering with System Restore.

    2. One or more of the core System Restore files are missing and/or corrupted.

    3. The Volume Shadow Copy Service (VSS) has been disabled. System Restore depends on VSS volume snapshots being created via Shared Protection Points (SPP). System Restore can not function if snapshot creation via SPP breaks or is disabled or if VSS is in a disabled state.

    4. Your Disk Space which store backup file is less than 300m.

     

    Let’s narrow down the issue.

     

    1.Try to use System Restore from WinRE, SafeMode or Windows Vista in a “Clean Boot” state. If that fails, proceed with the next steps.

    2.Check for the existence of the following files at the %windir%\system32 directory:

     

    Srrstr.dll

    Srclient.dll

    Srcore.dll

    Rstrui.exe

     

    3.Check that the Volume Shadow Copy Service (VSS) is not disabled.

    4.Check for either of the following registry keys:

     

    HKLM\Software\Policies\Microsoft\WindowsNT\CurrentVersion\SystemRestore

    HKLM\Software\Microsoft\WindowsNT\CurrentVersion\SystemRestore

     

    If you find a DisableConfig DWORD set to “1” in either of these keys, export the key as a backup and delete it.

     

    5. Verity your free Disk Space.

    6.Then try System Restore again.

    Friday, June 6, 2008 10:35 AM
    Moderator

All replies

  •  

    Hi,

     

    First, let’s check what is "volume change journal":

     

    -----------------

    How NTFS Works

    http://technet2.microsoft.com/windowsserver/en/library/8cc5891d-bf8e-4164-862d-dac5418c59481033.mspx?mfr=true

     

    As files, folders, and other NTFS objects are added, deleted, and modified, NTFS enters change journal records in streams, one for each volume on the computer.

     

    The change journal conveys significant scalability benefits to applications that might otherwise need to scan an entire volume for changes. File system indexing, replication managers, virus scanners, and incremental backup applications can benefit from using the change journal.

    -----------------

     

    FRS also depends on NTFS change journal for DFS replication. So, we can check the following:

     

    1. If possible, delete the current restore points and then try run system restore again. In this way, I think NTFS change journal should not be used.

    2. Check whether there are applications which may damage change journal, such as third party backup tool, indexing tool, antivirus tool, third party folder replication/synchronization tool, and so on.

     

    In addition, any of the following also could contribute to this issue:

     

    1. You have an application that is interfering with System Restore.

    2. One or more of the core System Restore files are missing and/or corrupted.

    3. The Volume Shadow Copy Service (VSS) has been disabled. System Restore depends on VSS volume snapshots being created via Shared Protection Points (SPP). System Restore can not function if snapshot creation via SPP breaks or is disabled or if VSS is in a disabled state.

    4. Your Disk Space which store backup file is less than 300m.

     

    Let’s narrow down the issue.

     

    1.Try to use System Restore from WinRE, SafeMode or Windows Vista in a “Clean Boot” state. If that fails, proceed with the next steps.

    2.Check for the existence of the following files at the %windir%\system32 directory:

     

    Srrstr.dll

    Srclient.dll

    Srcore.dll

    Rstrui.exe

     

    3.Check that the Volume Shadow Copy Service (VSS) is not disabled.

    4.Check for either of the following registry keys:

     

    HKLM\Software\Policies\Microsoft\WindowsNT\CurrentVersion\SystemRestore

    HKLM\Software\Microsoft\WindowsNT\CurrentVersion\SystemRestore

     

    If you find a DisableConfig DWORD set to “1” in either of these keys, export the key as a backup and delete it.

     

    5. Verity your free Disk Space.

    6.Then try System Restore again.

    Friday, June 6, 2008 10:35 AM
    Moderator
  • Hi .... When I try and manually create a restore point in Vista I get the following error message:

     

    Could not create the scheduled task for the following reason:

    Cannot create a file when that file already exists (0X800700B7)

     

    Coincidently this problem started when the last automatic restore point was created on Oct 26, 2008. Since then no other automatic restore points have been created and I can't create one manually either. Its almost as if the restore point creation process is stuck in constant write mode and won't create a new one automatically or manually.

     

    This error message occurs whether VSSCOPY service is running or not. I have all the required system restore files or dlls in system 32. I have also eliminated any possibility of it being caused by another program since the automatic restore point creation process worked fine up until Oct 26, 2008. 

     

    The following is the current content of my ONLY system restore registry key:

     

    "hklm\software\microsoft\windows nt\currentversion\systemrestore" and its values are:

     

    firstrun                       regdword     0x00000000 (0)

    lastindex                    regdword     0X000000BB (187)

    rpglobalinterval            regdword     0x00015180 (86400)

    rplifeinterval                regdword      0xffffff (4294967295)

    rpsessioninterval         regdword      0x00000001 (1)

     

    Please help if you can

     

    Thanks

    Ray

    Sunday, November 9, 2008 2:50 PM
  • Hi,
    I have got exact the same problem.
    And it happend at the same time in late October.

    I'm looking forward a solution...

    BR
    Nils
    Tuesday, November 11, 2008 9:17 PM
  • I have the same or very similar problem.  I discovered the issue when I attempted to install software. As part of the software install a restore point is automatically created but in this case the restore is prevented from being created and the software can't install.  I attempted to manually create a restore point using the System Protection tab under System Properties but in the Avialable Disks box the word Searching... is continously displayed.  I attempted to restore to an earlier system check point, but when I try to run the System Restore application the app doesn't start and no message or other indication of a failure is displayed.  I attempted a restore using the Vista Install Disk, oddly enough the last good restore point reported by the Vista Install Disk was created on 11/01/2008 which is probably when my system installed the 10/28/2008 patches.  No other restore points were created after 11/01/2008.  Using the Vista Install Disk allowed me to restore back to 11/1 but that did not correct the problem. I also reset the repository but theat did not correct the problem.  This will become a critcal issue because most MS Vista patches require the creation of a restore point prior to installation. Without the successful creation of the restore point, the patch cannot be applied.  I would hate to have to reload the OS to fix this problem, but I'm running out of options.       

     

    Thursday, November 13, 2008 3:22 AM