I’ve had my computer running a boot time scan, a day later and its only at 86%, scanning a drive that is not required for the running of my computer.
The method i’d thought of was to boot-time scan the necessary drives (C:\ and potentially another if you have program files on a non-ssd drive) then once the necessary drives have been scanned boot up with the un-scanned drives in a disabled/sandboxed mode, that way the computer can be used without being incapacitated for 24+ hours.
Is this plausible or is there another reason to have the boot time scan go through all drives pre-boot?
What setting changes did you make for the boot scan to take that long ???
Are you bypassing compressed files in the boot scan or, are they all being scanned ???
By default archives aren’t unpacked - so unless ‘alteration’ (ironic) has made any changes/alterations the scan shouldn’t take that long. Dependant on the quantity of data to be scanned, which we haven’t been told.
@ alteration
Now you can see why Bob asked the questions about your boot scan settings, see image of the default boot time scan settings.
The other thing is the areas to scan, the system Drive by default would only be for the SSD if that is your system drive - the drive you install programs on wouldn’t be scanned if you haven’t selected All Drives. The auto start programs would be scanned no matter what location they are in.
I disagree that All Drives need to be scanned - With a resident on-access antivirus like avast, the need for frequent on-demand scans (or boot-time scan) is much depreciated. For the most part the on-demand scan is going to be scanning files that would be otherwise be dormant or inert. If they were active files then the on-access file system shield would be scanning them before being created, modified, opened or executed.