avast! blocking and quarantining pCloud client app

Avast Free Antivirus / Premium Security
1

https://www.pcloud.com/download-free-online-cloud-file-storage.html

I’ve tried updating pCloud Windows 10 client yesterday and avast! blocked two things (one in ProgramData\PackageCache and another in .\TEMP_avast_\unpXXXXXX.tmp) in the installer with Behavior Shield and one component (cbfsinstall.exe as Dyna:Persistence-CU) with DeepScreen.

What’s weird is the detection of a file in avast!'s own TEMP unpacking folder. Is that intended behavior now or something weird going on? Certainly false positives that shouldn’t have happened.

EDIT:
Moved it here because I somehow managed to post it into BETA section…

2

I have had the same issue just now, with the result that I am now unable to access my Pcloud folders…very annoying.

Did you find a way around it you are willing to share ?

3

You can report a suspected FP (File/Website) here: https://www.avast.com/false-positive-file-form.php

4

I had the same stupid nonsense on 3 systems. Worst of all, DeepScreen says “IGNORED” yet it clearly trashed everything. After long time of not using avast! I had to remove it from all of my systems. It was this annoying. Come on avast! team, you can do better than this.

5

Has this been looked into to prevent future breakdown of pCloud installer caused by avast! false detection?

6

Seriously, fix this trash. I’ve dumped avast! on all my systems because of this. You can’t even exclude things from stupid DeepScreen and the damn thing even says IGNORED but botches the installer anyway wrecking everything up. Arrgh.

7

Hi, did you report it…? (Reply #2)

8

I’ve reported it here. The report form wants stupid reCAPTCHA and I don’t do those things coz it keeps rolling them billion times for me.

9

Good luck…! :wink:

10

Come on, this is ridiculous. The “Report as false positive” on DeepScreen popup literally does NOTHING. I was clicking it like mad and just nothing happened. At all. I also can’t extract the stupid file from pCloud installer that’s triggering the detection as it gets “Ignored” (that’s literally DeepScreen’s verdict) yet f**ks up the entire installation anyway.

8. 07. 2020 21:09:43 Autosandbox candidate: C:\ProgramData\Package Cache\F4A595785D327A491C83171BCFA3CCBD2CFE0F39\cbfsinstall.exe [Source: local://*C:\Users\RejZoR\AppData\Local\Temp\{6C2C540F-ACB6-48FB-9F57-249DEA2C65B5}\.be\pCloud Drive.exe ] [Opened by: C:\ProgramData\Package Cache\F4A595785D327A491C83171BCFA3CCBD2CFE0F39\cbfsinstall.exe] [Reason: 0x00020000] --> Result: Sandboxing (file was marked as infected) --> Instrumentation: Instrumentation inside sandbox requested

Can someone look at the bloody thing and fix it already?