Still getting corrupt files with 2302, no diffrence to 2289 except the version number has changed. I don't understand how its possible to release build after build with the same bug? To fix it you have to be able to reproduce it - Assuming you have done this then you test your software to see if it stops it happening. Assuming the opposite that they can't reproduce the error then why release a new build as its not going to change anything. Clearly they don't test the builds at all, how can you even consider releasing a new build without having a test rig producing the error then you fix it. Whats more embarrasing they seem to have gone through 13 internal builds and got nowhere!