I understand the NgBase folder contains files used by Avast 2015 for a virtual environment/sandbox type function. However I have noticed that the current .dat file is now 1.32GB and the .sav file is 324MB. The .dat file is also fragmented and my defrag utility cannot process it. How large are these files likely to grow to and are their current sizes and fragmented states normal? Is there a way to disable this feature and/or delete the NgBase folder?
Defrag was useful on FAT systems.
On NTFS and other filesystems it is “obsolete”.
Surely you meant to say: on SSD’s defrag is obsolete?
If not, you’re completely wrong. “Basically” it doesn’t matter which file system is in use, what matters is that the hard disk needs to spin the platters and find the requested data on those platters, and if a file has a lot of fragments all over the disk, then the reading of data is simply slower because the data has to be gathered from many different parts of the disk. Basic knowledge.
To OP, you can uninstall NG/Secure Virtual Machines by going to add/remove programs (or programs and features, it’s named differently in different Windows versions) and change the install, then deselect the component you don’t like, Secure Virtual Machines in this case.
To OP, you can uninstall NG/Secure Virtual Machines by going to add/remove programs (or programs and features, it’s named differently in different Windows versions) Select Avast then select change, then deselect the component you don’t like, Secure Virtual Machines in this case. Once the process is finished, reboot your system.
Thanks for the advice. I suspect the new Ng/VM might also have been causing chkdsk/autochk to fail too - I’ve had this problem when trying to check my hard drive after a couple of BSODs recently and I notice other Avast users have complained of this problem on the forum recently. I’ve changed the Avast installation as suggested.
Thank you Howard14 for asking the question.
Apparently, avast! implemented a new function, and “opted us all in.”
I had a snapsomething file almost 1/2 GB and 69 fragments that wouldn’t coalesce. Whatever the new function is, there has to be a better way.
Surely, Eddie, you meant to say: on SSD’s defrag is obsolete? My computer becomes a basket case if my NTFS drive is not kept defragmented. Recommend Piriform Defraggler by Piriform. I like it so much and the advertising is so innocuous, I should remember to check Piriform for other interesting utilities.
Of course, thanks to Skakara and bob3160 for the answer to the un-deframentable file. After un-checking and rebooting, I’m able to achieve 0 fragments again, which lasts for a few seconds.
avast! has to find a better way. Some people maintain their computers, and a file that won’t defrag gives us hives. I wonder if this is going to need to be unchecked every time the program updates.
I guess I should ask what function I turned off by disabling Secure Virtual Machines? In Programs and Features, the “Setup” window that opens for un-checking the checkbox has a question mark in the corner, but it doesn’t offer any information.
I hope Howard14’s blue screens go away. But in my limited experience, a big, fragmented file will not be sufficient cause for such instability. I might recommend some RAM testing, check the S.M.A.R.T. report for your hard drive, try to get through some online malware scans, wiggle all the connectors inside the computer to assure they’re all tight. Install temperature-monitoring software for CPU and hard drive, and anything else you can monitor. Swing a plastic chicken overhead while tapping your tummy…
-neil-
PS. I wish the Navy Blue were darker…