-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Rules > Allow Windows Update not working #1648
Comments
See: #1636 |
Was working correctly in v3.7.3 |
This comment was marked as abuse.
This comment was marked as abuse.
If you're not using the in-built Windows Update rule, then you might as well simply set svchost on a timer and let the update download. But anything other than the specific ruleset needed is non-ideal, hence this issue. |
Has anyone else here enabled the portable setting? That might be a factor. |
Not here, and the Update feature stopped working in 3.7.4 |
I have the same problem that you for at least a month under Windows 11, latest version. |
now it is fixed, see it in next version or... simplewall.zip |
Thank you! Works perfectly now. |
I just got the 12-2023 Cumulative Update, and now Windows Update has stopped working again. Did Microsoft change something again? Edit: Never mind. It must have been a server issue. Started working on its own. |
This bug is back - can't get the rule to persist reboot. |
Checklist
App version
3.7.5
Windows version
Windows 10
Steps to reproduce
Expected behavior
Windows Update should be allowed through the firewall.
Actual behavior
"We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet."
Also, this might be connected to 2 other bugs:
Update: I confirmed by checking the ini settings file that the WU-fix-enabled parameter never switches to true. Even manually setting it to true after closing Simplewall doesn't work. It switches back to false when Simplewall is started.
Logs
No response
The text was updated successfully, but these errors were encountered: