No result message appears when CyberCapture finishes analyzing files

[AnthonyQ]

Hi,

In the past, when CyberCapture determines a suspicious file needs to be sent to the Virus Lab for further analysis, relevant log will shows in the Notification; also, when the analysis is complete and the file is quarantined or kept based on the result of analysis, a message will appear informing users of the result (see below). Now, no such message will appear when CyberCapture finishes analyzing files. However, depending on the outcome, files will be quarantined or kept, without users being notified.



I hope Avast can inform users of the status of the files sent after analysis.

[Asyn]

Repair Avast:
1. Avast GUI -> Settings -> Troubleshooting
2. Click on 'REPAIR APP'.
3. Follow instructions.
4. Reboot.

[AnthonyQ]

Repair Avast:
1. Avast GUI -> Settings -> Troubleshooting
2. Click on 'REPAIR APP'.
3. Follow instructions.
4. Reboot.

Hi, just tried, but it doesn't work. Seems like a bug?

[Asyn]

- Which Avast..? (Free/Premium/One)
- Which version/build of Avast..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

[AnthonyQ]

- Which Avast..? (Free/Premium/One)
- Which version/build of Avast..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

Avast Antivirus Premium
Version 22.2.6003 (Build 22.2.7013.717)
Win 11 64 bit 21H2
No.
Kaspersky, ESET, Norton - they are fully removed

[Asyn]

Hi, are you maybe running Avast in silent mode and/or DND mode..!?

[AnthonyQ]

Hi, are you maybe running Avast in silent mode and/or DND mode..!?

Hi, Not in slient mode. Other notifications/alerts (when detecting threats) are able to appear.

[Asyn]

1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

[AnthonyQ]

1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

Hi, I think it's hard to reproduce this issue as CyberCapture is only triggered when user is trying to access unknown & suspicious files. I currently don't have such file. 

[Asyn]

1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

Hi, I think it's hard to reproduce this issue as CyberCapture is only triggered when user is trying to access unknown & suspicious files. I currently don't have such file. 

Well, according to you other thread (https://forum.avast.com/index.php?topic=318874.0) I thought you might have some.

[AnthonyQ]

1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

Hi, I think it's hard to reproduce this issue as CyberCapture is only triggered when user is trying to access unknown & suspicious files. I currently don't have such file. 

Well, according to you other thread (https://forum.avast.com/index.php?topic=318874.0) I thought you might have some.

Just tried to open a file... CyberCapture triggered and file has been sent...

File ID: 39BPN

[Asyn]

Just tried to open a file... CyberCapture triggered and file has been sent...

File ID: 39BPN

Ok, I forwarded it, let's see...

[Asyn]

Dev-Info: Fix will be released with version 22.4

[AnthonyQ]

Dev-Info: Fix will be released with version 22.4

Thanks for the update. Glad to know they have indentified and fixed the problem. When will this build be released?

[Asyn]

Dev-Info: Fix will be released with version 22.4

Thanks for the update. Glad to know they have indentified and fixed the problem. When will this build be released?

You're welcome and thanks for the report. (Can't comment on the ETA, sorry.)