Volsnap - Shadow copies deleted every boot

Answered Volsnap - Shadow copies deleted every boot

  • Sunday, March 27, 2011 3:30 PM
     
     

    Am using Win7 Ultimate Sp1 32 bit.  Since last week (bunch of Windows updates), upon every boot, I get a volsnap error:

    shadow copies of volume C: were deleted because the shadow copy storage could not grow in time

    and my system restore points are deleted.

    I  have 150 GB free space on the drive and System protection is allocated for 8% of the drive.  Coinciding with this issue is the fact that I'm also having problems resuming from sleep.  I'm not sure if the shadow copy error also occurs on resume from sleep

     

     

All Replies

  • Monday, March 28, 2011 5:44 AM
    Moderator
     
     Answered

    Hi charlestek,

    Thanks for posting in TechNet forum.

    Try the following method to fix this issue. Note: Please backup the registry before you modify.

    1. Click Start, input regedit, press Enter

    2. Locate and then click the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap

    3. On the Edit menu, point to New, and then click DWORD value.

    4. Type MinDiffAreaFileSize, and then press ENTER.

    5. On the Edit menu, click Modify.

    6. Type the size that you want for the shadow copy storage area, and then click OK.

    Reboot the computer to check if it works.

    If it doesn't work, please check the disk.

    1. Click the Start, input cmd in the search bar.

    2. Right-click cmd, run it as Administrator.

    3. Input the command: Chkdsk /f /r

    Restart the computer then check if the problem is still there.

    If the issue persists, I would like to know more details

    Is it a domain-joined computer? What's kind of your server?

    Did this issue happen before?

    Here's the similar thread before for your reference:

    http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/7f35bc14-195a-4db6-a0bf-0003f5ccdfef 

    http://social.microsoft.com/Forums/en/whssoftware/thread/d9499524-1e75-4da9-982f-fe82b4bf140e 

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Thursday, March 31, 2011 6:15 AM
    Moderator
     
     

    Hi,

    How's going?

    Please feel free to give us any update.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Monday, April 04, 2011 8:32 AM
    Moderator
     
     

    Hi,

     

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Sunday, April 17, 2011 3:48 AM
     
     

    Miya,

    Remember this is a Windows 7 machine, not a Windows 2003 server.

    chkdsk c: /r /v was performed, no errors.

    What is a default size value for MinDiffAreaFileSize?

    Why does that key not exist before?

    If the system was working properly a month ago without this key, why do I need it now?

     

    Thanks,

    Phil


  • Monday, April 18, 2011 1:37 AM
     
     

    I set MinDiffAreaFileSize to 3000

    Rebooted, still have shadow copies deleted......

  • Monday, April 18, 2011 9:42 AM
    Moderator
     
     

    Use the Vssadmin command to check how much shadow copy storage do you have now.

    Run cmd as administrator, input the command: vssadmin list shadowstorage

    How much size do you have? If it's too small, use the command to resize it.

    Refer to: http://technet.microsoft.com/en-us/library/cc788050(WS.10).aspx  

    Meanwhile, what's the detailed error message you got in your Event Viewer?

    Open Event Viewer - Windows Logs - Applications, under Actions, choose Filter current logs, choose the Event sources "VSS".

    Provide us with the detailed logs.

    Regards,

    Miya


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Wednesday, April 20, 2011 6:46 PM
     
     

     

    Volume H is another dual boot Windows 7 system, which is showing up even though C: is the active drive.

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{94305df9-0bc4-11dd-b4d1-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{94305df9-0bc4-11dd-b4d1-806e6f6e69
    63}\
       Used Shadow Copy Storage space: 777.188 MB (0%)
       Allocated Shadow Copy Storage space: 3.039 GB (1%)


     Shadow Copy Storage association
       For volume: (H:)\\?\Volume{f197c47a-111d-11de-b59f-001fc6488991}\
       Shadow Copy Storage volume: (H:)\\?\Volume{f197c47a-111d-11de-b59f-001fc64889
    91}\
       Used Shadow Copy Storage space: 5.745 GB (1%)
       Allocated Shadow Copy Storage space: 6.224 GB (1%)
       Maximum Shadow Copy Storage space: 10 GB (2%)  Maximum Shadow Copy Storage space: 24 GB (8%)

     

     


    Event 25, volsnap

    The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

     

  • Thursday, April 21, 2011 10:38 AM
    Moderator
     
     

    Please also check your  Volume Shadow Copy service writer, also use the vssadmin command.

    Input the command: vssadmin list writers

    Any errors there?

    Refer to this Hotfix: http://support.microsoft.com/?id=826936

    Regards,

    Miya


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Friday, April 22, 2011 3:42 AM
     
     

      Miya,  you are giving me all hotfixes and data for Windows Server 2003.  MY SYSTEM IS WINDOWS 7 ULTIMATE 32 BIT, NOT WINSERVER 2003.

    No errors from the list writers. 

     

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {b50b1477-2fbc-41dd-89df-4f45e38191b5}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {22ef4bcf-c0d3-42e4-9640-1eee40b4f170}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {fccc9196-9bc7-4a7d-8b7f-526294518933}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {e7e433cf-ada1-4789-9fd2-41aa3c287bb8}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {b0a6f36f-5f90-4422-a202-129d53e5e11b}
       State: [1] Stable
       Last error: No error

    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {5bbf2361-eaf9-47d5-ac3c-e787fcbfb009}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {a99903d2-adee-48c2-88ac-a363f842c9d7}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {bab47eec-36b1-42b6-8306-b7d27ef04f0a}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {930544e6-1d88-4b5e-af60-0a419127c20d}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {f0a0c998-b0b4-4e1b-a935-f5be0c78598c}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {5baef863-7d48-450c-97f8-9d15b1497365}
       State: [1] Stable
       Last error: No error


    C:\Users\SmallFry>
    C:\Users\SmallFry>
    C:\Users\SmallFry>

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

  • Sunday, April 24, 2011 3:00 PM
     
     Answered

    Finally found the answer:  http://blogs.technet.com/b/win7/archive/2011/02/16/restore-points-lost-after-system-rebooting.aspx

    The disk defragment software Perfect Disk recently had a version update.  Apparently it screws up the system restore.

    I disabled the two Perfect Disk services in the service manager gui, and I seem to not have the volsnap shadow copy deleted error when rebooting.

     

    I still have one other issue, I'm possibly not seeing the automatic system restore points.  I looked in the task scheduler and they are set to run at midnight.

    The scheduler says last run time 4/24/2011 1:01:52 AM, but I checked the restore point settings, and no restore point was created at that time. 

     


  • Monday, April 25, 2011 3:01 AM
    Moderator
     
     

    Glad you find the answer!

    I suspect your computer is in Sleep Mode in midnight when backup, if so, the backup won't start.

    If not, please start a new thread about this new issue. It will get more help from the community member here.

    Regards,

    Miya


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Friday, January 25, 2013 5:40 PM
     
     
    Hi to all am running a dual boot of windows xp and windows 7 on two hard drives. The windows 7 disk has been driving me crazy for the past 2 weeks, as it has been deleting every restore point i create, even the restore points that windows update creates it deletes and i have no back up, so i tried to fix this problem by installing 7tweak which just told me my hard drive was corrupt, which i knew to be false cause had only recently formatted and prior to that had checked the disk with seagate tools and other hd software. I could see in event viewer that volsnap was deleting the restore points and 7tweak was telling me i had no backup, so i went to control panel and system and security and backup and restore and told windows 7 to back itself up, it took about an hour and it created a system image and backed itself up on the other xp drive, and created a system restore point which cannot be deleted by windows xp and is bootable from in case of emergency, it says it will back itself up every 5 days to the same place on the xp drive and am happy with that, but it still deletes every manual restore point i create, have read its volsnap of xp doing this and that the only way to avoid it is to hide windows 7 from xp though the instructions are a little sketchy to me i dont fully understand, is there anyone who has more info on how to hide windows 7 from xp deleting its shadow copy files on bootup and peace to all