Admin MrG Posted April 5, 2010 Admin Share Posted April 5, 2010 With v1.18 of Defraggler, we've fixed many small bugs and also have optimized some of Defraggler's features. When you're defragging a large number of small files, we've massively improved the defragmentation speed! Also the 64-bit version of Defraggler now uses far less memory when running. Here's the change log: Optimized and bug fixed defrag with large numbers of small files. Optimized 64-bit memory usage. Drive map is no longer blocked by background operations. Simplified the drive map highlighting to make it faster and more memory efficient. Fixed control sizes on file search form. Fixed issue with exclude files dialog. Fixed a few missing translations. Fixed bug displaying filenames containing ampersands. Improved memory leak detection mechanism. Lots of minor bug fixes. Download Defraggler today at www.piriform.com/defraggler. While you're there, consider signing up for our spam-free newsletter that will inform you about the latest releases, updates, and new products. View the full blog post Piriform.com - [CCleaner - Defraggler - Recuva - Speccy] Link to comment Share on other sites More sharing options...
Lizardmannnn Posted April 7, 2010 Share Posted April 7, 2010 WOW Priform did a great job on V1.18 it really does run much faster and I use a 64bit system and you can tell the memory usage is much less. Thanks Link to comment Share on other sites More sharing options...
Lucky10 Posted April 8, 2010 Share Posted April 8, 2010 I've noticed that when I see the announcement of a newer version on here I open the app just to check the version number. Now CCleaner and Recuva say there is a newer version but Defraggler doesn't even though Automatically check for updates to Defraggler is ticked in Options. WinXP SP3 and Vista Home Premium SP2 Link to comment Share on other sites More sharing options...
Inversion Posted April 11, 2010 Share Posted April 11, 2010 Search with the option "Filename or path contains" doesn't work for me in this version. Rolled back to 1.17 and all became ok. Link to comment Share on other sites More sharing options...
Recommended Posts