[Question] Why Simplewall/system doesn't remember the rule for apps not present at the boot time?

[TheFax]

I have a drive encrypted with VeraCrypt; this drive is unlocked manually when the system is already started. Into this drive I have several portable applications, eg: putty.exe. Obviously putty.exe should be allowed for me, so I answer "Allow" to the Network Alert window,; the application works without issues as expected. But if I reboot the system, I unlock the VeraCrypt drive (using exaclty the same drive letter), and I boot putty.exe, Simplewall still shows me the Network alert windows.

Steps to reproduce the possible issue

1. get a detachable drive
2. put a portable app that needs network access onto it
3. boot the app and use it, allowing the traffic via the Network alert window
4. stop the app and detach the drive.
5. reboot the system, so at the boot time simpewall can't see the content of the detachable drive because it's not connected to the system
6. attach the drive (ensure the drive letter is exactly the same)
7. run the portable app expected behaviour: the app runs and simplewall allow the traffic, as specified in step .3 real behavior: simplewall asks me if I would authorize the app to use network.

Interesting detail

If I add this step to my list above, between step 6 and 7:

6b. Open simplewall and click on "Refresh"

the expected behaviour is achieved and it works like a charm. But I find it illogical to have to perform this procedure every time I make changes to my VeraCrypt drive.

The questions

• Why system doens't remember that I allowed this app in the previous session?
• Could someone explain me if there is a solution to this behavior?

Screenshot

---

Simplewall version: 3.8.5 - Same behavior also in 3.8.4 and 3.8.3 Windows version: Microsoft Windows 11 Pro - 10.0.22631 bld 22631

Similar interesting issues:

• Question 1756
• Feature 1898