Yepp. I installed on multiple Windows and donated many times; I suggest you do the same (I am not related to this project in any way).
The only "issue" I ever had was with Dropbox updates. Dropbox main instance would download its new update, name it somewhat randomly and then use that program to trigger update from the internet. This would trigger simplewall to ask for permission, but by the time you click "yes" the update would already fail. Minutes alter Dropbox downloads same install with new file name and the whole whack-a-mole game starts all over. In this case you need to whitelist Dropbox IPs: in user rules create new rule: tcpip v6, any direction with remote rule: 162.125.35.0:443-162.125.36.255:443 - this will allow any new Dropbox update to download new version and safely call home to finish install.
The only "issue" I ever had was with Dropbox updates. Dropbox main instance would download its new update, name it somewhat randomly and then use that program to trigger update from the internet. This would trigger simplewall to ask for permission, but by the time you click "yes" the update would already fail. Minutes alter Dropbox downloads same install with new file name and the whole whack-a-mole game starts all over. In this case you need to whitelist Dropbox IPs: in user rules create new rule: tcpip v6, any direction with remote rule: 162.125.35.0:443-162.125.36.255:443 - this will allow any new Dropbox update to download new version and safely call home to finish install.