First, I’m an Avast user and not an Avast Team member.
There isn’t a great deal that ‘you’ can do related to corrupt archive files, Avast is just reporting files that ‘it’ can’t scan them and giving the reason why.
Given these are windows related files, you could try a google search on the related error message and location. If these apps and or services are working without error, personally I wouldn’t be unduly concerned. The Delivery Optimization is a windows update function and for most people unless they are updating other windows installations not really necessary. I actually have that service disabled after watching a YouTube video on this.
I’m not really sure why you re running a boot-time scan, I can’t recall the last time I ran one and I have been using Avast for 21 years.
I’m not really that good with security. I thought boot time scan is a more safe way to scan the computer and maybe find malware that is dormant/hidden or something like that. Maybe I am mistaken of course. Do you think it’s unnecessary?
So given these files are windows related is it most possibly just a bug or something or could it be really anything serious?
I tried searching the error message and location and only thing that comes up is a generic “corrupted zip file” thing. Thanks in advance
- With a resident (on-access) scanner the need for on-demand scans is much depreciated. For the most part dormant/inert files are being scanned, the other active files are going to be scanned by the resident shields when they are activated.
- The boot-time scan is designed more to be able to handle issues that otherwise can’t be handled whilst Windows is running.
As I said in my reply
The Delivery Optimization is a windows update function and for most people unless they are updating other windows installations not really necessary.
So this service for most people wouldn’t be being run, if it were and there was a file corruption problem I would expect/hope (wishful thinking perhaps) windows would handle it.
With a resident (on-access) scanner the need for on-demand scans is much depreciated (which would include the boot-time scan). For the most part dormant/inert files are being scanned (such as the ones in your screenshot), the other active files are going to be scanned by the resident shields when they are activated.
Yup, agree with DavidR. You should only need to run a boot time scan if you suspect something is wrong and a normal full scan reveals nothing.