@ultim Thanks for your firewall. I've never used it before but I got the feeling it won't disappoint me. I'm going to start trying it this weekend so I ask whether are you going to release a new beta this weekend apart from the one you did yesterday?
I wasn't planning to, but sure, I will release a new one a few hours later this evening. I have fixed a couple of issues in the latest test version myself, so I'll make those available. Thanks for helping with the test. Can you tell me which Windows version will you be installing it on?
Perhaps an idea to always update the website, to avoid confusing. OK, I see. I forgot that TinyWall didn't use a driver. I do know you will always need to sign a driver since Win 8. But I didn't know that it was such a hassle if you need to sign your software.
@ultim Beta crashes with an error at Windows start up on W8.1 physical machine. On W10 vm, TinyWall Service runs but TinyWall Controller gui won't show up at all.
Just published a hotfix for the stable release, 2.1.11. It fixes two issues that basically both had the same root cause, and resulted in the Connections window locking up the service, or the service not starting at all (depending on previous TinyWall settings). It was hitting some users and not others (for example, not me on any of my VMs), which made it somewhat difficult to track down and fix. Also, for example, the problem never occurred on fresh (and genuine) Windows installations. I'm not sure what is the greater mystery, the fact that this wasn't a problem earlier, or the settings needed on a machine to trigger the bug. It was clearly a bug though. I'm pretty sure you're hit by the same bug that I just fixed in 2.1.11. The 3.0 beta doesn't have that fix yet, but I'll update it. I still need to carry over the fix to the 3.0 branch.
... and now the changes from 2.1.11 has been ported to the beta build too. Use the previous download links to get the new beta. The only difference is this single (but rather important) fix. @Mr.X: Please try again, I'm sure it will work this time.
just giving some feedback on the beta version. when i restart my computer the icon won't be present in my system tray. i have to run the controller manually to get it to show up.
Here is a new test build of the latest development snapshot. I thought this is a good time to make one, because IMHO this version is pretty solid and yet also contains many of the new features – so you have a very good incentive to try it out This is the first release of TinyWall that does not require Windows Firewall anymore. You need not disable it (in which case just leave it in its default configuration), but it doesn’t matter much. Starting with this release, TinyWall is no longer just a GUI for the default Windows firewall, but instead it communicates directly with the filtering layers in the kernel. This huge change is what made most of the firewall improvements in the changelog below possible at all, while also bringing several security and performance advantages. But maybe most importantly, it allowed me to finally get rid of TinyWall’s annoying quirks that we all had to live with until now. You should be able to do everything and more in this build that you can do in TinyWall 2.1. Still, this release is not feature-complete, so expect more new features to pop up before TinyWall 3 final comes out. But first I need a broader test to solidify the groundwork. So please help with the testing, assuming you don’t bump into any major issues, it’ll be worth it Want to help? Here’s the download link. And here’s the changelog: Firewall technology improvements: - Rebuilt firewall on top of Windows Filtering Platform - Full support for File and Printer Sharing and Network Browser - Raw and promiscuous socket filtering - Apps are no longer disconnected when firewall reloads - Connections window need not be open to register blocked applications - Multicast support for local network firewall rules - Support for machine-global exceptions Installer improvements: - Install location can be customized - Warning about remote installations during setup - Slightly modernized installer look GUI improvements: - Automatic app recognition for drag&dropped files - Manual app detection gives instant first results - Live update of traffic rate in tray menu - Processes window remembers size - Much improved loading time of the Processes window - Don't list duplicate processes in Processes window General reliability improvements: - Atomic saving of configuration - Reduced probability of failed whitelisting attempts - Fix: Don't leave locked files on service exit - Fix: Race condition between update check and service message loop Deprecation notes: - Windows Vista no longer supported - 32-bit systems no longer supported Features disabled in the test build: - Binaries are not digitally signed - Automatic updates are disabled EDIT: @stuffedtiger, @Mr.X: The autostart on reboot is also fixed.
Tried the new tinywall, but had to uninstall. the service does not start, ram shoots up ,cpu spikes ,windows freezes, could not restart buffer error. Great program though.
Tried the beta but the tinywall service just starts and stops repeatedly until i disable the service. Had to uninstall. Sorry should have said, this is on a Windows 10 x64 bld 1903 machine.
@polly77 @askmark Please send me your C:\ProgramData\TinyWall\errorlog to tinywall[a.t]pados.hu . @askmark: Were you running any of those security software in your signature when you tested the beta? If yes then I'll have to check if maybe they were blocking TinyWall from doing something, which would explain why the service crashed.
I've pasted the contents of the log here: https://pastebin.com/GuYcBH7B Voodooshield, NVT OSArmour and NVT ERP 4 are all installed but their corresponding services disabled. I can try uninstalling them and see if it makes any difference.
Perfect, thanks. From your errorlog now I already know exactly which line of code is returning an error. I have just no idea why... I'll keep making some experiments to see if I can provoke it somehow. No need, thank you (I don't want to cause you too much trouble), I might ask you later if I fail to determine the cause myself, but for now I'll trust/assume that if they were disabled, then they weren't the problem.
Not sure if it's of interest but every failed start of tinywall.exe appears in the Window's Reliability Monitor. They all have the same detail (see below): Code: Description Faulting application name: TinyWall.exe, version: 2.99.3.0, time stamp: 0x5d4840cc Faulting module name: KERNELBASE.dll, version: 10.0.18362.239, time stamp: 0xb6f4b059 Exception code: 0xe0434352 Fault offset: 0x000000000003a839 Faulting process ID: 0x1fe0 Faulting application start time: 0x01d54c9e3ca59fd9 Faulting application path: C:\Program Files\TinyWall\TinyWall.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 762ef942-9e9f-4354-93a6-b1cd01a97442 Faulting package full name: Faulting package-relative application ID:
@askmark Can you please re-download the beta and send me the new errorlog? The problem won't be solved yet, but the new version logs the exact error code on your computer, so hopefully it will bring me a lot closer to a solution. Sorry for the trouble.
