spudboy Posted August 3, 2018 Share Posted August 3, 2018 1 hour ago, Ultravires said: After uninstalling v5.3.1.0 and trying to update to 5.4.0 it gives me a popup error on win10 x64, guess it is back to 5.3.1 No one can try helping without knowing the error that popped up & what the Windows Logs say about it. :) Im on 10 x64 and had no issues. :) Link to comment Share on other sites More sharing options...
dcs18 Posted August 4, 2018 Share Posted August 4, 2018 11 hours ago, spudboy said: 11 hours ago, dcs18 said: The implementation of Secure Rules which you posted is failure-prone — the culprit (highlighted from your own image) is being reproduced below:— I guess I never once had a failure prior to it being changed. Can you provide an example of when/why/how it would fail? Is it reproduceable? And if so, how? Right after certain programs such as uTorrent, Skype, Firefox, etc., etc. were installed or updated/upgraded, their corresponding rules would be found on my Windows Firewall Control (WFC) with utter disregard to my selected option of Delete unauthorized rules — this behavior was reproducible on my own systems as also on all my client machines. Link to comment Share on other sites More sharing options...
spudboy Posted August 5, 2018 Share Posted August 5, 2018 On 8/4/2018 at 1:38 AM, dcs18 said: Right after certain programs such as uTorrent, Skype, Firefox, etc., etc. were installed or updated/upgraded, their corresponding rules would be found on my Windows Firewall Control (WFC) with utter disregard to my selected option of Delete unauthorized rules — this behavior was reproducible on my own systems as also on all my client machines. Sorry mate, but I am completely unable to reproduce this on several machines & have never experienced this issue even once in the past. Sounds like a configuration problem. Otherwise I don't know why it would happen to yourself and ALL of your clients, but never once for me on any machine. I use the following: Profiles: Medium Filtering Notifications: Show Notifications Options: Start automatically at user logon Rules: Outbound Security: Secure Profile/Secure Rules/Delete unauthorized rules (Authorized groups: WFC & Temporary Rules) Edit: Can you please provide a screencapture video of this being reproduced? Showing your configuration, that the rule does not priorly exist, and of it being created & not deleted regardless of having it set to do so? Edit2: @jayesh30202 I noticed you liked dcs18's comment. Are you able to reproduce this on your system as well? And if so, can you also please provide video of it happening? I've tried & tried & tried & tried. This unwanted behavior just does not exist on my end. Link to comment Share on other sites More sharing options...
dcs18 Posted August 6, 2018 Share Posted August 6, 2018 On 8/5/2018 at 9:40 PM, spudboy said: Sorry mate, but I am completely unable to reproduce this on several machines & have never experienced this issue even once in the past. Sounds like a configuration problem. Otherwise I don't know why it would happen to yourself and ALL of your clients, but never once for me on any machine. If it were truly a matter of misconfiguration, would've seen the same problem on the v5.3.1.0, as well. On 8/5/2018 at 9:40 PM, spudboy said: I use the following: Profiles: Medium Filtering Notifications: Show Notifications Options: Start automatically at user logon Rules: Outbound Security: Secure Profile/Secure Rules/Delete unauthorized rules (Authorized groups: WFC & Temporary Rules I use this one. On 8/5/2018 at 9:40 PM, spudboy said: Edit: Can you please provide a screencapture video of this being reproduced? Showing your configuration, that the rule does not priorly exist, and of it being created & not deleted regardless of having it set to do so? Would've been more than happy to post the screenshot . . . . . but, as mentioned — the issue can't be reproduced on the v5.3.1.0. However, had posted a screenshot of this issue somewhere on the thread (linked above) — but for some reason it's not showing-up in (the new nSane) search. Link to comment Share on other sites More sharing options...
Axe Posted August 6, 2018 Share Posted August 6, 2018 Just when I thought I should probably buy WFC it became a freeware. And after reading the comments I'm not sure if I should be happy or sad. Link to comment Share on other sites More sharing options...
spudboy Posted August 6, 2018 Share Posted August 6, 2018 10 hours ago, dcs18 said: If it were truly a matter of misconfiguration, would've seen the same problem on the v5.3.1.0, as well. I use this one. Would've been more than happy to post the screenshot . . . . . but, as mentioned — the issue can't be reproduced on the v5.3.1.0. However, had posted a screenshot of this issue somewhere on the thread (linked above) — but for some reason it's not showing-up in (the new nSane) search. Without some concrete evidence, I just can't accept that this behavior is happening specifically from reverting back to the prior implementation of Secure Rules. I have tried everything under the sun & I am unable to reproduce on several systems. I also saw in the Wilders forum mention of this happening to someone with the version used in 5.3.1.0. So I am left to believe that it is either user error, or some incompatability with other software installed on a users system. Maybe it's something that is installed on your, and all of your clients machines that causes it? Also, if it were misconfiguration it could very well not happen on 5.3.1.0 becasue they have different configuration options. It is also well known that the implementaion in 5.3.1.0 causes plenty of issues in Windows 10. INcluding but not limited to the Start Menu freezing or not working, and also having to disable secure rules, install updates, re-enable seure rules, then having to go in and manually delete the created rules manually. Thus far I have seen zero concrete evidence about the claims of 5.4.0.0 Secure Rules failing. What would you propose would cause it to happen on your own and ALL of youor clients machines, but not whatsoever, in many years, on ANY of mine? 2 hours ago, Axe said: Just when I thought I should probably buy WFC it became a freeware. And after reading the comments I'm not sure if I should be happy or sad. It's fine, imo. And so is the telemetry. If people want any future updates to WFC they should be allowing the telemetry. It's completely harmless. Link to comment Share on other sites More sharing options...
dcs18 Posted August 6, 2018 Share Posted August 6, 2018 On 8/6/2018 at 11:53 PM, spudboy said: Also, if it were misconfiguration it could very well not happen on 5.3.1.0 becasue they have different configuration options. As far as configuration is concerned, the only difference in option between the 5.3.1.0 and 5.4.0.0 is the one highlighted on this screenshot, from here. On 8/6/2018 at 11:53 PM, spudboy said: It is also well known that the implementaion in 5.3.1.0 causes plenty of issues in Windows 10. INcluding but not limited to the Start Menu freezing or not working, and also having to disable secure rules, install updates, re-enable seure rules, then having to go in and manually delete the created rules manually. The 5.3.1.0 does not cause any of those claimed issues since none of us are running Windows 10. Link to comment Share on other sites More sharing options...
sulim Posted August 6, 2018 Share Posted August 6, 2018 Windows Firewall Control 5.4.0.0 (Repack & Portable) ELCHUPACABRA Features of Windows Firewall Control repack: 1. Combine the installation of the program in one distribution or unpack the portable (PortableApps format) version 2. Optional installation of the crack (ru-board) 3. Optional installation of recommended rules 4. Removed components responsible for collecting and sending user data 5. Picks up the external settings.reg file (if located next to the installer) Site: https://www.upload.eeSharecode: /files/8777947/windows_firewall_control_5.4.0.0.zip.html Link to comment Share on other sites More sharing options...
spudboy Posted August 6, 2018 Share Posted August 6, 2018 15 minutes ago, dcs18 said: As far as configuration is concerned, the only difference in option between the 5.3.1.0 and 5.4.0.0 is the one highlighted on this screenshot, from here. The 5.3.1.0 does not cause any of those claimed issues since none of us are running Windows 10. Right. Those are the differences. But I did not know what you had for those settings outside of Delete unauthorized rules. As far as not using WIndows 10, gotcha. I would still like to know your take on why the auto-deleting of rules has failed for you and your clients, but not once for myself. Would you also be willing to re-install 5.4.0.0 and take video of it happening to you? I ask becasue if others can reproduce it easily, then there is most certainly a bug. Regardless if it happens to me or not. You are an extremely valued member here & people listen to what you say. I just feel that without some sort of hard evidence, people may be unjustifyably frightened away from the update due to your experience with Secure Rules in it. Link to comment Share on other sites More sharing options...
dcs18 Posted August 6, 2018 Share Posted August 6, 2018 On 8/7/2018 at 12:34 AM, spudboy said: I would still like to know your take on why the auto-deleting of rules has failed for you and your clients, but not once for myself. Would you also be willing to re-install 5.4.0.0 and take video of it happening to you? TBH, the issue I reported was not observed on the 5.4.0.0 — but on various previous builds based on the same implementation. As much as I'd like to install and use the very latest (5.4.0.0 in this case,) the answer to the failure of auto-deleting might lie in this post reproduced below in part (as per my suspicion.) On 7/25/2018 at 7:11 PM, dcs18 said: That been said . . . . . at every update, CCleaner is indeed guilty of switching-on a couple of unwanted features back to on (regardless of User preference/s) — have got this annoying aspect covered, as well . . . . . have already incorporated numerous hacks (over the years) whereby my registry rejects any attempt by any app. or program from adding unwanted entries which have been manually disabled. Link to comment Share on other sites More sharing options...
spudboy Posted August 7, 2018 Share Posted August 7, 2018 12 hours ago, dcs18 said: TBH, the issue I reported was not observed on the 5.4.0.0 — but on various previous builds based on the same implementation. As much as I'd like to install and use the very latest (5.4.0.0 in this case,) the answer to the failure of auto-deleting might lie in this post reproduced below in part (as per my suspicion.) I've never had that happen with CCleaner. Haha. Wasn't that only an issue with the 5.45 version that was pulled (which I never updated to)? If not, then it's another mystery as to why I've never had it change settings on me personally. All in all, I believe it's safe to say that no one should be concerned with the latest version of WFC. You, yourself stated that you didn't experience it in the latest version so that kinda leaves only the telemetry thing that some people are (imo) overly concerned about.... which can be blocked if a user chooses to do so. Although it will have an impact on future updates if enough people are doing so. Thanks for the conversation. Cheers! Link to comment Share on other sites More sharing options...
dcs18 Posted August 7, 2018 Share Posted August 7, 2018 15 hours ago, spudboy said: You are an extremely valued member here & people listen to what you say. I just feel that without some sort of hard evidence, people may be unjustifyably frightened away from the update due to your experience with Secure Rules in it. 2 hours ago, spudboy said: All in all, I believe it's safe to say that no one should be concerned with the latest version of WFC. You, yourself stated that you didn't experience it in the latest version so that kinda leaves only the telemetry thing that some people are (imo) overly concerned about.... which can be blocked if a user chooses to do so. Although it will have an impact on future updates if enough people are doing so. Thanks for the conversation. Cheers! Fair enough, shall install the latest 5.4.0.0 and then post the video here — this will have to wait till next week though, since I'm in the middle of a security changeover and deployment. Link to comment Share on other sites More sharing options...
dcs18 Posted August 24, 2018 Share Posted August 24, 2018 On 8/4/2018 at 12:42 AM, dcs18 said: The implementation of Secure Rules which you posted is failure-prone <snip> Was having a one-to-one interaction with Alex regarding a different issue when I discovered why my Secure Rules had failed me, in the past — at least, now I know the root cause. Link to comment Share on other sites More sharing options...
Ecarion Posted January 1, 2019 Share Posted January 1, 2019 Just for the record, I had just discover the WFN-v2.0 Beta 3 (aka Windows Firewall Notifier). That's why I can't give any feedback. But one day perhaps I will replace WFC by WFN ((abandon support ?) We will see in the futur). I think there is another choice also with the Private Winten. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.