Thank you for the reply. I still get the Incorrect Function error even when TinyWall is on Autolearn.
It's developed by, Karoly Pados, I'm looking into the rest. I will add what I find here. EDIT The Developer Owns it, here is his email address: Károly Pados, tinywall@pados.hu I don't know if he is here on Wilders, maybe someone could invite him ?
I got that Info off of the software's website, was I looking in the wrong place ? tinywall.pados.hu If that's not the right site can you link me brother ? Thanks
You've got the right info. I was just letting you know the dev is active on Wilders and his username.
One should not mix the firewall names. There used to exist in the olden times a software firewall called Tiny. There was nothing tiny about it though. https://www.cnet.com/products/tiny-personal-firewall-3-0/review/ Also TinyWall despite it's name is not tiny in it's protective capabilities. But certainly has one of the cleanest fast to learn interface.
I couldn't get Chrome to detect my ipv6. It seems TinyWall blocks it on the System level. ipv6 does get detected when TinyWall is disabled.
Sorry if my question looks silly, but did you enable the "Special Exceptions" for "Filtered ICMP traffic" and "Windows DHCP Client" ?
Here are some logs of app crash: Faulting application name: TinyWall.exe, version: 2.1.8.0, time stamp: 0x56e1e785 Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a146b Exception code: 0xe0434352 Fault offset: 0x0000000000033c58 Faulting process id: 0xa28 Faulting application start time: 0x01d3020f4d8ce18c Faulting application path: C:\Program Files (x86)\TinyWall\TinyWall.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 9c32db33-e299-4ad9-80a1-d65d534d4801 Faulting package full name: Faulting package-relative application ID: and: 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()
It also happened to me once. I re-enabled the normal mode by right-clicking the tray icon and it came back to work as expected. I'll post again if I get any news
Sup fellas, I have been watching this and the TinyWall site with interest, I may jump in and tinker, My question is can we import existing windows firewall rules into Tiny ? or I guess a better question is will it overwrite my existing rules on install ?
it will overwrite your existing rules, but it comes with some predefined rules you can use for essential windows processes. then, you'll have to manually add rules for apps that need internet access, but it's a very easy task with a single window to set everything
Yes, I just resurrected an old image with TinyWall and it did overwrite the existing rules. Seems to be working fine as of the moment.
Since MS/Google/.. and others have decided to drop StartCom it's not possible (in the traditional ways) to install TinyWall. Which means you get the 'application blocked' msg from Windows. http://i.imgur.com/PYNwXxG.png http://i.imgur.com/KxqqgSx.png it would be also good to know if that project is finally dead or not, cause since months no words or updates.
Try to run it as administrator. I'm using tinywall on Win10 latest stable build and everything is working fine
TinyWall is at the latest version and manages the Windows Firewall. Its not in need of frequent updates like third party fws are that completely replace WF on a day to day basis.
There are known bugs and I could add and list some more which are urgent need to be fixed. The author really should wake up and response here, otherwise I report this on several pages now as 'not under development'. That could all have been avoided just releasing the source code, but sigh ... The author seems to not care, not even the homepage works anymore because certificate. At this point I can't recommend it to use, so better go with the integrated firewall or use another one. @ Wilders Admin, pls close the TinyWall threads, makes no sense to leave it open until the developer give us a response. There tons of obsolete and outdated GUI's already, we not need another one.