I’ve used Avast for over 2 years now. Until Nov. 14, I never got the message “Some files could not be scanned” at the end of a scan. Since that day, I now get that message every time. When I look at the scan log, all the unscanned files are in C:\System VolumeInformation\restore; i.e., they’resystem restore files. I realize it doesn’t mean they’re infected; it just means Windows denies Avast’s access to them.
I’ve always had system restore files (never shut that function off). So why beginning 2 weeks ago did Windows suddenly decide to lock these files, and is there as way to unlock them so Avast! can scan them?
You're right. But password protected? Isn't it strange?
it depends what they are for....something that may be difficult to say when they are in system restor
But why worry...as you know it does not mean they are infected
if you ever have to use that restore point...then they will be scanned when unpacked
If your system is working correctly (so you currently don’t need old restore points), then disable System Restore, then reboot, re-enable System Restore, then reboot again. This will delete ALL System Restore Points.
You may want to manually create a new Restore Point at this point, since all the old ones are gone.
If the same message from Avast reappears in the future, please come back to report it.
Well, per Tech’s suggestion, I ran a boot-time scan, and sure enough, ALL files were scanned; no “Some files could not be scanned” message. But after that, I immediately ran a Quick Scan with Windows fully loaded…and the restore files again could not be scanned. The specific message under the Status column in the log is “Error: Archive is password protected (42056)”.
I realize this is a nuisance, not a serious issue, but I’m suspicious when a program behaves one way for almost 2 years, then suddenly starts behaving differently on a consistent basis. I will try zapping all the restore points, create a new one, then run another scan to see if it scans the new RP or continues to skip it.
Well, avast! did behave like this before, but lately Adobe started to pw-protect it’s updates, that’s most probably the reason you didn’t encounter this before.
OK, I turned System Restore (SR) off, which zapped all the restore points, rebooted, created a restore point, then ran a scan. Same result; every file in the System VolumeInformation/_restore subfolder is password protected. Now that there’s only one restore point in it, most of the files are .png (portable network graphics) or .js (JavaScript) files.
That these files are suddenly not scanable is not a big deal, but it signals that something in my system or the Avast software changed 2 weeks ago, and that’s what bothers me.
Don’t think you can. I was looking for an answer to the question, “What caused Avast to suddenly lose access to the system restore files.” The one suggestion to delete all the SR points, create one new point, then try a scan did not give Avast access to the files. If this forum had a “Solved” button for threads, I would click it, since I think I’ve gotten about as much information as I’m going to.
Maybe you missed something that was posted. Your first suspicion is that Avast is behaving differently. Maybe.
But maybe some other software is now behaving differently (Adobe password - protecting files) and that’s the reason. System Restore would be building the backups from the same files tahn before, but now those files are password protected, and Avast can’t do anything about it.
This is one possibility, already mentioned above. I’m just expanding the explanation.
If the original files were password protected, then as an when those are included in a restore point they too would be password protected.
So if you update or uninstall or delete a file/application and that had elements which were password protected that password protected would be in the restore point (that is the whole point of system restore to make copied of changed/removed certain files, etc.
I found the answer to the issue at techguy.org, the tech support forum I use 90% of the time when I have a technical issue. Turns out something (??) changed the permissions for the System Volume Information folder, removing me as having permission to open it. I had to use Safe Mode to access the Security tab under Folder Options to change the permissions to “Everyone”, but that solved the problem; Avast! now scans that folder and I get no “Some files could not be scanned” messages.
Thanks to all who contributed to this now solved issue.
That may “solve” the question (if you think you really solved something), but giving permissions to “Everyone” to the System Volume Information folder is not a good idea.
Why do you have the impression (or do you think) that these permissions were granted for “Everyone” before this “something” changed them? I mean, are you sure those were the security properties before this “problem” showed up?
Have no idea what the security was on that folder for the 3+ years I’ve had the computer… and frankly don’t care. I’m the only person who uses the computer, so giving “everyone” access to the System Volume Information folder means that I’m the only one who will access it.
