@Peter Randziak
"In case you would like to test new build (users reporting this same issue told us that the issue does not reoccur with 6.0.13),"
Looking at the ESET site, i see the current build is 6.0.9.1, does this mean this is issue should have been fixed in 6.0.1.3?? The build number you entered doesnt make sense.