As of a week ago I had noticed that some of my games had been stuck in update queued but didn't think much of it becuase I was not playing said games. Well now a game that I play has an update that will not download. Long story short after some trouble shooting on my end I discovered that the problem was that it could not create an HTTP connection with it's server to start the download (it uses HTTP I assume port 80). First thought was firewall and anything that interacts with firewall to enforce an access list so I turned off webroot and voila steam would create a connection to their server and downloads fired up. After some more refinement I discovered that it is not the firewall or the web shield it is the Realtime shield that is causing this issue. Running without the realtime shield seems problematic. Any ideas would be appreciated.
p.s. Steam.exe as well as steamwebhelper are already allowed processes.
Hi gh0st3d
Welcome to the Community Forums.
As far as I know there should be no issue in relation to Steam with WSA installed. From what you are describing it could be than an update or other change has triggered a false positive to which WSA is reacting.
What I would do is to Open a Support Ticket, to get the Support Team to look into this for you. That shoudl upload basic Scan & Threat Logs-related information for the Team to look at but you should either replciate the contents of your post or include a link to this thread in your ticket as it will provide valuable information for them.
Whilst waiting for them to respond you could also take a look at a number of areas in WSA where the user can alter the 'protection' provided as it may be that a component of Steam could be being 'Blocked' as a result of the FP.
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...WSA does not allow it to run on the system. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so will help you get to the bottom of what is causing you the issue… (I am indebted to the KB article by JimM of which this is my re-interpretation).
Do post back with any specific questions that you may have re. the above.
Regards, Baldrick
Welcome to the Community Forums.
As far as I know there should be no issue in relation to Steam with WSA installed. From what you are describing it could be than an update or other change has triggered a false positive to which WSA is reacting.
What I would do is to Open a Support Ticket, to get the Support Team to look into this for you. That shoudl upload basic Scan & Threat Logs-related information for the Team to look at but you should either replciate the contents of your post or include a link to this thread in your ticket as it will provide valuable information for them.
Whilst waiting for them to respond you could also take a look at a number of areas in WSA where the user can alter the 'protection' provided as it may be that a component of Steam could be being 'Blocked' as a result of the FP.
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
- PC Security > Block/Allow Files
- Identity Protection > Application Protection
- Utilities > System Control > Control Active Processes
- "Allow"
- "Protect/Monitor"
- "Block/Deny"
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...WSA does not allow it to run on the system. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so will help you get to the bottom of what is causing you the issue… (I am indebted to the KB article by JimM of which this is my re-interpretation).
Do post back with any specific questions that you may have re. the above.
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
I am in the same boat as the OP. I have been using Webroot in some form or another for close to a decade, and the end of January is the first time I have ever experienced an issue between it and Steam (or any program i run for that matter).
As with the OP I have tried many solutions supplied by cut and paste answers. The only thing that solves it is completely disabling Webroot. I loathe to do this, you guys really make a good product hence me using it for so long, but please look into this. My first encounter with it was January 28-29 as that was my first attempt at figuring this out from the Steam Community end. Nothing on that end worked, as previously stated only disabling webroot completely let me update any games.
The games themselves play perfectly even with a required internet connection. Only when they need an update is there an issue. I am not sure if Steam changing something client side that screwed with how Webroot handles it, or if you guys changed something that screwed with Steam. But again, please look into this.
As with the OP I have tried many solutions supplied by cut and paste answers. The only thing that solves it is completely disabling Webroot. I loathe to do this, you guys really make a good product hence me using it for so long, but please look into this. My first encounter with it was January 28-29 as that was my first attempt at figuring this out from the Steam Community end. Nothing on that end worked, as previously stated only disabling webroot completely let me update any games.
The games themselves play perfectly even with a required internet connection. Only when they need an update is there an issue. I am not sure if Steam changing something client side that screwed with how Webroot handles it, or if you guys changed something that screwed with Steam. But again, please look into this.
+62Hello Calibrated
Welcome to the Webroot Community,
Please Open a Support Ticket, to get the Support Team to look into this for you. They will be able to whitelist these files for you.
Welcome to the Webroot Community,
Please Open a Support Ticket, to get the Support Team to look into this for you. They will be able to whitelist these files for you.
Windows Insider, iMac 2021 27 in i5 Retina 5, iMac OS Sequoia (15.3.2}, Security: iPads, W 10 & (VM:15), ALIENWARE 17R4, W10 Workstation, ALIENWARE 15 R6, W11, Webroot® SecureAnywhere™ Internet Security Complete (Android Samsung Galaxy Ultra Note 23, Webroot Beta Tester. Security
1 person likes this
Reply
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.