AVG blocking Intel Arc Graphics install

[Bill65]

I'm attempting to install the following Intel graphic driver version 32.0.101.8247 and AVG blocks it saying its infected with IDP.HELU.PSE53.

In my install history it appears that version 32.0.101.8136 is the last successful install.

I was going to create a command line exception to allow the new update to be installed but AVG does not recommend that.

Is there a work around that will allow the new update to be installed without creating a security issue.

Please see attachments for additional details.

[sim1]

The AV I'm running blocks it too. It seems the archive exe runs a Powershell script encoded in base64 via the command line, which looks exactly like what a lazy hacker does to install malware:

"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -EncodedCommand "cABhAHIAYQBtACgAWwBzAHQAcgBpAG4AZwBdACQARQB4AHAAZQBjAHQAZQBkAEMAaABlAGMAawBzAHUAbQAgAD0AIAAnADEANQA4ADgAMgAzADEAMQAxADIAOAA4ADYANgAyADkANwA1ADgANQAyADUAOAA1ADMAMQA2ADgAMgAwADUAMgA5ADQANQA4ADQAOAA5ADgANwA3ADgANgA5ADEAMgA4ADYAOAA5ADcANgAyADgANAA1ADUAMAAwADMAMAA0ADgAMgAxADkAMgAyADgANQA4ADkAMAA2ADcANQAxADkAMQAnACkADQAKAA0ACgAkAGUAeABwAGUAYwB0AGUAZAAgAD0AIABbAFMAeQBzAHQAZQBtAC4ATgB1AG0AZQByAGkAYwBzAC4AQgBpAGcASQBuAHQAZQBnAGUAcgBdADoAOgBQAGEAcgBzAGUAKAAkAEUAeABwAGUAYwB0AGUAZABDAGgAZQBjAGsAcwB1AG0AKQANAAoAJABzAGYAeABBAHIAZwBzACAAIAA9ACAAWwBFAG4AdgBpAHIAbwBuAG0AZQBuAHQAXQA6ADoARwBlAHQARQBuAHYAaQByAG8AbgBtAGUAbgB0AFYAYQByAGkAYQBiAGwAZQAoACcAcwBmAHgAYwBtAGQAJwAsACcAUAByAG8AYwBlAHMAcwAnACkADQAKAA0ACgAkAHMAdQBtACAAPQAgAFsAUwB5AHMAdABlAG0ALgBOAHUAbQBlAHIAaQBjAHMALgBCAGkAZwBJAG4AdABlAGcAZQByAF0AOgA6AFoAZQByAG8ADQAKAEcAZQB0AC0AQwBoAGkAbABkAEkAdABlAG0AIAAtAEYAaQBsAGUAIAAtAFIAZQBjAHUAcgBzAGUAIAB8ACAARgBvAHIARQBhAGMAaAAtAE8AYgBqAGUAYwB0ACAAewANAAoAIAAgACAAIAAkAGgAYQBzAGgAIAA9ACAARwBlAHQALQBGAGkAbABlAEgAYQBzAGgAIAAkAF8ALgBGAHUAbABsAE4AYQBtAGUAIAAtAEEAbABnAG8AcgBpAHQAaABtACAAUwBIAEEAMgA1ADYADQAKACAAIAAgACAAJABzAHUAbQAgACsAPQAgAFsAUwB5AHMAdABlAG0ALgBOAHUAbQBlAHIAaQBjAHMALgBCAGkAZwBJAG4AdABlAGcAZQByAF0AOgA6AFAAYQByAHMAZQAoACcAMAAwACcAIAArACAAJABoAGEAcwBoAC4ASABhAHMAaAAsACAAWwBTAHkAcwB0AGUAbQAuAEcAbABvAGIAYQBsAGkAegBhAHQAaQBvAG4ALgBOAHUAbQBiAGUAcgBTAHQAeQBsAGUAcwBdADoAOgBIAGUAeABOAHUAbQBiAGUAcgApAA0ACgB9AA0ACgANAAoAaQBmACAAKAAkAHMAdQBtACAALQBlAHEAIAAkAGUAeABwAGUAYwB0AGUAZAApACAAewANAAoAIAAgACAAIAAkAHAAcgBvAGMAIAA9ACAAUwB0AGEAcgB0AC0AUAByAG8AYwBlAHMAcwAgAC0ARgBpAGwAZQBQAGEAdABoACAAJwBJAG4AcwB0AGEAbABsAGUAcgAuAGUAeABlACcAIAAtAEEAcgBnAHUAbQBlAG4AdABMAGkAcwB0ACAAJABzAGYAeABBAHIAZwBzACAALQBXAGEAaQB0ACAALQBQAGEAcwBzAFQAaAByAHUADQAKACAAIAAgACAAZQB4AGkAdAAgACQAcAByAG8AYwAuAEUAeABpAHQAQwBvAGQAZQANAAoAfQANAAoAZQBsAHMAZQAgAHsADQAKACAAIAAgACAAQQBkAGQALQBUAHkAcABlACAALQBBAHMAcwBlAG0AYgBsAHkATgBhAG0AZQAgAFMAeQBzAHQAZQBtAC4AVwBpAG4AZABvAHcAcwAuAEYAbwByAG0AcwANAAoAIAAgACAAIAAkAG0AcwBnACAAPQAgACcAVABoAGUAIABpAG4AcwB0AGEAbABsAGEAdABpAG8AbgAgAGMAYQBuAG4AbwB0ACAAcwB0AGEAcgB0ACAAYgBlAGMAYQB1AHMAZQAgAHQAaABlACAAZgBpAGwAZQAgAGkAbgB0AGUAZwByAGkAdAB5ACAAYwBoAGUAYwBrACAAZgBhAGkAbABlAGQALgAgAFQAaABlACAAcABhAGMAawBhAGcAZQAgAGEAcABwAGUAYQByAHMAIAB0AG8AIABiAGUAIABjAG8AcgByAHUAcAB0AGUAZAAgAG8AcgAgAG0AbwBkAGkAZgBpAGUAZAAuACAAUABsAGUAYQBzAGUAIABkAG8AdwBuAGwAbwBhAGQAIAB0AGgAZQAgAGQAcgBpAHYAZQByACAAYQBuAGQAIAB0AHIAeQAgAGEAZwBhAGkAbgAuACAASQBmACAAdABoAGUAIABwAHIAbwBiAGwAZQBtACAAcABlAHIAcwBpAHMAdABzACwAIAB2AGkAcwBpAHQAIAB3AHcAdwAuAGkAbgB0AGUAbAAuAGMAbwBtAC8AcwB1AHAAcABvAHIAdAAgAGYAbwByACAAYQBzAHMAaQBzAHQAYQBuAGMAZQAuACcADQAKACAAIAAgACAAWwB2AG8AaQBkAF0AWwBTAHkAcwB0AGUAbQAuAFcAaQBuAGQAbwB3AHMALgBGAG8AcgBtAHMALgBNAGUAcwBzAGEAZwBlAEIAbwB4AF0AOgA6AFMAaABvAHcAKAAkAG0AcwBnACwAJwBFAHIAcgBvAHIAJwAsAFsAUwB5AHMAdABlAG0ALgBXAGkAbgBkAG8AdwBzAC4ARgBvAHIAbQBzAC4ATQBlAHMAcwBhAGcAZQBCAG8AeABCAHUAdAB0AG8AbgBzAF0AOgA6AE8ASwAsAFsAUwB5AHMAdABlAG0ALgBXAGkAbgBkAG8AdwBzAC4ARgBvAHIAbQBzAC4ATQBlAHMAcwBhAGcAZQBCAG8AeABJAGMAbwBuAF0AOgA6AEUAcgByAG8AcgApAA0ACgAgACAAIAAgAGUAeABpAHQAIAAxAA0ACgB9AA=="

