Firewall does not detecting Adobe Acrobat.exe connecting to the internet.
Firewall settings: Custom Rules.
v12.0.0.6882 do it.
Please see attachment.
Regards
Could you show or state what process is being blocked by the Firewall? Is it AcroRd32.exe?
What is not being blocked ? Is it about automatic updating? That may be done by another process than the reader executable AcroRd32.exe.
In the past Acrobat Reader was quite a naughty program when it comes to updating. Iirc it was member Radaghast who found it when it is not allowed to update it will try to use BITS service (Background Intelligence Transfer Service) or svchost.exe instead to update.
I got tired of the Adobe Update running, so I just turned it to Manual in Services. Checked and its armsvc.exe, which updates all Adobe software according to the description
Setup Details:
In order to install online setups, please ensure you have following entries in Windows hosts (c:/windows/system32/drivers/etc/hosts) file:
178.255.86.194 download.comodo.com
178.255.86.194 www.download.comodo.com
i wonder what are they cooking for beta 2… 
really excited about it…
Maybe Valkyrie will be made to send for verification.)))
Sorry I had not seen
It’s OK
Thank you megaherz33 :-TU
Adobe.exe (belong to Adobe Acrobat) call at home (Adobe) and FW does not detecting this connection.
v12.0.0.6882 detect this connection.
Regards
Getting that same error when I try to install the beta of the firewall.
I just tried adding those entries to the host file and got the same error.
Like this
How do you determine it was successfully calling home? Because the updater ran? If that is the case then the updating gets done by armsvc.exe as Ploget stated and not adobe.exe.
Please see attachment CFW_12.0.0.6882_Blocked_Applications.png
Regards
Problem with the Security Centre fixed and all working well now
The problem was that since the inception of CCAV, I’ve been running it alongside CIS with no faults at all - it just blended seamlessly. Even Umesh ran it that way also . . .
This Beta put a stop to that as I just found out! I had an idea that there may be a conflict as no one else reported the fault, so uninstalled CCAV, ran the CIS Uninstaller, re-installed CIS and Win 10 Security Centre is now happy. Oh well - goodbye to CCAV and maybe one of the reasons it was discontinued
Undertaker…Which version of windows are you running?
Win 7 SP1 x64
Regards
Hi Ploget,
Thank you for the update.
So i too had the 404 error. Adding this two entries to hosts allowed me to run the installer.
However all I use is Firewall. Is there a way to install it’s beta without the AV?
Courtesy of futuretech
Now updated 2 Win10 Pro machines to 1909 (1836.476) with this Beta 6938
All chugging along nicely with no problems or Security Centre issues. Everything looking stable and smooth