Intel® Driver & Support Assistant vs. F-Secure Total

Botte42

I am using Intel DSA for updating of drivers in my laptop. When I tried to install drivers for Intel graphics ("Intel® Graphics Driver 32.0.101.7080 for 11th-14th Gen Intel® Core™ Processor Graphics") the installation program was blocked by F-Secure:

"Program blockerat", with information:

I tried to allow this program in the F-Secure app, but it seemed to ignore that, running a new installation came out with the same blocking again.

Is there any solution for this issue? Is F-Secure making a mistake?

Botte42

Latest news:

I have now tried to disable all device protection functions in my Internet security app F-Secure Total, and executed the Intel DSA web app once more.

Success! The installation succeeded this time.

I suppose the next update from DSA will fail in the same matter 🙁.

I have informed the F-Secure support about it, the problem, my work-around, and the outcome. I'll inform you about their answer to my message when I get it.

Botte42

Has it anything to do with the recent update och the F-Secure app?

Intel DSA has been working allright for me for at least 3 years.

Ukko

Hello,

// well, I saw it a later (edited): your search query in F-Secure threat descriptions is "TR/SensorBased". So, it is likely then related to mentioned "Firewall Sensor" option below. You can try to disable it and re-check situation if you want. Or just to use information and report it to F-Secure Labs via SAS page.

Original content of comment:

You can try disabling some options in the settings. For example, to temporarily disable "firewall sensor" in F-Secure Device Protection's settings (the feature is introduced in 25.9; you recently got 25.10; if this feature is a reason for detection, then maybe you did not use this tool for a while). And see if there is any difference.

You can also re-check how to add the blocked app to the exception list or "allow" it. Some parts of detection is not visible in screenshot and I am not really familiar with this situation (I used to use this tool without any problems, just like you; but I haven't used it lately).

Since your main screenshot with mentions of powershell error. Perhaps, the detection is due "AMSI" integration. This is another option in F-Secure Device Protection's settings. But it's more likely that this is simply a side effect of some file being inaccessible because blocked by F-Secure.

Anyway, excluding paths or files is not the most recommended step. So, it's probably best to send an executable sample to F-Secure Labs so they can check the situation and fix the detection or explain the reasons. F-Secure SAS is available at: https://www.f-secure.com/en/support/submit-a-sample

Thanks!

Botte42

Thanks Ukko, I'll send a SMS to the support like you said as the first step. I also have an on-going case/dialogue about this matter with Intel Support (based in India!).

So, I'll wait for their answers before trying your advice about "firewall sensor".