Yes I did that (thanks for the reminder to check again). Afaik the MsMpEng.exe shouldn't pop up there anymore after the dev fixed something with "registry paths". Maybe Microsoft changed it again in some way. https://www.wilderssecurity.com/threads/tinywall-firewall.309739/page-90#post-3045798
I installed tinywall 3.2.5 . it's running but any rules apllied with it are not working. any applications can bypassing tinywall. please help me to solving the problems.
@ultim I'm having issues with network shares, Windows to Windows machines. Two of them, one W7 the other one is brand new W10 21H2 x64. Windows Explorer cannot see each other shares and as soon as I disable TW, shares are seen again. File and Printer Sharing option is checked in TW.
After investigating I found that 3 windows services must be allowed to make Network Shares work again on both W7 and W10 machines. Code: Function Discovery Provider Host (fdPHost) Function Discovery Resource Publication (FDResPub) SSDP Discovery (SSDPSRV) I set them to Unrestricted UDP and TCP traffic and Restrict to local network.
@ultim I apologize for reposting, maybe you didn't notice my previous posts. Hope you're fine. I'm having issues with network shares, Windows to Windows machines. Two of them, one W7 the other one is brand new W10 21H2 x64. Windows Explorer cannot see each other shares and as soon as I disable TW, shares are seen again. File and Printer Sharing option is checked in TW. Workaround: After investigating I found that 3 windows services must be allowed to make Network Shares work again on both W7 and W10 machines. Code: Function Discovery Provider Host (fdPHost) Function Discovery Resource Publication (FDResPub) SSDP Discovery (SSDPSRV) I set them to Unrestricted UDP and TCP traffic and Restrict to local network.
I have this annoying issue with yt-dlp.exe (I havent noticed it much with anything else). Obviously I have the executable whitelisted like several others, but very often when I run it from the command line, it won't respond, until I disable TinyWall. Sometimes even re-adding it to Exceptions helps, but it seems random and will get blocked again later on. Any ideas? //nothing appears in blocked connections btw
@ultim : I'm unsure about the following entry in TinyWall: https://i.postimg.cc/gjmCm9sb/202209210627-System-Trojan.jpg Is this the System.exe Trojan? Or is it a legitimate system file? Thanks in advance for your time and assistance in this matter...It is greatly appreciated!
Legit. I got my own System.exe too on Windows 10 x64 21H2 I can live well without it connecting anywhere, even my LAN.
The weird thing is that even when I allow system.exe unrestricted access, it will still be blocked by TinyWall, never really understood this. The reason why I allowed it, is because I was under the impression that perhaps it might sometimes cause problems with my Devolo powerline adapters, which my laptop is connected to.
I installed both TW and Comodo Firewall. (CruelSister settings more or less) Thus is what comodo HIPS says about TW: C:\Program Files (x86)\TinyWall\TinyWall.exe Modify Key HKLM\Software\Microsoft\SystemCertificates\Disallowed I'm no expert but see no reason for TinyWall to be messing with certificates? Especially after it's already installed??
I haven't got a clue what those system certificates are about. I doubt TW has any malicious motives for doing this though. So far it seems that it has always been able to correctly block outgoing connections and don't forget that it's not necessary to disable the standard Windows firewall, eventhough TW is a standalone firewall.
No expert here, but there may be a child process spawned by system.exe that has no privileges. You can check the box under system.exe for apply to child processes and see if that helps. Under the manage tab, click on the file, then there are 2 checkboxes there, one of them is the child processes. I've had trouble like this before. It may also be another .exe that is trying to run. You can see what attempts to connect by looking at the show connections option. Try unblocking and maybe your problem goes away.
Thanks, didn't think about this. But if it were child processes of system.exe, then TW should also display the right name of these .exe files.
I will just add something new I have noticed about this, it seems all it takes to unblock it, is to right-click tinywall systray icon.
Has anyone heard from @ultim ? It looks like it has been almost a year since any posts here. Hope all is well.
Let's hope everything is OK with him and hopefully he is working on some other project. I must say that I'm quite content with TinyWall, it doesn't really need any further development, but certain things could be better. Now that I think of it, he did plan a new GUI for TinyWall, but perhaps he simply doesn't have the time.
Hi, I am sorry if I worried anybody. I am fine, but I did take a hiatus from TinyWall. This pause also lead me to some revelations, I'll have a mixed bag of announcements (good and bad) as soon as I release version v3.3. I know I promised long ago that v3.3 will happen soon, but to show I mean it this time, I've prepared an RC: [download] If no regressions are found I could term this the final release. I'll just wait a couple days to see if anything shows up. Changes compared to v3.2.5 are pretty much as described here earlier. There shouldn't be anything surprising you need to watch out for, all your settings should automatically migrate when upgrading to the new version. The only problem you might run into if you're running an old Windows version is that Win10 is now a requirement. Hence Win7 users will need to stay on v3.2.5, but right now they aren't missing out on too much. Our good old SmartScreen "friend" will complain again for some time. This is because to make this release I had to buy a new code signing certificate as the old one expired. SmartScreen will stop being annoying as usual as soon as enough downloads happen.
