I used tw on two PCs, but on a PC with emisi installed, I noticed that there were cases where selecting an application to be excluded was not reflected in the rules. I guess it is probably not coexisting well with emisi's fw monitoring function.
- Status
Emisi? I can't find anything about it on the internet.
Any software that prevents TinyWall from adding its "Compat rules" to Windows Firewall will make it impossible to whitelist things in TinyWall.
Any software that prevents TinyWall from adding its "Compat rules" to Windows Firewall will make it impossible to whitelist things in TinyWall.
By Emsi he meant Emisoft Anti-Malware: Emsisoft | Anti-Malware: Lightweight Malware Protection for the Home
F
ForgottenSeer 85179
Thread author
I got this error if i try to allow a program from network log:Well, if there are problems and you report them, hopefully I can get rid of the problems
Thx, fixed in next build. I got this fixed now in my code, but this must have been a one-off error, right? Or is it easily reproducible in your case?
I did a 5-min test. I installed Emisoft Anti-Malware on a Win8.1 VM, then I installed TinyWall. For now I couldn't see any compatibility problems. Firefox decided to update itself which Emsisoft overzealously blocked in the middle, and that resulted in Firefox running in some kind of ghost process from a non-existing file on the disk. That made it impossible to whitelist Firefox in TinyWall as there was no corresponding file on the drive. This was still the case even after closing and reopening Firefox (yeah, weird). After a reboot of the VM everything solved itself though, Firefox was again running from its usual path (C:\Program Files\Mozilla Firefox\firefox.exe) and it could again be whitelisted.
In other words, aside from some glitch which was seemed to be caused by Emsisoft interfering with the browser's self-update, it seems for now TinyWall and Emsisoft can be run in parallel.
F
ForgottenSeer 85179
Thread author
It was reproducible on every try to allow a program from network log. So easily reproducible.
I can test new build after upload
I think your firewall was locked. Did you set a password in TinyWall? It is of course still a bug in TinyWall, I'm just making sure I have really found the cause.It was reproducible on every try to allow a program from network log. So easily reproducible.
I can test new build after upload
I am using Windows10 1909 environment. Most of the software applies the rules without any problems. However, only 'Microsoft Store' can not connect in the environment where tw is installed. I cannot connect even if you register the software by specifying it. The results were the same for automatic rule creation. To be precise, the rules are written but cannot be connected.
This problem does not occur on the PC using Defender.
I don't have a Win10 VM right now, and Emsisoft is not installed on my work machine, but I can whitelist Windows Store there easily and it works. I tried the same thing in the Win8.1 VM too (where Emsisoft is installed), went to TinyWall->Whitelist by process->winstore, and the store worked and I could log in and install apps. there.
I'm not sure if will make a difference in your case, but just to be sure: Is the "Windows Store Update" special exception enabled?
I'm not sure if will make a difference in your case, but just to be sure: Is the "Windows Store Update" special exception enabled?
Special exceptions only enabled recommendations.
F
ForgottenSeer 85179
Thread author
Last edited by a moderator:
What does the Connections windows say? Is there anything newly blocked when you try to use Windows Store on the Emsisoft PC?
@ultim
I appreciate your concern. This is the pc ss running Emisisoft.
I uninstalled tw, reset the Windows Firewall restrictions, and then installed it again. I was able to connect to the Microsoft Store without any problem right after I set it to the automatic memory state, but it will be this state when I restart it.I couldn't connect the weather report as well, but this has been resolved.
The pc running WD has no problem. This is ss of that pc.
I appreciate your concern. This is the pc ss running Emisisoft.
I uninstalled tw, reset the Windows Firewall restrictions, and then installed it again. I was able to connect to the Microsoft Store without any problem right after I set it to the automatic memory state, but it will be this state when I restart it.I couldn't connect the weather report as well, but this has been resolved.
The pc running WD has no problem. This is ss of that pc.
Oh, ok, it seems you are not running the beta. Please install the beta (2.99.15) and whitelist the Store not as an executbale, but as a UWP-app. TinyWall 2.1 never officially supported UWP apps in the first place.
EDIT: I recognize this is an older version because the new version has a 3rd column in that list. See:
Last edited:
You might also need to whitelist Microsoft.Windows.CloudExperienceHost (UWP).
Hello Everybody,
As a token of thanks for everybody here helping me out, I would like to offer you a small utility I've written. You'll love it if you ever wished you could easily download music and video from various websites.
PM me if you'd like access. After a week only donators will have access.
As a token of thanks for everybody here helping me out, I would like to offer you a small utility I've written. You'll love it if you ever wished you could easily download music and video from various websites.
PM me if you'd like access. After a week only donators will have access.
I have installed and tried beta version 2.99.15.
The PC with the problem with the UWP application will display a message immediately after installation, such as 'Cannot start because required data cannot be found'. We reset the built-in fw settings just in case, but there was no improvement. When transitioning from stable to beta, how do you best handle uninstalling the stabilizer? Overwrite recommended?
The PC with the problem with the UWP application will display a message immediately after installation, such as 'Cannot start because required data cannot be found'. We reset the built-in fw settings just in case, but there was no improvement. When transitioning from stable to beta, how do you best handle uninstalling the stabilizer? Overwrite recommended?
What displayed this message? TinyWall's installer? Or TinyWall itself? Or something completely else? The only similar message in TinyWall is "Database is missing or corrupt.", but that seems to be a different message (or maybe the same but original meaning lost in translation?).
You can/should just install the beta while 2.1 is installed. It will automatically upgrade the version AND migrate your firewall settings. It is unnecessary to uninstall the older version first.When transitioning from stable to beta, how do you best handle uninstalling the stabilizer? Overwrite recommended?
Downgrading is a different story: To downgrade, you need to uninstall the newer version first and then install the old version.
It is very important in general, that you only use the installer and uninstaller to install, remove and upgrade. Never try to upgrade or remove the files manually without using the (un)installer. This is of course true for all other security software too that have non-trivial integration with the system, but I need to point out TinyWall is no exception. You haven't done any manual file deletions or upgrades have you?
- Status
You may also like...
-
Block Common Attacks: A Beginner's Guide to Windows Firewall- Started by Divergent
- Replies: 18
-
Defender Hardening Console (part of Hawk Eye Analysis Platform)- Started by Trident
- Replies: 62
-
Linux Firewall Basics: A Beginner's Guide to iptables for Blocking Common Attacks
- Started by Divergent
- Replies: 1
-
Simple Steps to Secure Your Windows 11 PC
- Started by Divergent
- Replies: 0
-
