Why are you so stubborn? Nobody is talking about a date or month, @askmark gave you a link for the latest beta. Latest beta is 2.99.9. Use this one *******!
You need to calm down first of all. The point is that I'm not using one of the first beta's. And I made a mistake, I'm using v 2.99.8.
Please always use the latest version when reporting errors, especially with betas. 2.99.9 was almost purely a bugfix release, and among many things it fixed a GUI crash too that often happened when opening the tray menu - since this aligns with your error report, I'd like to ask you to install the latest beta and check again before I investigate any further.
For compatibility reasons with Windows updates, I think it would be better if Tinywall could work with Windows defender firewall
Isn't that just the new name for the Windows Firewall? Tinywall beta can already work with or without it.
Ah, so you mean, Tinywall stable (2.1.10) can only work if Windows Firewall is ON, while Tinywall beta (2.99.9) can work with Windows Firewall either ON or OFF
Correct. The former is a GUI for WF. The latter is based on WFP and currently works with or without WF.
The beta links I publish are only valid for 1 month each time. New version should come soon now. Boot-time filtering is an invasive change and hence time-consuming and I also had my long trip last month.
So, here it is, another major and important new feature: Boot-time filtering. This means starting with this release, with TinyWall there is not a single point in time where your firewall rules are not in effect or not filtering. All filters are active even before TinyWall's service starts up, right from the get-go when the IP-stack is initialized during early boot. This is yet another step-up from the standard Windows Firewall, which does not have this. Other than boot-time filters, there are only a few minor fixes, which IMHO is a good sign. Changelog 2.99.10: - New: Boot-time filtering and protection - Increase application compatibility by filtering socket accept() instead of listen() - Profile fixes for file sharing, printer sharing, and time synchronization (for W10) [Download] Window 10 v1909 was also released recently. So in case anybody was wondering if it breaks anything with TinyWall, no it does not, all is fine. I checked documentation and also tested personally on this new Windows version. There is one more major feature I want to experiment with (optional inheriting rules to child processes) before I release 3.0. I'm not sure yet if it is plausible to implement without a driver effectively (for those who don't know, TinyWall does not install drivers), but I'll find out once I've coded it. With some luck, the next beta will have that, and then we're in bug-fix-only mode. If I'd have to guess, I'd put a public and officially stable release to January (as far as I'm concerned though the current beta is pretty stable too, I just don't feel like it received enough testing). There are many more ideas for features and improvements, but they will have to wait after post-3.0, after all, I need to put an end to the current development cycle at some point. Thank you again for all who help with testing the betas.
Great news indeed and thank you for your time and efforts. Sorry but I don't have the time or skills to do so. But anything I notice while using my daily stuff I'll let you know.
That's perfect, and is exactly what I've meant by testing: Just install the beta and use it as you normally would Thanks!
It works perfectly fine alongside WF. Just remember that both firewalls can block apps separately, so if you add any blocking rules to WF, you won't be able to whitelist the same apps in TinyWall (and vice-versa). My official recommendation is, when you install TinyWall, you should not disable Windows Firewall, but you should leave it in (or reset it to) its default configuration.
I've been running v2.1.12 for about a month now and had a few questions about some the following situations. Is there a way to keep a "Windows App" whitelisted? It would seem that when an app is updated it also changes the directory and therefore is not whitelisted anymore. Example: C:\Program Files\WindowsApps\Microsoft.BingWeather_4.32.12463.0_x64__8wekyb3d8bbwe\Microsoft.Msn.Weather.exe C:\Program Files\WindowsApps\Microsoft.BingWeather_4.33.13094.0_x64__8wekyb3d8bbwe\Microsoft.Msn.Weather.exe Does tinywall keep a hash of any whitelisted executable to prevent a simple replacement of a previously whitelisted exe with a malicious one? Is there a way to whitelist an entire directory and keep it whitelisted? I have some applications that may create files/folders when updated that need to be whitelisted and whitelisting manually on every update is a real chore. Thanks
> Is there a way to keep a "Windows App" whitelisted? It would seem that when an app is updated it also changes the directory and therefore is not whitelisted anymore. This is due to the missing support for Windows Store apps in the current version. There is no current way around this in TinyWall, but I hope to implement a solution in a future version. > Does tinywall keep a hash of any whitelisted executable to prevent a simple replacement of a previously whitelisted exe with a malicious one? No, it does not. Any checks that are done are done at the time of whitelisting, after that any executable under the same path is whitelisted until the firewall rule is removed. > Is there a way to whitelist an entire directory and keep it whitelisted? I am working on a similar feature now which I can hopefully make part of the next release.
I have started using the latest Beta version, now that it is close to release. It's a definite improvement over last release version and very smooth so far. Thank you.
I am back using your firewall again Karoly, 2.99.10 version. I stopped when there was troubles with W10 and what with the hackers and stuff on my computer and used only WFW, it allowing everything out. Now I'm happy to have your TinyWall back
Hello! I am a beginner and I just installed TFW on two PC's, one with w7 and other with w10. Before to install TFW I can establish a home network but noe TFW does not allow me to configure the advanced sharing settings to allow network detection etc... I have marked in TFW "desbloquear trafico de red local" Some help please? JM
Hi, TinyWall 2.1 has known issues with Windows file sharing. Instead of describing how to work around it, I recommend you install this pre-release version. It has no known issues and the problems related to Windows networks and sharing are resolved and gone. p.s. TinyWall is not Tiny (Personal) Firewall. The latter is a different product by an unrelated developer. I wrote above advice assuming you are here actually for TinyWall and not for Tiny Personal Firewall, which I know nothing about.
Bwah, basically it detected TinyWall because of a partial string-match to the name of TinyWallet. What a great and sophisticated heuristic engine...