2.1.2 thrashing hard drive

Hi, updated to 2.1.2 last night and loaded a 25 min audio. Then went about the usual editing, and the HD started thrashing aggressively. It was noisy too… all the HD chatter. Might add it seemed to take LONGER for simple edits. Has there been any change in the way Audacity handles the Temp file? I looked in the release notes. Or is it my imagination?


The default location of the temp file has changed. This was done because we received an increasing number of reports about security products deleting the temp files while Audacity is running and destroying the project data.

To change the temp directory, go to “Edit > Preferences > Directories”.
I’m not sure exactly what happens on Windows (I’m on Linux) but you may not be allowed to use the folder name “tmp” or “temp” (because these are the folders that the offending security products are targeting).

If you use a real-time virus scanner, you may need to tell it to ignore the Audacity temp folder so that it does not scan all of the “au” data files, or tell it to exclude “au” files.

Thanks for that… good tips! I did a system restore this morning, to sort it out first before re-installing 2.1.2.


Is it ok to install 2.1.2 in a separate directory? for Eval purpose?


Please ensure you use Audacity 2.1.2 final release supplied by us: Audacity ® | Download for Windows.

Audacity 2.1.2 supplied by us will refuse any directory in C:\Users<your user name>\AppData\Local\Temp\ because file cleanup apps target that directory.


If you mean use the EXE installer, that will have the problem that you will only see the last installed Audacity in the Windows Control Panel > “Uninstall or change a program”. So if you had 2.1.1 installed, installed 2.1.2 to another location (even in Program Files), then uninstalled 2.1.2, the Control Panel would then not show any Audacity version to uninstall.

Other than that you can still uninstall any version using unins000.exe in the installation directory.

Even if you add 2.1.2 from a ZIP file, any Explorer “Open with” associations you had created will still point to the original audacity.exe, and you won’t be able to add the new executable unless you name it as something other than “audacity.exe”.