For some reason my “c:\User\D…\AppData\Local\Microsoft\Outlook\Outlook.pst” is no longer being scanned because “the process cannot access the file because another process has locked a portion of the file(33)”
Never had this happen before with this location and nothing has changed. Seeing that the outlook file is important I’d like it to be scanned. I have turned off Outlook and it still won’t scan it.
I did the update yesterday. Scan last night shows same problem - “can’t scan Outlook.pst because another process has locked a portion of the file (33)”
Is there any way I can tell what process has the file locked?
I always forget I have Unlocker! I closed Outlook, went to the outlook.pst file and clicked Unlocker. Says nothing is locking it, no handlers found. So, I got out of that, choosing No Action. Then used my right click/Scan with Avast on just the outlook.pst file. Scanned it no problem.
I know almost nothing about this stuff, but I have two thoughts.
Is the scan Avast does from the menu on one file different than the scan it does at night while doing a full scan?
I leave Outlook open all the time. And Avast never used to have a problem scanning it while open until this last update. Should it matter to Avast if Outlook is running?
I ran Unlocker again, only I left Outlook running this time. I’ve attached a screen shot of the results. Unfortunately, it doesn’t mean much to me. It looks to me like it is saying that it can’t access the outlook.pst file because the process outlook.exe has it locked. Wouldn’t that be a normal state? I’m also curious why I seem to be the only one having this issue. I’m not comfortable not having this particular file not being scanned. I can start closing it every night if that will allow it to scan, but I’ve been using it this way for years. Why has it changed now?
I closed Outlook yesterday at the end of my day. When Avast scanned at 3:30 a.m. (with Outlook not running) I got NO messages this morning. Meaning it did scan outlook.pst.
I don’t get why it just started not liking that it is running while being scanned, but it’s not a big deal for me to close it. I do think I’ll send a message to Support though.
It is also a dangerous file to scan. There are many that warn against it, can’t recall the references.
I don’t use Outlook, so I can’t speak from personal experience. Essentially .pst files if an infected email is found inside many AVs (not necessarily avast!) will delete the complete .pst file not try to extract the infected email with the resultant loss of your emails.
I believe if you check the Mail Shield, Expert Settings, MS Outlook related settings, the Scan archived messages when opening, these aren’t scanned by default and my guess that has something to do with scanning (or not) the .pst file also. But the advice is to scan only unread messages, see image extract of the avast Help Center.
Hi David!
Thanks for that reply! What you have said makes perfect sense.
Because I don’t really “get” what scanning is doing, I just know I need to do it to keep my computer safe, the .pst file seemed like an important one to keep clean. But your explanation clears up my questions. I’ve never understood the .pst file but you are right, I certainly wouldn’t want it deleted! I just didn’t know what else was in there besides emails.
I don’t know if it might have been a change in the default avast MS Outlook settings or as a result of a windows security update.
But the error 33 is as has been said the crux of the matter as it wouldn’t really have thought it would be avast locking it, whereby it couldn’t scan it. That could be a) MS Outlook trying to protect the file (possibly in use, etc.) or b) other security software locking the file preventing avast from scanning it…