Windows 10: Explain Ports to me as it works in Tinywall Firewall

I'm trying the latest version of Tinywall. Tinywall is a Windows Firewall Front End that helps you configure the built in Windows firewall better than you can without it. Tinywall's claim to fame is by default it blocks Everything, then Only allows the applications, processes or services through the firewall that I expressly tell it to allow.

I see under Show Connections if I have Open Ports checked, I get a list of what I presume to be, Open ports (open meaning unblocked IMO). Yet, if I right click on any of the ports, there is an option for UnBlock. there is also an option to kill leading me to believe these ports are open and active with outgoing connections. . - If these ports are Blocked, then How can they be open? This is confusing and misleading to me. Are these ports open or blocked?

There are a lot of ports most "duplicates?" Two lsass.exe's many Services.exe's and scvhost.exe's, many System(4)'s and a few Wininit.exe's The only one in the list I know is the Chrome.exe I manually set a rule for so I could access the internet.

I don't want anything going in or out that I don't specify, the PC should look and act as if it's not connected the the internet at all save when I tell it to open Chrome. The state on all these ports are Listening - why listen when i don't want or need them to run? - or do I? Are these ports somehow needed for Chrome to work? What Exactly are these ports, how can I determine if i need them or not, and how can i block them? If I can block them, I don't want to ever see them in this list again. I ask several question here, can someone please go through the post and try to answer all of them. Thank you!

:)

 

RESOLVED - Windows Defender Firewall - Conflicts with Tinywall

Why does Windows Defender Firewall cause conflict with Tinywall. My Tinywall icon sits in the tray icon area all greyed out with Unknown Mode status.

Whilst Tinywall is installed Windows Defender Firewall also blocks internet access. To resolve the issue I have to turn Windows Defender Firewall off from the control panel and turn it on again.

Basically in recent updates Tinywall has been rendered useless by Windows Defender Firewall. How can I run Tinywall and WIndows Defender Firewall side-by-side?

When I turn Windows Defender Firewall off and launch Tinywall, Windows Defender Firewall automatically re-enables itself. Surely this seems like the code is intentionally targeting Tinywall.

Best security and protection comes in layers. I'd rather completely disable Windows Defender Firewal and stick to using Tinywall.

 

RESOLVED - Windows Defender Firewall - Conflicts with Tinywall

Forgive me for sounding my objections but your line of questioning seems irrelevant. After starting the Tinywall Service it keeps getting stopped. Do the 2 event log entries below offer any clues?

Event 1

Application: TinyWall.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.Runtime.InteropServices.COMException

at NetFwTypeLib.INetFwRules.Remove(System.String)

at PKSoft.WindowsFirewall.Rules.ClearItems()

at PKSoft.TinyWallService.InitFirewall()

at PKSoft.TinyWallService.ProcessCmd(PKSoft.Message)

at PKSoft.TinyWallService.FirewallWorkerMethod()

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Threading.ThreadHelper.ThreadStart()

Event 2

Faulting application name: TinyWall.exe, version: 2.1.8.0, time stamp: 0x56e1e785

Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x4736733c

Exception code: 0xe0434352

Fault offset: 0x0000000000013fb8

Faulting process id: 0x2328

Faulting application start time: 0x01d35f49f17ed077

Faulting application path: C:\Program Files (x86)\TinyWall\TinyWall.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: ae260407-8bef-4220-8112-de486f1d8bda

Faulting package full name:

Faulting package-relative application ID: