Thank you, I’m just looking in how to fix this for other users (if when you said “the blocks set specifically for Microsoft always changed back to allowed on their own,” you were talking about MFW), as I haven’t ever encountered Windows turning a MFW block rule into an allow rule. If it’s just creating a separate allow rule and another block rule is in place (which is expected with Windows, or if you give that permission to some app), then it shouldn’t matter as block rules supersede allow rules within Windows Defender Firewall (though if there are separate ipsec or kernel/custom driver rules, it’s not always quite so clear).
In my case, the rules actually changed and the old ones were lost.
And I tried for a long time to solve the problem with Opus.
Thanks, I’ll open an issue on Github to see if anyone else has reproduced.
1 Like
It’s a simple workaround, I had removed the MFW prefix, which allowed Windows to override those rules. Now adding back the prefix by default, they exist as separate rules, and block rules override allow rules.
I attempted to disable all Windows-created rules by default, but that would lead to ongoing maintenance to figure out every service and app necessary for internet, which gets complicated when dealing with WSL + VPNs. So in reverse, users can look at the audit log and determine if they want to block and Windows-created rule that they don’t already have a rule for.
1 Like