Hi Bossland, good to see you active in the DB forums. The problem is that the 'autoupdate' feature overwrites an existing install. If you download a DB release and always use the auto update feature by the time it gets updated for a D3 patch you'll never actually have a working local zip of an older version. The autoupdater pops up a window saying "a new version is available" and people have a tendancy to click those types of windows without thinking twice about it. Please consider adding some code to the auto update that i) allows a user to disable it ii) during the update process copies the old version to a backup directory allowing a user to rollback easily if they want to. I'm a geek and I have a local copy on my HD of every single release of DB so that if I want to go back to one I can. A lot of less computer literate users just click update popup windows and never download a new zipfile after they first install the s/w.
