"Windows Operating System" keeps blocking my torrent port

I keep getting firewall blocked logs for “Windows Operating System” for udp port 6600. I have this app added to allow this port in network policy , i even tried adding it in svchost, there is no app in my network policy named as such so i even tried making the one listed “system” as trust all but nothing changed so i just set it back to block". I then tried to add port 6600 to port set. Hopefully someone can help me this is driving me nuts and hindering my upload/leechers torrent connection.

Did you also add it to the Global Rules to allow incoming traffic?

If you have a deny IP any any rule on the bottom of global rules you need to add a

Allow
In
UDP
Source port Any
Destination port 6600
Source Any
Destination Any

To allow this traffic globally.

thanks just tried adding it and its still happening only rule i have below it is block icmp. In my firewall log its showing blocked udp port, destination ip 192.168.1.108 destination 6600, source appears randomn

I deleted my torrent rules and created these based from a thread i found but my firewall kept logging that my torrent app is blocking attempts [at] udp dest address 192.168.1.xxx and dest port 6060, so i had to add an allow one for that and blocks on 6060 are now gone, but it seems as though my torrent client doesnt find even close to the right amount of leechers available, so ul speed is slow and when its faster its just because of one source. In peers i see a lot of times out connecting
Why is this 192.168.1.xxx(my ipv4address in ipconfig) address needed, if in rules below i used MAC address
Im connected by cable from linksys router.
Im wandering if i need to modify network zones , what should i have in there?
Also my svchost uses that 192.168.1.xxx

Option 2 - Deny use of privileged ports (Recommended for additional security, but might cause problems due to some ports being blocked)

Go to Firewall->Advanced->Network Security Policy->Global Rules and add the following rule above all blocking (red) rules:

Action: Allow
Protocol: TCP or UDP
Direction: In
Description: Allow incoming traffic for uTorrent
Source Address: Any
Destination Address: Your IP/MAC or Any
Source Port: 1025-65535
Destination Port: uTorrent-port

Now go to Firewall → Advanced → Network Security Policy → Application Rules, and add these for uTorrent.exe:

Rule 1

Action: Allow
Protocol: TCP or UDP
Direction: In
Description: Allow incoming traffic
Source Address: Any
Destination Address: Your IP/MAC or Any
Source Port: 1025-65535
Destination Port: uTorrent port

Rule 2

Action: Allow
Protocol: TCP or UDP
Direction: Out
Description: Allow outgoing traffic
Source Address: Your IP/MAC or Any
Destination Address: Any
Source Port: 1025-65535
Destination Port: 1025-65535

Rule 3

Action: Allow
Protocol: TCP
Direction: Out
Description: Allow outgoing HTTP-traffic
Source Address: Your IP/MAC or Any
Destination Address: Any
Source Port: 1025-65535
Destination Port: 80

Rule 4

Action: Allow
Protocol: UDP
Direction: Out
Description: Allow DNS-requests
Source Address: Your IP/MAC or Any
Destination Address: Any or your DNS server (can be found by launching cmd.exe and writing ‘ipconfig /all’.
Source Port: 1025-65535
Destination Port: 53

If you have more than one DNS-server, add a rule for each of them.

Rule 5

Action: Block
Protocol: TCP or UDP
Direction: Out
Description: Block outgoing traffic on privileged ports
Source Address: Your IP/MAC or Any
Destination Address: Any
Source Port: 1-1024
Destination Port: 1-1024

Rule 6

Action: Block
Protocol: TCP or UDP
Direction: In
Description: Block incoming traffic on privileged ports
Source Address: Any
Destination Address: Your IP/MAC or Any
Source Port: 1-1024
Destination Port: 1-1024

Rule 5 and 6 will prevent connections to privileged ports from getting logged, so that CFP 3 won’t log a lot of intrusion attempts.

Rule 7

Action: Block (mark ‘Log as firewall event if this rule is fired’)
Protocol: IP
Direction: Out
Description: Block and log outgoing traffic
Source Address: Your IP/MAC or Any
Destination Address: Any

Rule 8

Action: Block (mark ‘Log as firewall event if this rule is fired’)
Protocol: IP
Direction: In
Description: Block and log incoming traffic
Source Address: Any
Destination Address: Your IP/MAC or Any

I think the issue is caused by restricting 1-1024, can you set your rules 5&6 to log and see how many denies this generates?