Many thanks, I am going to uninstall TW and I will install new pre-release. I will post here the result.
I updated to v2.99.10. All went smoothly except for the following notes: * (As with v2.99.9) The installation put the tick back in "Enable global hotkeys", and reset the settings for the Connections window. * The issues I was having with Windows file shares not coming back after a reboot appears to be solved ... I think. I had to untick/tick Unblock LAN Traffic and then reboot again before the problem (as relates to Windows file shares) really seemed to clear on one system I tried. * Some systems do still have an issue with Unblock LAN Traffic - After a reboot I still have to untick and then retick before non-windows local connections can be established. This is true even if the program is in the exception list. (Before this update I was only checking Windows file shares, I didn't realise that was a separate problem to all these other connections - devices like security cameras, printers, routers and so on.) Note that this Unblock LAN Traffic issue is probably not a TinyWall problem as such. I've also got a new clean Windows 10 1903 virtual machine build and it does not suffer from this problem, so there seems to be something in my other systems (both virtual machines and hosts) that causes this ... I haven't been able to work out what yet. So generally good, but still some niggles.
Hello, I tried to install the beta version and this is the message that appears: "This installation package is not compatble wuith this kind of precessor"
Hi asilesoft, Do you have a 32-bit Windows system? TinyWall 2.1. was compatible with both 32-bit and 64-bit systems, but the newer TinyWall and its beta only runs on 64-bits.
Using Tiny 2.1 how can I open for LAN the files and printers sharing? Need I to uninstall TW 32 bits?
With TW 2.1 you cannot use the network browser of Windows Explorer. You can share files and use shares by mounting them as a drive letter. The computer browser works starting with TW3.
I've been trying to uninstall v2.99.10 from one machine but it keeps coming up: "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." I click the okay button and it appears to undo whatever it was it had done. The controller has exited, but restarting it (or the machine) seems to have everything working as normal - but TinyWall was not removed. I get the same problem whether I use the uninstall option from the Windows 10 Settings, or whether I right click on the MSI installer and choose Uninstall (or repair). I cannot manually disable the TinyWall service ... so how can I clean this up? What I want is to completely clean it out, and then re-install it to see whether I could get rid of the problems I have with things not working on reboot until I untick and tick Unblock LAN Traffic. The problem doesn't affect a clean Windows build so I've experimented with resetting and then disabling the Windows Firewall with no change. Now I wanted a completely clean TinyWall install - any help would be appreciated.
Thanks for that, Betazzone, but it turns out that ... I found out how to kill the TinyWall service, and after I did that the normal uninstall worked. To kill the TinyWall service: In Services set TinyWall Service to "Disabled" (to stop it automatically restarting) From admin command prompt: Code: sc queryex TinyWall that gives you the service PID, which you type into: Code: taskkill /f /PID nnn As I said, after that I could uninstall. Not that it helped. After uninstall and resetting the Windows Firewall to defaults, I proved the network was all restoring properly after a reboot. (You start up an the file shares show red Xs but clicking on them immediately reestablishes the connection.) Then I installed v2.99.10 again and the old problems came back, this time with network shares not coming back either (red Xs but clicking on them delays and then reports failure). These problem don't happen on a clean Windows 10 1903 virtual machine, so I am still baffled as to why it's happening on this Windows 10 1903 virtual machine (and several others).
When you cannot uninstall TinyWall, the only reason I am aware of is TinyWall.exe has been deleted/removed before running the uninstaller. This has happened recently due to false positives with Avast. If this happens in the future, I'd check if your antivirus has quarantined TinyWall.exe, and restore it. Then uninstalling should work to the best of my knowledge. No known problems at least.
I had problems uninstalling it yesterday and had to do a similar process. I am running Windows Defender on 64 bit Windows 10 1909. The uninstaller stopped with an error but I cannot remember what it said.
In the cases such as above, TinyWall.exe was still obviously present, otherwise the service would not have been running. To debug such a case, I would need the uninstaller log created by MSI if somebody can provide it to me. Here's how to do this.
Contents of log file: Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action UninstallCustom, location: C:\Program Files\TinyWall\TinyWall.exe, command: /uninstall === Logging stopped: 08/12/2019 20:36:43 ===
That's the message I got on the screen (as reported above). And TinyWall.exe was definitely there in my case too because (as I wrote earlier) killing the service process was what I had to do before the uninstall would work. I am also running just the default Windows Defender on Windows 10 (64bit), in my case build 1903. No other firewall or AV products active on that machine. ultim, I remember that the uninstall got past the point of asking if I initiated the uninstall, and the controller process on the taskbar was stopped. That's about as much of a hint as I can give regarding how far it got before failing. Edited to add: I also remember that there was a noticeable delay (10sec? I didn't time it). My guess would be it's your uninstall waiting for the process to end - but it never does.
TinyWall 2.1.13. released with a fix for CVE-2019-19470 discovered by security researchers at CODE WHITE GmbH. An attacker who has already compromised the local system could use TinyWall Controller to gain additional privileges by attaching a debugger to the running process and modifying the code in memory. This release fixes that. Update available from website, and soon over the built-in self-update function.
Sometimes, randomly, TW tray icon doesn't show up at startup. It started to happen after last Patch Tuesday update for Windows 8.1: Monthly Quality Rollup for Windows 8.1 KB4453070 I don't know whether the update is related to this issue or coincidence though. Also it happens on another W8.1 machine so that makes two different hardware scenarios. Code: http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/12/windows8.1-kb4530702-x64_8a3d5f3eb996149590805699de1e65c37c57a5f1.msu