Inaccurate C: drive capacity reading/Unable delete winold folders

Page 3 of 3 FirstFirst 123

  1. Posts : 4,594
    Windows 10 Pro
       #21

    Ah, thought you had already done that.
      My Computers


  2. Posts : 31,611
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #22

    tosalet said:
    ...Tomcat got it with turning protection off for C: and deleting all restore points worked. All is good now.
    Glad to hear that. It's always best to use the official methods if at all possible. Hacking should only ever be used as a last resort.
      My Computers


  3. Posts : 31,611
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #23

    AddRAM said:
    Ah, thought you had already done that.
    It would seem not - it would appear that Disk Clean-up's 'delete all but the last restore point' had been tried though.
      My Computers


  4. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #24

    Those large file are the orphan System Restore points and I have seen in Win 8 forum where some users have > 100GB. The most effective way is to delete the whole "System Volume Information" folder using Linux, reboot and let Windows re-create the folder. That's the reason I have Linux Mint installed on a separate partition and when needed to clean up those stubborn Files/Folders such as Windows.old, System Volume Information etc...
    Once back in Windows, create a new restore point.

    From time to time, I use Linux to delete "System Information Volume" Folders on all drives, Reboot and Windows will re-create everything. I've been doing this since Windows 95 and can assure you there will be no ill affect.

    My suggestion to you is turn off System Restore point and use a third party back up software. System restore is not reliable, slow down your PC and often cause problem like this.
      My Computer


  5. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #25

    tosalet said:
    Hi guys, thanks for all your help. Tried to delete from within Treesize but it didn't play ball. Tomcat got it with turning protection off for C: and deleting all restore points worked. All is good now. Great service and thanks again to you all for your time and expertise. :):)
    Glad to hear! Thought, too, you had tried it. If you havn't already, make a new one manually after you turn it back on, for safety.

    EDIT: Topgun's suggestion is the better long term solution.
      My Computers


  6. Posts : 4,594
    Windows 10 Pro
       #26

    I`m running this on my X299 now, darn these updates take a while to get rid of, over 5 minutes now

    I also agree with Dino, I don`t use system restore, I create images. But you need a place to store those images.
    Attached Thumbnails Attached Thumbnails Inaccurate C: drive capacity reading/Unable delete winold folders-dc.jpg  
      My Computers


  7. Posts : 11
    Windows 10 Home
    Thread Starter
       #27

    All good advice noted!
      My Computer


  8. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #28

    AddRAM said:
    I`m running this on my X299 now, darn these updates take a while to get rid of, over 5 minutes now
    It's all that TiWorker compression of the patches cooking your CPU. Check taskmanager.
      My Computers


  9. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #29

    FYI,
    A clean System Volume Information folder should only contains 2 files (20KB). If you have Macrium installed, a third file $MRCBT is also created (7MB).
    $MRCBT ( To reduce the amount of time it takes to perform incremental and differential imagesby monitoring the changes to an NTFS formatted volume in real-time).
    Besides the System Restore points, SVI also stores other junk files, For example, when you run chkdsk, the result will also be stored there.

    Inaccurate C: drive capacity reading/Unable delete winold folders-p1.jpg

      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:33.
Find Us




Windows 10 Forums