This journey began not with software, but with purpose—to build a secure, minimal, privacy-focused Windows system free of tracking, bloat, or forced connectivity. From creating a clean USB using PowerShell and diskpart, to bypassing mandatory internet setup with OOBE\BYPASSNRO in windows 11 only to ensure secure firewall as the first layer of intraction with the ISP so every step was chosen for control and clarity. Whether it was installing Windows offline, isolating driver installs, or experimenting with firewall behavior—everything was tested by hand, not just copied from the internet.
Today’s Windows 10 and 11 push users toward automatic connectivity—through dynamic ports, service dependencies, and forced telemetry updates that can override even manually configured rules. This shift places user privacy firmly in the hands of system designers and update mechanisms. Worse, during the initial setup—when internet access is mandatory—your system becomes vulnerable to ISP-level interference or malicious manipulation.
Yes, you can install drivers manually and define strict firewall rules later—but if you connect blindly to the internet during setup, you risk handing over control before you’ve secured your system. This guide exists to reclaim that control—for those who believe the system should obey the user, not the other way around.
To lock down your Windows firewall before installing or using any other apps, run the following in PowerShell (Administrator):
netsh advfirewall set allprofile firewallpolicy blockinbound,blockoutbound
netsh advfirewall set publicprofile firewallpolicy blockinbound,allowoutbound
💾 Save Your Current Firewall Settings
Before making major changes, back up your firewall rules with:
netsh advfirewall export "C:\path-to-file\firewall.wfw"
To restore them later:
netsh advfirewall import "C:\path-to-file\firewall.wfw"
📁 Download Sample Configuration
Use this sample .wfw file to start from a known, minimal configuration: Click here to download
