Odtnhj

Do to much movement in Get-NetFirewallPortFilter.
IDK.. how to fastest..

$RuleCount = 0;
$total = (Get-NetFirewallRule).Count;
$testcount = 0;

Get-NetFirewallRule|ForEach-Object 
 $Rule = $_;
 $portfilter = Get-NetFirewallPortFilter

You should expect this to take time, as you are asking the portfilter to check all its rules against the firewall rules, which just is checking all the rules against itself.

Example:

I don't know how many rules you are dealing with, but on my standalone system:

($total = (Get-NetFirewallRule).count)
783

($portfilter = Get-NetFirewallPortFilter).Count
783

This means that is code is running 1566 times (on my system), because you are asking the filter each one of its own rules against all 783 portfilter rules against the 783 firewall rules to create your object. ForLoops are just slow, and with 1566 passes, in my case, well you should gather how much this will add up.

If you did this for just one firewall rule, you'd get something like:

Measure-Command 
$RuleCount = 0
$testcount = 0
($total = (Get-NetFirewallRule).count)
($portfilter = Get-NetFirewallPortFilter).Count

ForEach($Rule in (Get-NetFirewallRule 

Days : 0
Hours : 0
Minutes : 0
Seconds : 2 ********* * times the total needed passes 
Milliseconds : 414
Ticks : 24149617
TotalDays : 2.79509456018519E-05
TotalHours : 0.000670822694444444
TotalMinutes : 0.0402493616666667
TotalSeconds : 2.4149617 **************
TotalMilliseconds : 2414.9617

If we tweak your code a bit more to show more information / progress, say like this...

Clear-Host
$total = (Get-NetFirewallRule).count
$total1 = (Get-NetFirewallPortFilter).Count

$RuleCount = 0

ForEach($Rule in (Get-NetFirewallRule | Select -First 3))
 
 ForEach-Object 
 Write-host "Processing port rule $($_.Name)" -ForegroundColor Yellow

 $testcount++
 $perc1 = [Int]($testcount/$total1*100)
 Write-Progress -Activity 'My Important Port rules' -PercentComplete $perc1 -Status $perc1 -Id 2
 
 Write-Warning -Message "$testcount "



Processing firewall rule vm-monitoring-dcom
Processing port rule 
...
WARNING: 783 
Processing firewall rule vm-monitoring-icmpv4
Processing port rule 
...
WARNING: 783 
Processing firewall rule vm-monitoring-icmpv6
Processing port rule 
...
WARNING: 783 

… it should further illustrate what I am trying to say.

Then you have the limitations of your system itself, processor speed, memory resources / speed, any other processes you are running on your machine.

See this similar Q&A discussion:

How can I speed up PowerShell to get firewall rules on windows 10?

#Using a registry approach

param
( 
 [switch]$Local, 
 [switch]$GPO 
) 

# If no switches are set the script will default to local firewall rules 
if (!($Local) -and !($Gpo)) 
 $Local = $true 

$RegistryKeys = @() 

if ($Local) $RegistryKeys += 'Registry::HKLMSystemCurrentControlSetServicesSharedAccessParametersFirewallPolicyFirewallRules' 
if ($GPO) $RegistryKeys += 'Registry::HKLMSoftwarePoliciesMicrosoftWindowsFirewallFirewallRules' 

Foreach ($Key in $RegistryKeys) 
 
 if (Test-Path -Path $Key) 
 
 (Get-ItemProperty -Path $Key).PSObject.Members 

and the link from that post as to:

2.2.2.19 Firewall Rule and the Firewall Rule Grammar Rule