The script itself seems to just be a file integrity check, but they've never done this before, which is a bit suspicious. They should probably do this another way.

[Bill65]

Thank you Sim1. I wonder if anyone has a work around to solve this issue?

[RMZahn]

for me the same!
Norton blocks as well

log-file available

[RMZahn]

file manually downloaded run as admin - same result 😞

[Mike_Intel]

Hello Bill65,

Thank you for posting in Intel community Forum.

For me to better understand and diagnose the issue further, let me ask you to provide detailed responses to the following questions. This information will help me isolate the problem and determine the most appropriate course of action moving forward.

1. Can you tell me the brand and model of your system?
2. What is the model of the Graphics controller?
3. What is the model of the processor?
4. Are you having the same if you download the driver manually and install it manually?
5. For me to review hardware and the installed driver, please help generate the SSU logs of your system. Kindly refer to the link below for the steps:

How to get the Intel® System Support Utility Logs on Windows*

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[Bill65]

Hi Michael 

Thanks for you help.

I've attached the SSU scan of my system and the system info from my machine which is probably the same but less detailed.

I have not tried manually downloaded/installed the driver. Others have said they have had that issue with manually d/l and installing.

My system was custom built so it's not a mass production machine.

I you need an additional info please feel free to reach out.

Bill

[Larry_VonLobster]

I had the same problem with Avast, I downloaded the update first on the intel website as package, deactivated the safety modules for an our, after deactivating I started the update manually. After that I restarted the pc and it worked