Avast and Dwservice/Dwagent

Avast Free Antivirus / Premium Security
1

Hi,

For remote connection to Windows 10 screen I’m using dwagent/dwservice (www.dwservice.net).

But frequently and always when avast screen is open, the remote connection is forced in view only mode and so becoming useless.

How to solve that ?

Thanks for your help.

2
  • Which Avast…? (Free/Premium)
  • 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…?
3

the requested info:

  • Avast free, probably version 20.7.2425
  • Windows 10 2004 (19041.508) - x64
  • no other security related software installed

NB: to keep the business on, I had to uninstall Avast and switch to native windows defender

Best reagards,
André.

4

Update to the latest version (20.8.2429): https://forum.avast.com/index.php?topic=238421.0

5

Hi,

I do not want to put again the business at risk.
Nothing in the change log related to this issue.

Could you confirm that “this feature” is fixed or this is just to see if be chance…

Thanks.

6

Free Avast version 20.8.2429 (20.8.5653.561) tested on a spare Windows 10 (2004).

Same bad behaviour …

Any screen/process to register an allowed remote access program ?

Thanks to help to manage that blocking issue

7

→ https://support.avast.com/article/Antivirus-scan-exclusions
→ https://support.avast.com/article/298/ (Blocked & Allowed apps)

8

Both already tested but no success

screen remains not mangeable remotely

9

Do you get any warning from Avast…? Post a screenshot.

10

Not a single message …

Only remote available option is a logout or reboot via ALT-CTRL-DEL

11

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

12

Application is not blocked.

Only access to the screen, keyboard and mouse is frozen.

13

You can submit a bug report in “About Avast”. (Add a link to this thread)

14

I can confirm the above behaviour with the latest version of Avast. Actually, the Avast on the remote connection is not completely frozen. If you send a CTRL-ALT-DEL request, it triggers the standard Windows blue screen, from which selecting the Task Manager takes focus from the Avast window and the remote connection can be used again.

I was trying to exclude the DWservice daemon from being scanned by adding all sorts of exclusions to the Avast installation to no avail. It would be really useful to have the exclusions working on Avast, I have the same negative experience also with executed script programmes on Windows (Perl and Pyton), where regardless of any formulated exclusions, Avast is still checking them fully (as can be seen from the processor load during their execution).

15

You are posting in an olde topic. If you have a problem, please start your own topic and give us details.