Fort Firewall v3.11.4 UI: Options: Warn about deprecated App Group's Texts. UI: Options: Schedule: Open Programs on double-click of "Purge Obsolete" task. Driver: Fix new programs ignoring for "Ignore" mode.
Fort Firewall 3.11.5 UI: Show Splash screen on startup (Force Qt to populate fonts). UI: Remove 'v' from version text.
Fort Firewall 3.11.8 UI: Options: Add "Default" button. Driver: Enumerate processes on startup for "Apply rules to child processes".
Fort Firewall 3.11.9 Driver: Shaper: Tweak limit processing. UI: popcnt is not supported by old CPU (MSVC 17.9 regression in v3.11..
Fort Firewall 3.12.0 UI: Option to try to start a Service on startup. UI: Logger: Append to last log file. UI: Tasks: Add debug outputs. Installer: Add "qt.conf" to use GDI font engine. Driver: Shaper: Rework packets processing again.
Fort Firewall 3.12.1 UI: Add Arabic language. UI: AppInfoUtil: Improve version info parsing. UI: Update SQLite to 3.45.2
Fort Firewall 3.12.2 UI: Prepare Rules forms (Driver is not yet ready). UI: Options: Edit Hot Key Shortcuts. UI: Fix layouts for Arabic language. UI: Update SQLite to v3.45.3
Fort Firewall 3.12.3 UI: Support "-c prog add|del|allow|block|kill PATH" command line argument. UI: MyFort: About: Add Download/Install buttons. Installer: Add "/LAUNCH" argument (useful with "/SILENT"). UI: FortFirewall.exe.ini: Add "forceDebug" flag.
Fort Firewall 3.12.4 Process "-c prog ..." command line arguments by Service directly in absence of UI process. Installer: Don't uninstall "boot filter" on upgrade.
Fort Firewall 3.12.5 UI: Portable: Istall driver on startup and uninstall on exit. Installer: Portable: Don't install driver to system.
Fort Firewall 3.12.6 UI: Service: Restart clients on upgrade. UI: Use RegisterApplicationRestart(). Installer: Remove unneeded "delay-start.bat".
@tnodir I'm currently testing Fort Firewall and i like it a lot so far. However, i just updated to the newest version. After update, it started to ask outbound connections again, which i already granted access. Like outlook.exe, steam.exe etc. I also noticed, that some programs, when doing update check, can make outbound connection, before Fort Firewall can react "Block or Allow".
Please check a Programs window: does it contain the requested paths already? You may use Wildcard paths, if that programs change version in the path. Because a Filter Mode is set to "Auto-Learn" initially. You have to change it to "Block..": - https://github.com/tnodir/fort/wiki...the-fort-firewall-operates-in-auto-learn-mode - https://github.com/tnodir/fort/wiki...irewall-block-any-programs-after-installation
@tnodir Yeah, damn, rtfm Found one "bug" or is it just me again. I enabled "Block all traffic when Fort Firewall is not running". Rebooted. After reboot, Fort Firewall tray icon is grey. When im trying to open Fort Firewall, it throws an error "Service isn't available" and "Cant save settings". On this test laptop, i also using trial version of Sophos Home Premium. It might or not that Sophos causes problems here, especially its early-lauch malware driver or something like that.
Please show a log files from: - C:\ProgramData\Fort Firewall\logs - C:\Users\<USER>\AppData\Local\Fort Firewall\logs Also check that Fort Firewall Service is running. How did you install the Fort Firewall, with which flags? I do NOT recommend to use Portable installation until you know what you are doing. With portable you always will have errors with driver (because of Admin rights), updating to new version etc etc. Also recently one user messed up with permissions to "C:\ProgramData\" folder. Regular users should have read access to its sub-dirs.
@tnodir Can't find anything in Sophos logs related to Fort Firewall...Sophos writes to Windows Event Log, nothing Fort related stuff there. When i try to start Fort service, it errors 1075: "The dependency service does not exists or has marked for deletion" When query FortFirewallSvc dependencies by using command: sc qc FortFirewallSvc: SERVICE_NAME: FortFirewallSvc TYPE : 10 WIN32_OWN_PROCESS START_TYPE : 2 AUTO_START ERROR_CONTROL : 1 NORMAL BINARY_PATH_NAME : "C:\Program Files\Fort Firewall\FortFirewall.exe" --service LOAD_ORDER_GROUP : NetworkProvider TAG : 0 DISPLAY_NAME : Fort Firewall Service DEPENDENCIES : fortfw SERVICE_START_NAME : LocalSyste
"fortfw" is a Driver's service. Again, did you check the "Portable" flag on installation? If yes, then remove all Fort's stuff and reinstall it without the "Portable" flag, as in this video: https://github.com/tnodir/fort/wiki/User-Guide#step-by-step-guide-to-install-the-software
Then it's very strange, why the driver can not start on reboot. Maybe there is some error message about "fortfw" driver in the Event Viewer?
@tnodir Uninstalled and reinstalled Fort. Now all is fine, even "block all traffic when fort firewall is not running" works now after booting. When uninstalling i saved my old Fort rules, so i dont have to do them again. This feature is a big plus. But what caused this "1075" error is still mystery. No biggie, system up and running nicely now.
Yeah, but I would like to know why the driver was not started. Did you check the Event Viewer: System logs for "fortfw" events?
