WindowsFirewallRuleset | PowerShell scripts to automatically create rules | Firewall library

If you don't have ssh keys and other setup required to clone via SSH then either clone with HTTPS or just download released zip file from Releases, and then for latest release under "assets" download zip file. These steps here assume you have downloaded a zip file from "assets" section under "Releases". Extract downloaded archive somewhere, these steps assume you've extracted the zip file (project root directory) into C:\ root drive directly. If you would like to use Windows PowerShell instead of PowerShell Core see: How to open Windows PowerShell. Otherwise the procedure for both PowerShell Core and Windows PowerShell is similar: Open up extracted folder, right click into an empty space and there is an option to run PowerShell Core as Administrator (Assumes you enabled context menu during installment of PowerShell Core) if not open it manually. If you don't have PowerShell context menu then move to C:\ root drive by executing following 2 lines (type or copy/paste following commands and hit enter for each), this is where you extracted your downloaded zip file.
If you don't have ssh keys and other setup required to clone via SSH then either clone with HTTPS or just download released zip file from Releases, and then for latest release under "assets" download zip file. These steps here assume you have downloaded a zip file from "assets" section under "Releases".
Extract downloaded archive somewhere, these steps assume you've extracted the zip file (project root directory) into C:\ root drive directly.
If you would like to use Windows PowerShell instead of PowerShell Core see: How to open Windows PowerShell
Otherwise the procedure for both PowerShell Core and Windows PowerShell is similar: Open up extracted folder, right click into an empty space and there is an option to run PowerShell Core as Administrator (Assumes you enabled context menu during installment of PowerShell Core) if not open it manually.
If you don't have PowerShell context menu then move to C:\ root drive by executing following 2 lines (type or copy/paste following commands and hit enter for each), this is where you extracted your downloaded zip file c: cd \
cd into downloaded folder, of course update command below if your extracted folder is called something else: cd WindowsFirewallRuleset-master
To see current execution policy run following command: (hint: you can use TAB key to auto complete commands) Get-ExecutionPolicy Remember what is the output of the above command, note that PowerShell Core defaults to RemoteSigned while Windows PowerShell defaults to Restricted on non server editions.
Set execution policy to unrestricted to be able to unblock project files, (Note that RemoteSigned will work only once scripts are unblocked) Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted You may be prompted to accept execution policy change, if so type Y and press enter to accept. For more information see About Execution Policies
At this point you should "unblock" all project files first by executing the script called Scripts\Unblock-Project.ps1, btw. project files were blocked by Windows to prevent users from running untrusted script code downloaded from internet: .\Scripts\Unblock-Project.ps1 If asked, make sure your answer is R that is [R] Run once as many times as needed to unblock project. (approx. up to 8 times)
Once project files are unblocked set execution policy to RemoteSigned: Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned You may be again prompted to accept execution policy change, type Y and press enter to accept.
Rules for programs such as your web browser, games etc. depend on installation variables. Most paths are auto-searched and variables are updated, otherwise you get warning and description on how to fix the problem. If needed, you can find these installation variables in individual scripts inside Rules folder. It is recommended to close down all other programs before running master script in the next step.
Back to PowerShell console and run Deploy-Firewall command below: .\Scripts\Deploy-Firewall.ps1 Hit enter and you'll be asked questions such as what kind of rulesets you want. If you need help to decide whether to run some ruleset or not, type ? when prompted to run ruleset and press enter to get more info.
Follow prompt output, (ex. hit enter to accept default action), it will take at least 15 minutes of your attention.
If you encounter errors, you can either ignore errors or update script that produced the error then re-run that specific script once again later.
When done you might want to adjust some of the rules in Local Group Policy, not all rules are enabled by default or you might want to toggle default Allow/Block behavior. Rules may not cover all programs installed on your system, in which case missing rules need to be made.
Now go ahead and test your internet connection (ex. with a browser or some other program), If you're unable to connect to internet after deploying these rules you have several options: Temporarily open outbound firewall in GPO or Disable Firewall Troubleshoot problems: Network troubleshooting detailed guide You can Reset Firewall to previous state Take a look into Readme folder for more troubleshooting options and documentation
As a prerequisite to deploy firewall, some system services have been started and set to automatic start, inside Logs directory you'll find Services_DATE.log to help you restore these services to default if desired. For example Windows Remote Management service should not run if not needed (The default is "Manual" startup)
This method requires you to simply download released zip file which can be found in Releases, this is always from "master" branch.
This method is good if you want to download from "develop" branch, to do so, use the branch button here on this site and switch to develop branch, next use Code button and either clone or download zip.