AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Ni reaktor11/24/2023 This is also the reason why I think that a Windows installer for each little plugin is overkill! It is much overhead and many times there are things installed with it that you never use (Avid. Nowadays we have to be quite vigilant in managing our system drives since updates have become so bloated. I wasn't aware of TreeSize Free, so thanks for mentioning it. I also use a disk space analyzer (SpaceSniffer) to see the breakdown of my system drive. Like you I regularly check System Restore and delete restore points when I know I won't need to roll back to an earlier state. They do begin to add up, even though you can set a max usage of 1% of the drive, but in my case that equals 4.64GB (on a 500GB M.2 SSD).īottom line is that I suspect Native Access is not using 3GB of drive space by itself. Then created a manual restore point that only used 1.1 GB. I just scanned with TreeSize and they were using 3GB here, so I deleted all. You can delete the restore points if you don't need them by clicking on "Configure" in System Protection, which shows the space used, and then clicking on "Delete". They are the large files in braces with long names in hex. Alternatively you can confirm this by using a disk space analyzer like the excellent TreeSize Free run as Administrator, and looking at the System Volume Information folder. You can see how much drive space System Restore is currently occupying by opening System Protection from Windows Settings. That can easily eat up at least several GBs. I have discovered that Windows usually makes a system restore point when you run an installer, if you have System Restore protection enabled on your system drive. I frequently see my C drive disk usage increase by several GBs after a new install (in excess of the expected actual files installed). That's surprising! I see Native Access 2 only using 375MB here. Equally surprising is that the 3GB loss of drive space was due solely to the installation of NA2 (I checked before updating any VIs/FXs).
0 Comments
Read More
Leave a Reply. |