You don't have to open the Settings panel from the tray. You can click on the popup notification after whitelisting a single entry, which brings you directly to the exception details. Alternatively, you can select the "Prompt for exception details" in the General settings, which saves you even an additional click (then you'll always get the dialog).
Sure, simply kill the service process from the Task Manager, it will be restarted immediately with a clean state. By the way, when this happens, do you see a higher CPU usage by TinyWall's service at the same time?
My apologies, I should have told that I tried, killing both the tray and the service to be sure, and it did not work. I'll be sure to check it next time it happens.
Well, the service is getting restarted, so it must be picking up some erroneous state from the running system. Might this be the thought-to-be fixed parent-process tracking problem from earlier? (rhetorical question) I'll take a guess and add extra guard logic in there. I'll give you an experimental fix in PM this evening.
Ok, thanks. I wasn't really aware of that, and it will for sure make it quicker and easier, although having an extra entry in the right-click would have been even more convenient, avoiding any additional windows or dialogs.
I understand, but then where do I stop? Somebody will ask for menu entries for outgoing only and in&out permissions separately (edit: this did happen actually). Another person will want a local-network-only whitelist entry. A third person will want to create 5-min rules menu for online installers. And so... My point is, if I were to start a system like this, I could fill up the screen with all the different whitelisting options. There is a user for every such option. Instead, the current GUI allows you to customize any new rule the way you want with as few as only two extra mouse clicks.
You stop when you decide you want to. And if that is at the current state, that's fine by me. I just happen to think this option might be worth having a separate entry for, but I have absolutely no problem accepting that you feel it will create too much clutter. I'm still happy with the product you have provided, and will continue to use it.
How about black leather seats with red piping? Or notification pop-ups? (Only kidding about the last one!)
I can confirm that the Windows Defender check box is working. I have just noticed I have a new version and the TinyWall lets it through. Thank you.
Version 3.0 is released! Aaaand.... a very big Thanks to everybody here!!! I don't think there is a need to describe the countless improvements and new features to anybody in this forum, but as for the changes since the last beta, here's the list: - Fix GUI crash when whitelisting from Connections form while server is locked - Fix GUI crash when error is returned in response to reading the connection log - Extra guards for when Windows returns false parent-PID information - Persist the timestamp of the last update check on disk - Updated profile for IE on Win8.1 - Improved French localization If you are on a beta right now, you should be getting an update notice within the next 2 days. I have not yet enabled automatic updates for v2.1-users yet, I'll wait a week before doing that. If you are currently using v2.1 and you don't want to wait until then, you can get the new release from the homepage. A couple of days ago I also launched my Patreon. If you are against that though, there are countless other ways too to support me. Here are a couple of ideas: - Tell your friends about TinyWall, share it, tweet it, discuss it - Give it upvotes on sites like alternativeto.net or slant.co - Write a blog entry or review about TinyWall - Give TinyWall a star rating on a download site if you like it - Improve or add to TinyWall's localizations Thanks for staying with me until now, for testing, installing, and putting up with various bugs in the beta releases, for your bug reports, ideas and help in general. TinyWall 3.0 is just a new milestone, a very large one at that, but TinyWall's story is nowhere near done. I'll keep on improving it as long as I see there is enough interest out there.
Hi Ultim, First thank you for the new version. I have tried uninstalling v 2.1 without success. After uninstalling, the folder c:\program\data\tinywall remains. In the folder there are 2 log files which I deleted manually, and a file called eh52mmf1.kbb which I cannot delete. It says "the action can't be completed because the file is open in another program". I uninstalled then reinstalled again. I uninstalled again by first disabling tinywall service. No luck. I went into safe mode but got the same message. Any help will be appreciated. This is strange, I cannot install v3.0 because it won't uninstall v2.1. Thank you very much.
True, it is strange, this does not normally happen. It is perfectly normal for some data or log files to remain in c:\programdata\tinywall, but it is not nomal for files there to be continued to be locked or used. I suggest after you perform an uninstall of TinyWall v2.1 that you restart your computer once. If after that you still cannot install 3.0, I'll offer you a TeamViewer session to have a look at it personally.
Hi Ultim, Thank you for your response. I was able to remove the file. It was an old .kbb file, which is a keyblock backup file. I unplugged my ethernet cable, unencrypted, and removed the file. I then was able to install the new tinywall version. It is slightly disconcerting since when I viewed the .kbb file, it was filled with random Chinese characters. I lived in China for a long time and still spend time there. If noone else has ever mentioned this, then I'll assume it is just something strange. I'll keep an eye on the folder to see if it reoccurs, although I doubt it will. Thank you very much for getting back to me. I look forward to using the new version. All the best.
TinyWall 3.0 for Windows introduces major changes March 23, 2020 https://www.ghacks.net/2020/03/23/tinywall-3-0-for-windows-introduces-major-changes/
Hi, ok, thank you. Yes please let me know if you notice anything strange in the future. For now you were the first with something like this. I also have no idea what a "keyblock" file is, and I can also tell you it was not placed there by TinyWall. So I'm guessing there might be another app on your system that is playing a role here.
To any Moderators out there: Is there a way to get permission to change the contents of the first post (and thread title with it)?
Will try to use this software again, around mid this year when my ESET IS expires. I'll most likely "downgrade" to NOD32 and get this as firewall.
