Boot scan found infected files but could not delete them

Viruses and worms
1

Hello, I ran a scheduled boot scan and got the following results, should I be concerned? Looks like files could not be deleted by AVAST, but I’m not sure how to interpret. After Windows 7 booted up, I scanned each listed file and got “no threat found” on each. Thanks for any help, I’m a novice at this!

File C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount\Windows\System32\bcdboot.exe is infected by Other:Malware-gen [Trj], Delete: Error 0xC0000279 {The layered file system driver for this IO tag did not handle it when needed.}
File C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount\Windows\System32\cscript.exe is infected by Other:Malware-gen [Trj], Delete: Error 0xC0000279 {The layered file system driver for this IO tag did not handle it when needed.}
File C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount\Windows\WinSxS\amd64_microsoft-windows-bcdboot-cmdlinetool_31bf3856ad364e35_10.0.10586.0_none_eddb7cede87b99bf\bcdboot.exe is infected by Other:Malware-gen [Trj], Delete: Error 0xC0000279 {The layered file system driver for this IO tag did not handle it when needed.}
File C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount\Windows\WinSxS\amd64_microsoft-windows-scripting_31bf3856ad364e35_10.0.10586.0_none_d4edeb6eaab124ac\cscript.exe is infected by Other:Malware-gen [Trj], Delete: Error 0xC0000279 {The layered file system driver for this IO tag did not handle it when needed.}
Number of searched folders: 45345
Number of tested files: 884987
Number of infected files: 4

2

seems to be False positive on Win10 update files

3

Thanks!

4

any special reason why you did a boot scan?

5

It had been a while since I did one.

6

It is not meant to be used as a regular scanner and it does not give any better detection, what it give is better removal of some infections

7

How often should one do a “boot scan” then? I’ve never done one…I just run the regular scan… Quick Scan, every day. Is that enough?

8

For me it was once, when I first installed avast 12 years ago. It is a special scan that is generally only used if there is a problem dealing with an infection in normal windows mode.

Or if you get a detection by avast in a normal scan it will most likely suggest running a boot-time scan.

With a resident on-access antivirus like avast, the need for frequent on-demand scans 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.

I used to have avast set to do a scheduled weekly Quick scan, set at a time and day that I know the computer will be on. But I have ceased this practice for some time now, based in the above.

9

I just got the same issue. Boots scans always fixed problem but this can not be fixed by Avast. Probably get a different virus scanner and try again?

10

what was detected?
what location of detected file(s) … full file path

11

Exactly what FrankH initially described in this email . Having the same virus alert as he describs. No fix automatically or delete is possible (Avast says cant access file) . When I searched the file manually and run a Avast scan just on this file , it says the same “no access” . So I dont know if I simply just delete the file and remove it from the PC but I do not know what the file is needed for in Windows OS?

12
Exactly what FrankH initially described in this email ........
Then as said above, it is a False Positive detection on Win10 update files
13

Hello, this FP was fixed 22.04. Upgrade your virus database please.

14

Great , the fix worked . thanks