Drive Bender v1.1.4.1 Released

by Damian on June 7, 2011 · 1 comment

in News

An update to Drive Bender, the DE replacement for Windows Home Server 2011, has just been released. See the release notes below:

Release v1.1.4.1 – beta (2011-06-07)
- Bug fix: Under high CPU usage, a number of file system errors could occur. This bug also effected other areas of the application, and could have cause a number seemingly unrelated issues. This bug has been known to cause :-
* Sync / copy applications displaying errors with some files.
* WHS client backups failing.
* WHS backup service crashing.
* Client applications / services crashing.
* Memory leaks on large file transfers.
* Drive Bender slow down after a period of time.
* Excessive C drive usage due to the large log files being generated.
- Bug fix: Deleting a file can sometime leave an orphaned duplicate file.
- Update: Log files are now limited in size.
- Issue: On occasions a deleted file will NOT go to the recycled bin.
- Bug fix: Restarting the Drive Bender service could sometimes cause the service to hang.
- Update: Drive balancing and health monitoring now pause during heavy read / write activity.

You can download the latest version from http://www.drivebender.com/beta-download/


Article by

Hi, my name is Damian, and I'm tech gadget addict! Although I always had some interest in technology, it wasn't until I got my EX470 and more importantly found Mediasmartserver.net, that my interest became an addiction. My goal, aside from world domination and to see the Mets/Broncos win another championship, is to set up the perfect digital home where all my media is available at the click of a button. When I am not writing for Mediasmartserver.net you can find me over at my blog at http://www.adigitalhomeblog.com or follow me on twitter


{ 1 comment }

jericko June 16, 2011 at 4:43 pm

Sounds like allot of bugs still. It would be awesome if this becomes stable and can run on Windows Server 2008 R2!

Comments are closed, visit the forums to continue the discussion.

Previous post:

Next post: