Windows 10: Cryptographic Services and other Windows Services firewall rules

Cryptographic Services is frequently requesting to connect to port 80 at remote IP addresses. is there a range I can specify in my firewall configuration for this and other windows update related services to access to?

I'd much rather not allow all outbound traffic from this service, as that's a remarkably poor security model to expect people to allow. Ideally, if there were one single address which this service connected to would be ideal, but I assume there's some load balancing and DDOS attack resisting requirement for multiple addresses. however, that would not explain the number of discrete remote addresses on different subnets?

:)

 

Windows 10 Firewall won't keep my inbound/outbound rules

Hi,

I realize the inconvenience caused to you regarding the Windows Firewall. I will certainly assist you.

I suggest you to restart the Windows firewall service and check if it helps.

Follow the below steps for the same.

• Press Windows key + R simultaneously for Run.
• Type services.msc and then Enter.
• Right click on the Windows firewall services and then restart the services and check if it helps.

If the issue still persists then I suggest you to remove and then read the Windows fire wall rule.

Hope this information is helpful. Please get back to us with the information required, if you need further assistance, we’ll be glad to assist you.

 

Cryptographic Services Failed

Hello,

Thank you for visiting Microsoft Community.

Did you make any changes to your computer prior to this issue?

I would suggest you to refer to the suggestions provided by szz743 replied on January 24, 2014 and check if it helps.

Cryptographic Services failed while processing the OnIdentity() call

Cryptographic Services failed while processing the OnIdentity() call

Please do let us know if you need any further assistance, we will be glad to assist you.

Thank you.

 

Firewall rule doesn't work

Hi,

my default setting for the firewall is to block all traffic. Exceptions are added if necessary. This strategy will not be changed for there is no clarity regarding all the traffic going on. For instance, two exceptions enable DNS and DHCP. This works well.
Another one is svchost, service="Cryptographic services" (CryptSvc). The latter does
not work. This means, the firewall still blocks these packets. I have verified my rule multiple times, even removed it and added it again.

As the normal firewall log file isn't speaking enough, I have enabled logging of dropped packets in the event log via group policies. I wrote a little program for live observation of these log entries. Thereby, I am able to lookup the services from the logged
process ID.





The firewall rule exactly matches this case. Consequently, the packet should not be blocked. The rule is: Allow, Outgoing, program=svchost, service=CryptSvc, all profiles, all local ports, all IPs, protocol TCP, remote ports 80 and 443.

So my question is: Why does the firewall block packets even if a rule allows them? (There is no other rule denying it)

Win 10 x64 Pro

Thanks