Please try 2.99.11 from the previous post. Due to large changes to GUI initialization it might actually fix your case (though only by chance). And even if it doesn't, it will give you a stacktrace (that I need for further analysis) with the log for the GUI when it crashes.
Thanks but digital signature dates back to November 18 2019. This belongs to the last installer you posted on that date.
That's what I get for not running my Nextcloud sync client all the time, it was still the old installer. Fixed now.
Hi gmw, With the new build I notice even File Sharing is working flawlessly now. The only gripe I had and explained to you, the half-minute delay after boot, is completely gone. I'm too lazy now to bisect which change corrected the problem, but if I had to guess it was either the fix for WAF or the DNS. Can you check if your problem went away too?
While attempting to install it: Clicked OK, then Finish, installer closes but TinyWall wasn't installed. Windows 8.1 x64
Just to be sure, please check after a reboot. If something is left inside the GAC (but marked for deletion), it could result in this. But I admit, unlikely this happened. I need time to think and/or more info. In my tests on W10 and W7 no problems. Anyway please check after a reboot.
Here using Shadow Defender so when I restarted the PC modifications were gone. I got this in GAC from previous installations: Spoiler
Oh, well, that is/was then most likely the problem. So does that mean you were able to install the new beta after the reboot? Otherwise you need to remove those GAC entries. The catch is that since relatively recently, you cannot do that using Windows Explorer anymore thanks to Microsoft removing the needed shell extension. I also wonder how those remained. Security software on the computer are my first suspects. Second is "manual" uninstallation. Anyway, this doesn't look like at all to be a problem with TinyWall AFAICT, so no need for others to be concerned. Also, the new beta doesn't use the GAC anymore so no matter what you do, this is impossible to happen in the future. Nevertheless I'll help you clean those up of course if your problem is not already solved.
There aren't. The reason is, even if checksumming was implemented, you couldn't trust it, because TinyWall would only be able to recognize the change after some small time window, and if the change was malicious, in that time the modified software could have already been started. Also, on most computers software tends to get updated often, so checking for file alterations would be annoying for most users. Annoying + ineffective = no thanks. However, TinyWall does check digital certificates at least during whitelisting, that is what gives you the green/blue/red bars at the top of the exception details dialog. I also have plans for the future to further extend the checks on files during whitelisting. If you wish to prevent unauthorized modifications after whitelisting, install your apps to Program Files and do not use the admin account for daily tasks.
Didn't try again. I was waiting for your reply. Not sure what you mean, so what exactly I need to remove them? Are you talking about this? https://docs.microsoft.com/en-us/dotnet/framework/app-domains/how-to-remove-an-assembly-from-the-gac Those entries are "leftovers" from 2.99.10 and probably previous versions, don't know. Yes I've played with manual uninstallations before.
The official MS tool is gacutil, yes. But you won't have it unless you have the .Net SDK, and also you'd need two different versions because there are separate GACs for CLR2 and CLR4, and a single gacutil version can only handle one of them. So, I recommend GACBrowser instead, which can handle both GAC versions as well as being a graphical tool. Run it as admin after install, then remove any and all versions of the following assemblies: - TinyWall - TinyWall.Interface - TinyWall.resources - WFPdotNet - Interop.NetFwTypeLib (or NetFwTypeLib) After you're done, you'll still have native images left over, but by themselves they shouldn't cause problems anymore, so you can leave them be (unless you're bothered by the ~2MB disk space they consume). Then try installing 2.99.11 again.
No prob, just remove anything with GACBrowser that has TinyWall in its name, and don't forget about the WFPdotNet and NetFwTypeLib stuff. Then try the new installer again.
Alright let me clear this up a little bit more. GAC Browser is not detecting it yet that folder exists under C:\Windows\assembly\NativeImages_v2.0.50727_64\TinyWall.resources Windows Explorer can browse it. Still a no problem?
Yeah, as I said earlier, cleaning up with gacbrowser or gacutil will still leave you with native images left over (look at the folder name). Removing these requires a different tool (ngen.exe) but they shouldn't cause problems so you can leave them alone.
Okaaaay, let's continue this conversation in PM. As of now the download count of the new installer is well over two dozens, yet nobody else reported problems, so I'm still assuming this a problem isolated to your computer. We'll continue in private to leave the others in peace.
Windows 10 Home 1909 OS build: 18363.535 AV: Kaspersky Cloud Free Account: SUA Issues: 1. Kaspersky Cloud Network (KSN) can't connect even with the process being whitelisted. It only connects on auto-learn or disable mode 2. On Wi-Fi. When laptop goes to sleep after a while the connection gets lost. To fix I need to disable firewall then disconnect and re-connect the Wi-Fi
Did you check the blocked connections list of TinyWall? You just need to figure out what to whitelist, it will help you do that.
Yes. I did checked the blocked connection list. Even when I ublocked the process the KSN still wouldn't connect.
For anybody wondering, the problem on Mr.X's computer is solved. It was not a problem with the current build.
Using the latest beta, when the network is changing, all connexions seem block. Simply triggering a change in Tinywall (like activating and deactivating block lists) will make everything work again. It's a new installation, on Windows 10 19.09.
