[Bug] Already-installed app (Zoom) does not seem to register its allowed connection properly with 3.7.1 anymore?

[krzemien77]

Checklist

• I have used the search function to see if someone else has already submitted the same bug report.
• I will describe the problem with as much detail as possible.

App version

3.7.1

Windows version

Windows 10 22H2 (all latest updates etc.)

Steps to reproduce

1. Open Zoom app (pre-installed before update to 3.7.1, latest version 5.15.5 (19404) (64-bit) )
2. Allow in 'Network connection was blocked'
3. No difference
4. Rinse and repeat - to no avail.
5. Removal from the list does not help.
6. Restart does not help either.

Screenshot enclosed.

NB I find it strange that Simplewall reports Zoom as 'unsigned'? See another screenshot - perhaps issue lies elsewhere?

Version 3.6.7 does work fine, but there's no SHA-256 feature shown in there. Also, it was possible to disable apps's signatures - it this option does not seem to be present in 3.7.1 any more?

Am reverting again to 3.6.7 in the meantime.

Expected behavior

Filter / rule with 'allowed' connection to be added to the config

Actual behavior

Connection remains blocked by the latest Simplewall v3.7.1

Logs

[henrypp]

even me see that zoom.exe is your list is non-existing file

[krzemien77]

What do you mean 'non-existing file'? Did you check the view from Explorer on the left - and zoom.exe highlighted in there?

Also, if it's non-existing, then where the connection prompt would be coming from?

Would you mind re-reading what I wrote please - and fix?

[krzemien77]

From 3.6.7:

[henrypp]

zoom.exe is highlighted as non-existent file, in 367 i dont know because it is selected

Also, if it's non-existing, then where the connection prompt would be coming from?

i dont know,im not telepath

[krzemien77]

Look mate, Zoom is installed on this PC, and 3.7 seems buggy and for some reasons thinks it's not.

3.6.7 is not buggy (in that respect) and recognises Zoom okay.

I supplied screenshots above to demonstrate it and that's all I had to say.

Do what you please but refrain from rude remarks and responses.

[henrypp]

and other apps can display notification?

[krzemien77]

Did not see, or check anything else: literally got updated to v3.7.1 earlier today (having reverted to v3.6.7 from v3.7 two days ago or so due to the crashes) and spotted after GUI popped up that Zoom is displayed as not present.

The queries I'd be really asking here are:

1. Why its SHA-256 is empty in Simplewall (not sure how this is obtained by your app)?
2. Despite that, why v3.6.7 is fine, and v3.7.1 is not, i.e.: what's changed?

I can always re-install Zoom and see if that helps. But find it strange that v3.6.7. remember it in the rules's list, and I do not have to do anything, but v3.7.1 seems to think it's not installed at all.

[krzemien77]

Please also note that Zoom is labelled as unsigned app in v3.6.7.

What does that actually mean?

[dethknite]

I would recommend uninstalling zoom and downloading the latest installation client (or at minimal downloading the latest install client) and then reinstalling it. The "not signed" means the zoom.exe file is not code-signed, which is abnormal for the actual install from Zoom. I would also remove the zoom rule and let it recreate a new one after launching.

[krzemien77]

Yeah, might do that - re-install - but everything was fine prior to updating to the latest release.
Also, there's second instance of Zoom installed for another user, so might see if the behaviour is the same.
Currently still using v3.6.7 where all is fine.

[krzemien77]

Just after I removed the rule and re-launched Zoom prior to its possible re-installation (via v3.6.7):

[krzemien77]

Having just removed and re-installed Zoom (latest version, downloaded at source) - still via v3.6.7:

I am going to check the behaviour using second user on this PC.

[krzemien77]

The situation with another user account is the same.

Via v3.6.7:

Once upgrade to v3.7.1 takes place:

Zoom client's version is the same in both cases.

Now, what just made me think is this: Zoom seems installing in user's profiles rather than in Program Files or similar.

Would that be the factor as effectively there are two instances of this app installed on this PC - and Simplewall might not handle that well?

[krzemien77]

Entirely out of my curiosity as admittedly I've not been lurking here for a while - since the above entry, in fact: this problem I reported above is seemingly addressed now, as I did allow simplewall to be updated to v3.7.7 some week ago or so and can confirm that all other things being equal and no changes to configuration, Zoom install etc., the app behaviour is now as expected.
So the inevitable query: did you manage to find the culprit?