I noticed on a standard scan with no archive scanning (the first since the new V4.8) there are a few pauses during certain files (eg windows update (hot fixes etc), install record files etc), is this anything to be worried about or is to do with the new anti-rootkit checking?
The scan percentage complete reading didnt move from 1% for the first 100,000 files and then it started increasing quite fast as it started scanning the system files, will there be refinements to how it judges progress completed in future?
I didnt notice it scanning the system restore folder like it use to do in V4.7, v4.7 use to linger on this folder for a long time yet now it seems to skip it or am I mistaken?
I also noted that no results screen at the end of the scan (the one that says whether there was decompression bombs etc), I find it odd because my steam files use to show up on it as being corrupt due to the packer not being supported but now nothing comes up
sorry for the large queries but I forget these things otherwise and why they are fresh in my mind I thought I would ask, again sorry for the large volume of queries
I wouldn’t be worried about it, but I don’t think it related to anti-rootkit scanning.
No idea what it might be… shouldn’t be different from 4.7 I think. However, it’s hard to say more without checking the exact files/folders that cause the delays (if it’s reproducible exactly).
Hard to say. The progress estimation is, and always will be, inexact (unless we want to double the time and perform the whole “initial scan” just to estimate how long the second pass will take). However, the number of files doesn’t have to be the right variable to match the progress against (e.g. in thorough mode) - the time should be. But - what I wrote in the previous sentence still applies.
This will be correct in the next program update (or maybe sooner).
The particular unpacker may have been updated - so that it doesn’t consider the archives to be corrupted, but unpacks them successfully. Again, hard to say without checking the files themselves.
the files that usually are displayed as corrupt are steam files (valve software) but now no screen appears saying it, is there a way of checking if an option has been disabled that would prevent the actions log being displayed or is it due to no problems being present that it has not been displayed