Ueseter

The first sentence quoted above is the exact sweet answer I was looking for. But just to clarify on the second sentence, the offline scan is referring to the scan I did right? (you're trying to differentiate what I did from ESET's online scan offering?) And thanks for the links. They're way above my head but I did learn some interesting things from it.

I did update the BIOS firmware but since I got no CD-Rom drive or USB with write-protection I loaded a USB with most updated BIOS file and set it to read-only. I also checked the SHA256 hash code of the BIOS file on the USB before and after I updated the BIOS to make sure the BIOS file remained unchanged. But stupidly the SSD was connected to the motherboard during bios update though the SSD was brand new. Do you think that could wipe any BIOS viruses? I had to improvise lol I'd rather not take apart my newly assembled PC. I'm happy enough nothing short circuited on my first attempt.

Thank you for posting. But the answer you have given is similar to other threads but the meaning or implication of the answer is not clear to me that's why I started this new post. When you said "If they are locked for an antivirus, they are locked also for malware" can I then safely conclude based on that statement and my log above that my BIOS/UEFI is clean?

Hi, I recently assembled my own PC using a supposedly brand new motherboard but one that doesn't come sealed in any way when delivered. So I got worried and came across Eset as one of the few AVs that can scan UEFI or BIOS for viruses/malware. But I'm having some trouble using the scan. It seems to be unable to scan the BIOS/UEFI files as it can't open the necessary files for scanning. I read some other posts in this forum regarding the "unable to open" log messages but the answers given were not clear to me as a non techie person. I tried scanning the UEFI through "Custom Scan" -> "Boot sectors/UEFI" and ran the scan as Administrator. Below is the resulting log: Log Scan Log Version of detection engine: 26208 (20221105) Date: 6/11/2022 Time: 5:09:28 pm Scanned disks, folders and files: Boot sectors/UEFI \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD - unable to open [4] \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD.LOG - unable to open [4] Number of scanned objects: 141 Number of detections: 0 Time of completion: 5:09:28 pm Total scanning time: 0 sec (00:00:00) Notes: [4] Object cannot be opened. It may be in use by another application or operating system. My questions are the following: -are the files listed in the log as unopenable supposed to be unopenable or am I using the scan wrong? -If the scan is unable to open those files detailed in above log does it mean that my BIOS/UEFI is clean? -If the scan is able to open those unopenable files above does it mean that my BIOS/UEFI is compromised in some way? -according to the following link Eset will be able to scan those unopenable files during startup and shut down but I can't find the logs of those scans happening during startup or shutdown. Why? (link: https://support.eset.com/en/kb2155-error-notifications-in-computer-scan-log)