Is there any plan to finally address the disabled firewall controls on W88.1 and W10 systems - or - will Webroot continue to charge W88.1 and 10 users for a non-functional feature ? Afterall, this issue has persisted for years now since the release of W8.
Please don't direct me to a technical explanation. I understand the OS doesn't allow WSA firewall controls to function on W88.1 and 10 systems the same as on W7 systems. It's a technical issue as far as implementation.
What I am asking is this: After nearly 3 years to mull it over, what is Webroot going to do about it ?
What is going to be done about the disabled firewall controls in W88.1 and W10 ?
Hi HJLBX
I won't direct you to a technical explanation, as you have requested, but just say that I was under the impression that Webroot had stated the position as far as this 'issue' (as you call it) and as far as I am awre nothing has changed re. that.
Why not be constructive and open a Feature Request on the subject...that is by far the best way to get attention for your 'issue', rather than posting her as you have done...the Development Team regulalrly review the Feature Requests and so it is a full proof way of getting their attention (cannot promise that they will give yo the response you are looking for though).
Regards, Baldrick
I won't direct you to a technical explanation, as you have requested, but just say that I was under the impression that Webroot had stated the position as far as this 'issue' (as you call it) and as far as I am awre nothing has changed re. that.
Why not be constructive and open a Feature Request on the subject...that is by far the best way to get attention for your 'issue', rather than posting her as you have done...the Development Team regulalrly review the Feature Requests and so it is a full proof way of getting their attention (cannot promise that they will give yo the response you are looking for though).
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
Hello Bladrick,
I thank you for your reply.
If my tone seems rather abrasive, it is not directed to any one person in particular, but rather the high-level Webroot "decision-makers."
What I find so distasteful is that Webroot, since the introduction of W8 in 2012, has not , and continues not to openly notify potential WSA purchaseers who use W88.1 and 10 systems that the WSA firewall controls do not function on those operating sytems. At least no place that I can find - and I have searched extensively over time.
Consequently, the W88.1 or 10 user only finds out after purchasing and installing WSA that the firewall controls do not function.
The ethical thing (and probably a legal obligation
equirement in some jurisdictions) to do would be for Webroot to inform potential buyers that WSA firewall controls do not function on W88.1 and 10 systems.
No one has a problem with this sort of behavior. Really... ???
* * * * *
As far as submiting a feature request it is rather pointless. The WSA firewall control functionality on those OSes is a long-standing, known issue to Webroot development that cannot be fixed - unless Microsoft changes the OS. And as we all know, Microsoft is not going to do that... as they have stated Windows 10 is projected to be around for a long time.
Plus, I'm not confident that Webroot development wishes to add much more to WSA. After all, you and other dedicated WSA users have submitted good suggestions for a file monitoring notification - which would be a HUGE benefit to the WSA user - but, unfortunately - that request has languished for a very long time.
I thank you for your reply.
If my tone seems rather abrasive, it is not directed to any one person in particular, but rather the high-level Webroot "decision-makers."
What I find so distasteful is that Webroot, since the introduction of W8 in 2012, has not , and continues not to openly notify potential WSA purchaseers who use W88.1 and 10 systems that the WSA firewall controls do not function on those operating sytems. At least no place that I can find - and I have searched extensively over time.
Consequently, the W88.1 or 10 user only finds out after purchasing and installing WSA that the firewall controls do not function.
The ethical thing (and probably a legal obligation
equirement in some jurisdictions) to do would be for Webroot to inform potential buyers that WSA firewall controls do not function on W88.1 and 10 systems.
No one has a problem with this sort of behavior. Really... ???
* * * * *
As far as submiting a feature request it is rather pointless. The WSA firewall control functionality on those OSes is a long-standing, known issue to Webroot development that cannot be fixed - unless Microsoft changes the OS. And as we all know, Microsoft is not going to do that... as they have stated Windows 10 is projected to be around for a long time.
Plus, I'm not confident that Webroot development wishes to add much more to WSA. After all, you and other dedicated WSA users have submitted good suggestions for a file monitoring notification - which would be a HUGE benefit to the WSA user - but, unfortunately - that request has languished for a very long time.
Hi HJLBX
I assumed that you missive was indeed n"ot directed to any one person in particular, but rather the high-level Webroot "decision-makers."", hence why I suggested that you raise the Feature Request rather than post in the Forums. As far as I know that is the quickest way to get through to the 'powers that be' and it also allows focused and unequivocal support (if that is what the Community want to do) for the point being made.
What I do not understand is if "The WSA firewall control functionality on those OSes is a long-standing, known issue to Webroot development that cannot be fixed - unless Microsoft changes the OS" then why even open the thread as surely you know what the answer is and why...and it is not down to Webroot.
One aspect of Webroot's design philosophy has always been, as I understand it, to look to make sure that there is absolutely no bloatware added to the core app...and therefore the probably weigh every request up carefully before deciding whether to proceed with inclusion or not...and that takes time. I believe, from checking some of the current statuses that there are a number of additions coming (but that is not official) so the best thing we can do is to continue to appropriately represent what we users believe should be included...some we will get and some not...but it is the right way IMHO.
Regards, Baldrick
provide the best in breed product in a number of areas, one of which is lightness of the app and hence new fucntionality...unless absolutely essential, is not added lightly.
I assumed that you missive was indeed n"ot directed to any one person in particular, but rather the high-level Webroot "decision-makers."", hence why I suggested that you raise the Feature Request rather than post in the Forums. As far as I know that is the quickest way to get through to the 'powers that be' and it also allows focused and unequivocal support (if that is what the Community want to do) for the point being made.
What I do not understand is if "The WSA firewall control functionality on those OSes is a long-standing, known issue to Webroot development that cannot be fixed - unless Microsoft changes the OS" then why even open the thread as surely you know what the answer is and why...and it is not down to Webroot.
One aspect of Webroot's design philosophy has always been, as I understand it, to look to make sure that there is absolutely no bloatware added to the core app...and therefore the probably weigh every request up carefully before deciding whether to proceed with inclusion or not...and that takes time. I believe, from checking some of the current statuses that there are a number of additions coming (but that is not official) so the best thing we can do is to continue to appropriately represent what we users believe should be included...some we will get and some not...but it is the right way IMHO.
Regards, Baldrick
provide the best in breed product in a number of areas, one of which is lightness of the app and hence new fucntionality...unless absolutely essential, is not added lightly.
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
To be perfectly honest, what is Webroot Development supposed to do in this situation ?
If they remove the firewall controls, then W7 and earlier users lose that WSA functionality. If they change it so it works on all versions of Windows, W7 and earlier users will cry "Foul."
Technically, there is nothing that can be done except change the WSA firewall controls in such a way that they function on all versions of Windows - or - create separate versions for W8-10 and W7 and earlier. In this second instance the firewall protections would be very different for WSA on W8-10 compared to that on W7 and earlier...
Webroot Development is in a tough spot. Technically, their options are limited.
* * * * *
All I'm saying is that Webroot should do the right thing and notify consumers about firewall control limitations on W8 - 10.
How would you feel if you purchased a vehicle ,and discovered only after purchase, that the lights do not function - and never can function. Would you find that acceptable ? If you were informed of that fact by the auto dealership while viewing the model in the showroom, would you still purchase that vehicle ?
If, and when, Webroot Development implements a solution to the firewall controls on W8 - 10 is irrelevant.
The issue is all about being forthright with consumers and ethical... that's it.
It's not about features, bloatware, technical details - but instead about Webroot doing the right thing.
One Webroot Staffer's reply was "Well, we offer a 30-day trial..."
From my perspective that's great, but many users never avail themselves of the trial before purchase. Most don't know any better...
So from the staffer's comment I infer their (the purchaser's) loss, I suppose... right ? Really ???
If they remove the firewall controls, then W7 and earlier users lose that WSA functionality. If they change it so it works on all versions of Windows, W7 and earlier users will cry "Foul."
Technically, there is nothing that can be done except change the WSA firewall controls in such a way that they function on all versions of Windows - or - create separate versions for W8-10 and W7 and earlier. In this second instance the firewall protections would be very different for WSA on W8-10 compared to that on W7 and earlier...
Webroot Development is in a tough spot. Technically, their options are limited.
* * * * *
All I'm saying is that Webroot should do the right thing and notify consumers about firewall control limitations on W8 - 10.
How would you feel if you purchased a vehicle ,and discovered only after purchase, that the lights do not function - and never can function. Would you find that acceptable ? If you were informed of that fact by the auto dealership while viewing the model in the showroom, would you still purchase that vehicle ?
If, and when, Webroot Development implements a solution to the firewall controls on W8 - 10 is irrelevant.
The issue is all about being forthright with consumers and ethical... that's it.
It's not about features, bloatware, technical details - but instead about Webroot doing the right thing.
One Webroot Staffer's reply was "Well, we offer a 30-day trial..."
From my perspective that's great, but many users never avail themselves of the trial before purchase. Most don't know any better...
So from the staffer's comment I infer their (the purchaser's) loss, I suppose... right ? Really ???
Well, if you have, as you say, "...contacted Webroot through official channels. We have campaigned to have Webroot's no-notification policy reversed." then what has been the point of starting this thread?
To be honest, and if I thought hard enough about it...but I won't waste the time...I could probably come up with one of two points of a similar nature, i.e., things that some may say should be declared to the customer before purchase, in terms of the several other security apps that I have used previously.
If one started putting caveats in terms of functionality then where would it end...the potential user would have to wade through potenteially hundreds of lines of text to check things...LOL...most user probably NEVER EVER read the EULA for the products they buy...so where does it end.
As far as I am concerned the position is clear.
Regards, Baldrick
To be honest, and if I thought hard enough about it...but I won't waste the time...I could probably come up with one of two points of a similar nature, i.e., things that some may say should be declared to the customer before purchase, in terms of the several other security apps that I have used previously.
If one started putting caveats in terms of functionality then where would it end...the potential user would have to wade through potenteially hundreds of lines of text to check things...LOL...most user probably NEVER EVER read the EULA for the products they buy...so where does it end.
As far as I am concerned the position is clear.
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
Personally, I think the complaint and conversation would be better off being brought to the actual source: Microsoft. Since it is the OS itself that is keeping what you seem to think is a 3rd party control option that you want to have returned, it must be done by them.
+56To be honest there isn't much we can do if Microsoft has disabled those controls. They're a much bigger company than us, so it isn't like we can force them to do our bidding 🙂
I started looking for topics related to this issue when I discovered that my recently updated Windows 10 system was relying on the Windows Firewall even though WSA is installed.
If you look at the feature list on the Webroot web site, the fourth feature mentioned is "Firewall and network connection monitor." There isn't an asterisk there that says "Except for Windows 10, where you will be using the standard firewall that comes with Windows." (I can't comment on Windows 8/8.1, although they are apparently incorporated by reference in the topic's name).
I have several computers that are now running Windows 10 that have different security software running, and none of them rely exclusively on the Windows firewall. Norton uses its own firewall. Trend Micro uses a firewall booster to harden the standard Windows firewall. Bitdefender uses its own firewall. So the argument that some have made that this is a Microsoft issue appears to be fallacious, as it appears to be a Microsoft issue only for Webroot.
Frankly, the fact that Webroot lists a firewall in its product features and does not indicate any limitations (i.e., there is no firewall other than the one you get with Windows) seems like false advertising to me. I used to feel pretty good about using Webroot software, but right now, I'm seriously looking at dropping them entirely.
If you look at the feature list on the Webroot web site, the fourth feature mentioned is "Firewall and network connection monitor." There isn't an asterisk there that says "Except for Windows 10, where you will be using the standard firewall that comes with Windows." (I can't comment on Windows 8/8.1, although they are apparently incorporated by reference in the topic's name).
I have several computers that are now running Windows 10 that have different security software running, and none of them rely exclusively on the Windows firewall. Norton uses its own firewall. Trend Micro uses a firewall booster to harden the standard Windows firewall. Bitdefender uses its own firewall. So the argument that some have made that this is a Microsoft issue appears to be fallacious, as it appears to be a Microsoft issue only for Webroot.
Frankly, the fact that Webroot lists a firewall in its product features and does not indicate any limitations (i.e., there is no firewall other than the one you get with Windows) seems like false advertising to me. I used to feel pretty good about using Webroot software, but right now, I'm seriously looking at dropping them entirely.
Hi DMCATL
Welcome to the Community Forums.
I do not think that anyone can have issue with your views and perhaps you are correct that Webroot should make some reference to the way that the outbound firewall component has reduced functionality due to Microsoft's stipulation.
Having said that WSA does not provide a full alternative firewall to the built in Windows but just makes use of it in terms of its overall solution. True, if one is looking for a goodly deal of firewall-related control then one may be well advised to look elsewhere but I believe that the majority of WSA users are not looking for that but rather an intelligent fire-wall component which they can leave alone/will do the business with minimal user intervention...which is precisely what WSA does.
For those like you who want more control the answer is pretty simple; turn off the Windows Firewall and run a 3rd party firewall in conjunction with WSA...WSA will cede control to the 3rd party firewall if it detects it running. There are a number of users that I know who do both and are happy, and that leaves them protected by the core strengths of WSA.
Now as to whether what Webroot list is 'false advertsing' or not is a moot point but I suspect that anyone trying to prove that would have a job to do it...for a number of reasons I will not go into here.
It is a shame that you are considering a move away from WSA, just because of what is a minor feature or lack of feature (depending on your point of view, of course) in WSA...and we will be sad to see you go...but that is your choice to which you are very much entitled.
Hope that you will reconsider but if not then I hope that you find an equally good solution to replace WSA with.
Regards, Baldrick
Welcome to the Community Forums.
I do not think that anyone can have issue with your views and perhaps you are correct that Webroot should make some reference to the way that the outbound firewall component has reduced functionality due to Microsoft's stipulation.
Having said that WSA does not provide a full alternative firewall to the built in Windows but just makes use of it in terms of its overall solution. True, if one is looking for a goodly deal of firewall-related control then one may be well advised to look elsewhere but I believe that the majority of WSA users are not looking for that but rather an intelligent fire-wall component which they can leave alone/will do the business with minimal user intervention...which is precisely what WSA does.
For those like you who want more control the answer is pretty simple; turn off the Windows Firewall and run a 3rd party firewall in conjunction with WSA...WSA will cede control to the 3rd party firewall if it detects it running. There are a number of users that I know who do both and are happy, and that leaves them protected by the core strengths of WSA.
Now as to whether what Webroot list is 'false advertsing' or not is a moot point but I suspect that anyone trying to prove that would have a job to do it...for a number of reasons I will not go into here.
It is a shame that you are considering a move away from WSA, just because of what is a minor feature or lack of feature (depending on your point of view, of course) in WSA...and we will be sad to see you go...but that is your choice to which you are very much entitled.
Hope that you will reconsider but if not then I hope that you find an equally good solution to replace WSA with.
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.