warning on splash screen

Avast Free Antivirus / Premium Security
1

I have a new warning on the splash screen…
The process cannot access the file because it is already being used by another process.
If you click the FAQ link it takes you to the page about the INI file… in the previous posts

I click OK and and the memory testing stalls.
stop the memory testing and it goes into the program just fine… but my memory isn’t getting scanned

whats up with this

2

What operating system do you use?

3

windows me

4

Could you please try to update to the latest avast beta, and if the problem reoccurs, send me the latest \data\log\error.log?

To install the beta, please run the program http://files.avast.com/files/beta/aswbeta.exe and follow the on-screen instructions.

Thanks
Vlk

5

Not wishing to Hijack this thread, but is there going to be an official beta notification for this on the Forums Vlk ?

6

I don’t think so, the only “fix” in it is the enhanced logging in the case of DB problems and a fix for the access-right issue discussed in another thread.

So it’s not really a “beta” - we’re just using the beta mechanism to distribute this testing update.

Thanks
Vlk

7

There were probably a few additional fixes or improvements (for example, the links in about dialog are doubleclickable now ;)) - but I don’t think an official update is to be expected any soon.

8

Thanks for the info, I guess I can wait for avast version 5.0 ;D

9

I installed the beta… I get the same message as before… “The process cannot access the file because it is being used by another process” and below that is states… “Program cannot set property in to main storage”

I have to stop the splash screen with cntrl/alt/delete then the program will open up the scan screen…
how do I send you the log files…

10

The beta is not really supposed to fix the problems as we don’t know what is causing them (and we are not able to simulate it on our machines - everything works correctly here).
Some more logging has been added to the beta that might help us to identify the problem.

Just click on Vlk’s profile - you’ll find his e-mail address there; that’s the best way to send the error.log file.
Thanks!

11

Igor, just for you to know, I’m on this beta ;D
I suppose the error.log is only generated if an error on scanning is found… am I wrong?
Is there any other side-effect on using the beta?